Ninja Tables plugin review and common issues

In Ninja Tables Pro → WooCommerce Table Settings, check the product visibility filters. Products may be excluded due to: (1) product status — only “Published” products appear by default; (2) stock status — out-of-stock products may be hidden if a stock filter is applied; (3) product category filter — if a specific category is selected, only that category’s products show; (4) per-page limit — the default items per page may not show all products. Increase the per-page limit and enable pagination, or set the limit to 0 for all products. Also verify “Show Hidden Products” is enabled if some products have the “hidden” catalog visibility.

Ninja Tables caches Google Sheets data to avoid excessive API calls. In the table’s data source settings, find the Cache Duration setting and reduce it (e.g., 1 hour to see updates within an hour). For an immediate sync, go to the table settings and click “Sync Now” or clear the table cache from Ninja Tables settings. If the sync is failing silently (data never updates), check: (1) the Google Sheets API key is valid and not rate-limited; (2) the spreadsheet is published/shared with view access; (3) the specific sheet tab name in the URL matches the sheet being read.

Conditional formatting in Ninja Tables Pro operates on column data values. Debugging steps: (1) verify the column type is set to “Number” for numeric comparisons — conditional formatting on “Text” type columns uses string comparison, not numeric; (2) check the condition operator matches your data — “greater than” vs “greater than or equal to” is a common mistake; (3) ensure the rule is saved and the table is re-published after creating the rule; (4) clear all caches — cached table HTML will not reflect newly added conditional formatting rules until the cache expires or is cleared.

Go to Ninja Tables → Add New Table → WooCommerce Products data source. Select which WooCommerce product attributes, meta fields, and taxonomy terms to include as columns (price, stock, SKU, weight, custom attributes). Configure sort and filter options for the columns customers are most likely to use for comparison. Style the table using Ninja Tables’ built-in theme presets for a professional appearance. Embed via shortcode on a product comparison page. For per-product Add to Cart buttons in the table, use Ninja Tables’ WooCommerce Button column type in the Pro version.

In Ninja Tables Pro, when creating a new table, select “External JSON Feed” as the data source. Enter the JSON API URL. Configure the JSON path to the array of records (e.g., “data.items” if the array is nested under those keys). Map each JSON field to a table column by configuring the Column Key to match the JSON property name. Set the cache duration for how frequently the table refreshes from the API. For APIs requiring authentication headers, configure the Authorization header in the API settings. The table will display live data from the JSON endpoint, refreshing on the configured schedule.

For visual styling without CSS customization, Ninja Tables free is generally more attractive out-of-box. TablePress free has more features in its free version (better DataTables integration, more import/export options) but requires CSS work to look polished. If visual design matters more than feature depth, Ninja Tables free produces a more presentable table faster. If data management features (CSV import, formula support, formula-based cells) are the priority, TablePress free is the stronger choice.

Ninja Tables does not include front-end editing functionality for visitor-facing tables — it is a display-only plugin from the visitor perspective. For front-end table editing (allowing users to add or modify rows), wpDataTables Pro has a dedicated front-end editing feature. Alternatively, integrate Ninja Tables with a form plugin (Fluent Forms, which is made by the same team) to allow data submission through a form, with the submitted data appearing in a connected table.

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.