Ninja tables not loading unless Jetpack is deactivated

Do you think you could activate Jetpack again for a few minutes, and check for JavaScript errors on the page, that may break the display of some of the blocks on the page?

Here is how you can check for such errors:

Using Your Browser to Diagnose JavaScript Errors

Let us know what you find!

Here’s a follow-up:

First, only the activation of the Jetpack plugin does not cause the table to cease loading. It does so after Jetpack is set up.

I followed the steps in the link you provided.

Step 1, different browser: no difference, table will not load

Step 2, enabling script debug: no difference, table will not load

Step 3, diagnosis, reveals the following error:

footable.min.js?ver=3.1.5:8 FooTable: unhandled error thrown during initialization. Error: Rows ajax request error: 200 (parsererror)
at Object.<anonymous> (footable.min.js?ver=3.1.5:9)
at mightThrow (jquery.js:3762)
at process (jquery.js:3830)

In addition to the above: the table will load correctly with the Jetpack plug activated and Jetpack setup, when I am logged in to WordPress. However, it will not once I am logged out and therefor will not be available to anyone visiting my website.

• This reply was modified 3 years, 9 months ago by Clear Skies.

Thank you!

footable.min.js?ver=3.1.5:8 FooTable: unhandled error thrown during initialization. Error: Rows ajax request error: 200 (parsererror)

I don’t believe this error is related to our problem at hand; I saw it earlier, when Jetpack was not active on your site. It seems to be an issue with the Ninja Tables plugin itself.

the table will load correctly with the Jetpack plug activated and Jetpack setup, when I am logged in to WordPress. However, it will not once I am logged out and therefor will not be available to anyone visiting my website.

This is odd. I actually see a table when I access your site right now, and Jetpack is still active:

Is this the table you don’t see when you’re logged out, or is this another table?

No, it’s the table at the bottom of the page, where an infinitely spinning arrow is displayed at the position of the table that will not load.

Ah, I see it now, thank you!

Could you try to deactivate Jetpack again, and try to access your site in a new incognito window? Do you still see the JavaScript error you mentioned above? Is the table displayed then?

If both issues have disappeared, it may be worth activating Jetpack again, and then going to this page and deactivating each feature, one at a time, so we can figure out what part of Jetpack is conflicting with the table.

Let us know what you find!

When Jetpack is deactivated, the table loads, as described above. When Jetpack is activated and set up, the table will not load.

That being said, I tested it with Jetpack activated and set up, in an incognito window. This error resulted:

footable.min.js?ver=3.1.5:8 FooTable: unhandled error thrown during initialization. Error: Rows ajax request error: 200 (parsererror)
at Object.<anonymous> (footable.min.js?ver=3.1.5:9)
at e (jquery.min.js:2)
at t (jquery.min.js:2)

Follow-up: deactivated each feature. Table will not load.

Jetpack seems disabled on your site at the moment, but I still do not see the table, and still see the error. It would indicate that the problem is not linked to Jetpack:

This seems to happen because this AJAX call, apparently used to fetch data to populate the table, does not return any data unless you are logged in:
https://clearskies.eu/wp-admin/admin-ajax.php?action=wp_ajax_ninja_tables_public_action&table_id=4269&target_action=get-all-data&default_sorting=old_first&chunk_number=0

Jetpack would not block AJAX requests like this, but that request may be blocked if you’ve used a security plugin on your site that added code to block such unauthenticated queries. Do you, or have you used such a plugin in the past?
It may also be worth reaching out to NinjaTables again, and let them know about that failed AJAX request when logged out; they may have run into similar issues with others customers in the past.

I hope this helps.

Jetpack is indeed disabled at this time.

The table loads fine when I am logged out of WordPress, in Safari, Chrome and Firefox in and Safari in iOS (have not tested Chrome or Firefox on iOS).

I will tinker with other plugins to see what happens.

Follow-up: I do not have any plugins that block any queries. None of the other plugins seems to be a factor.

The table loads fine when I am logged out of WordPress, in Safari, Chrome and Firefox in and Safari in iOS (have not tested Chrome or Firefox on iOS).

I currently see the problem in Chrome, Safari, and Firefox, on a Mac. The problem is the same in all browsers: no data is returned by that AJAX call, that just returns a 403 (forbidden) error.

If it works on your end when logged out, I’m not quite sure what to make of it. Here is what comes to mind:

• It could be that the data is cached in your browser.
• It could be that the calls are blocked for specific countries, like mine. I tested accessing the site from 3 different European countries, and that query was blocked every time. I find it weird that a country block would be applied to only that query though.

At this point I’m afraid I can only encourage you to reach out to NinjaTables with that information. They have more experience with their plugin and may have had customers running into this issue in the past.

Thank you for all your replies and your insight. It is a nasty bug indeed…

For now, I will keep Jetpack deactivated.

Can you please check whether or not the table now loads for you?

Caching is not an issue here: I can reproduce the problem in any browser, simply be activating/deactivating the Jetpack plugin.

The folks at Ninja Tables are following this, hopefully a solution will follow.

Can you please check whether or not the table now loads for you?

No, it still doesn’t.

Thanks. That means that, along with the Ninja Tables vs. Jetpack issue, there is definitely a regional issue, too.

That means that, along with the Ninja Tables vs. Jetpack issue, there is definitely a regional issue, too.

I don’t believe the problem is related to Jetpack at all, to be honest. As we can see on your site, the problem appears whether Jetpack is active or not. To confirm this, I installed the Ninja Tables plugin on a test site of mine, imported this test table, and added to a page alongside an Image Compare block provided by Jetpack. The table was accessible whether I was logged in or logged out:

The 2 plugins consequently seem to work well together, but something else on your site appears to block some of the queries and break the table.

It may be worth looking for anything that filters queries on your site: Web Application Firewall, .htaccess edits, other plugins, security measures put in place by your hosting provider, … Maybe your hosting provider can help you narrow things down a bit?