Hi guys,

To begin, I want to extend my heartfelt apologies for the delayed reply, 

which is due to an unexpectedly high volume of inquiries. 

We truly value your patience during this period.

-

@Frank, 

We have responded to your ticket https://tmsplugins.ticksy.com/ticket/3493787/.

We are not sure if you have the same error as Harihar has here;

Here we got a more detailed error message in Private,

on this Site they have a "403 (Forbidden)" error when trying to generate a Table.

I will elaborate what happens, about our Admin-Ajax Calls for Tables in general,

and what it means when you get a 403 error.

-

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)

@Hariar,

Now, this does not mean you guys have the exact same issue,

but you can check this by opening your Browser Developer Console ( For Chrome the hotkey is F12),

then open the Network Tab, and keep it open when you try to do the step for the issue.

After that, see the red text 403 error ( or if it is another error, such as error 500),

then click in the text of the Error, and open the "Preview" Tab.

If you see something like this :

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. 

Please let us know if you reach out to your hosting support if they shed some light on this matter.

Thank you.

Hi Hariar,

We will be on stand-by, let me know how it goes with the hosting support.

Thank you.

Hi Hariar,

In that case, please reach out to the Hosting Support, and you can pass all the details i explained in the previous response where i went in more details about how our Admin-Ajax call works,

and they should be able to help you find what is blocking it and solve the issue via their Firewall.

I hope that helps.

Hi Hariar,

Just following up to check the status.

I hope that the issue is fixed by now.  We will be on stand-by, let us know if we can provide any additional advice or guidance on the matter.

Thank you.

Hi Hariar,

You're welcome.

We will be here if you require any further assistance from our end.

Thank you.