TablePress plugin review and common issues

First verify the shortcode format is correct: [table id=1] where “1” matches the table ID in TablePress → All Tables. If the shortcode renders as literal text (not a table), TablePress may not be active or a theme/plugin is interfering with shortcode processing. If the table is completely absent from the rendered page (shortcode is removed), a page builder or editor (Elementor, Beaver Builder) may be processing shortcodes differently — use that builder’s Shortcode element/widget to embed the TablePress shortcode. Also check if your caching plugin is serving a cached page from before the table was added — clear all caches.

DataTables features are enabled per-table in TablePress → Edit Table → Advanced Configuration. In the Table Options section, verify “Enable Sorting”, “Enable Search/Filtering”, and “Enable Pagination” are checked. If the options are enabled but features are not working on the frontend, check browser DevTools Console for JavaScript errors — a JavaScript conflict may prevent DataTables from initializing. Also verify DataTables.js is loading on the page (check Network tab for datatables.min.js). Some performance plugins defer JavaScript loading in ways that prevent DataTables from initializing correctly.

CSV import issues are often caused by encoding mismatches or incorrect delimiter settings. In TablePress → Import Table → Advanced Settings, select the correct character encoding (UTF-8 for standard files) and verify the delimiter matches your CSV file (comma vs semicolon — European Excel exports often use semicolons). For Excel files, save as “CSV (Comma Separated Values)” rather than “CSV UTF-8 (Comma delimited)” — the latter sometimes exports BOM characters that corrupt the first cell. Inspect the raw CSV in a text editor before importing to verify the delimiter and encoding.

TablePress provides a custom CSS field in TablePress → Plugin Options → Custom CSS. CSS rules entered here apply to all TablePress tables globally. Use the .tablepress class as the base selector: .tablepress { border-collapse: collapse; } .tablepress td, .tablepress th { padding: 8px; } For table-specific styling, use the table ID class: .tablepress-id-1 th { background: #003366; color: white; } Each table has its own ID class (tablepress-id-N) allowing per-table styling without custom shortcode parameters.

The free version of TablePress does not include responsive column hiding. Workarounds: (1) enable “Horizontal Scrolling” in Table Options — this allows the full table to be viewed by scrolling horizontally on mobile; (2) use the “Responsive Tables” extension from TablePress Extension for automatic column hiding on narrow screens; (3) manually write CSS using CSS overrides (@media max-width) to hide less important columns on mobile — target .tablepress td:nth-child(N) { display: none; } for column N on small screens.

For a standard text-based pricing comparison table (product name, features, price, CTA button), TablePress free is fully capable. The sort, search, and pagination features are more relevant for data tables with many rows than for typical 3-5 column pricing comparisons. If the pricing table needs to be visually styled (highlight a “best value” column, custom button colors), plan for CSS customization — TablePress free provides the structure, not the visual design. For very design-heavy pricing tables, a dedicated pricing table plugin like Ninja Tables or a page builder component may produce a more polished result with less CSS effort.

TablePress tables contain static data managed in the TablePress editor — they do not connect to WooCommerce product data dynamically. For displaying WooCommerce products in a table format with live pricing and stock status, a specialized plugin like WooCommerce Product Table (by Barn2 Plugins) or wpDataTables with WooCommerce integration is more appropriate. TablePress is suitable for static WooCommerce-related content like shipping rate tables, size guides, or comparison tables with manually entered product data.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.