Hi, Diane 

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

It seems that there is either some kind of a permissions issue on your server,

or perhaps if you are using an optimization plugin that might be blocking our plugin Ajax-Admin calls for tables.

Can you tell me, do the tables load better when you are logged as Administrator - 

compared to if you try from an incognito ( or non logged tab) ,  do you get just this "spinning loader" on the table?

When i visit the page https://ngb.org/ngb-membership-breeders/ the Admin-Ajax call that is needed for this table 18 to load , is throwing an error 403 ( forbidden access error).

-

The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.

You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.

You need to contact your hosting provider because you have an issue with your permissions.

Please show them my screenshot, and tell them that this error happens when a non-logged user visits the page.

Let me know what they say/  if they help you resolve the issue. Thank you

Hi, Diane 

When i visit all of the pages, as a non logged user, i can not even load the tables at all.

It seems that i found the error causing this for all tables, and i know how you can resolve it.

There is something on your Sucuri Website Firewall that is blocking our plugin Ajax-Admin calls for tables.

This is a screenshot of the error 403 thrown on your site ( in this case, you have Sucuri Website Firewall) :

We had another couple of users,  that had this exact same issue, it was also blocked by the site firewall,

and in the end, their hosting support realised that this should not happen, so they have resolved it / lifted the block from Admin/Ajax calls for our tables.

-  But, i will elaborate more to clarify everything:

Basically, this Admin-Ajax call is a request coming from our server-side processing feature. Here are more details that explain the process :

• wpDataTables with server-side processing enabled fetches only those rows needed on the page at the exact moment. By default, it equals to the number of rows that administrator defines for the table in the “Display length” setting; the front-user can however, change it. For example: if the table is configured to show 10 rows by default, only 10 rows would be queried from MySQL. When the user switches to the next page, and sorts the table by some column, or filters by some column, an AJAX-request is sent to the server, the query is processed by MySQL, and 10 more rows are returned. This may slow down the processing, search, filtering and sorting (of smaller tables also), but for larger tables it may be the only option.

-

If you wish, you can see more about our server-side processing process here.

-

Here is the screenshot from another user who had the same "false positive" block by their site firewall ( i blurred their website and IP, just to be safe)

In their case, they have another Firewall system, by GoDaddy - but it is the same issue they had :

So, we cannot say why your site firewall blocks the admin-ajax call. 

That's a question for the hosting provider. There could be a number of reasons. 

If you search/Google for admin-ajax (https://www.google.com/search?q=what+are+admin-ajax+calls&oq=what+are+admin-ajax+calls&aqs=chrome..69i57.6300j0j4&sourceid=chrome-mobile&ie=UTF-8) 

you can find that this is one of the most common methods for routing requests,

and it is one of the most crucial methods in Wordpress.

Maybe your hosting provider is not optimized for WordPress, we can only guess why they block it,

but we don't wish to guess too much.

Until your hosting support does not resolve this, you won't be able to load server-side tables. 

If you can please reach out to them, and let me know how it goes.

Thank you.

Hi, Diane 

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

If i visit the page as non logged user,  from any device - for example, from my Desktop,

i am still getting a "forbidden access" error 403.

This is how the table looks when i visit the page as non logged user.  It just gives the "spinning loader", and the Admin-Ajax call is still being blocked by something on your site.

Here are some screenshots showing the table, and the Network Tab in the Browser Developer console :

Just that this time i am not getting a "clear" error message that points to what might be blocking access to the page.

As you see - the Admin-Ajax call that our plugin tries to make in order to pull the table for non-logged users still gets blocked for some reason.

-

If you are blocking access to non-logged users on purpose, in that case, you can leave it like this.

But if you wish to allow non-logged visitors to also see this table,  then you will have to find what is blocking our plugin's Admin-Ajax calls.

-

The 403 Forbidden Error happens when the web page (or another resource) that you’re trying to open in your web browser is a resource that you’re not allowed to access. It’s called a 403 error because that’s the HTTP status code that the webserver uses to describe that kind of error.

You usually get this error for one of two reasons. The first is that the owners of the webserver have properly set up access permissions and that you’re really not allowed access to the resource. The second reason is that the owners of the webserver have improperly set up permissions and you’re getting denied access when you really shouldn’t be.

You need to contact your hosting provider because you have an issue with your permissions.

Once you do that, please try to visit the page with  the table as non logged user, or from incognito browser mode,

and let us know if everything is back in order.

Thank you