This thread is resolved. Here is a description of the problem and solution.
Problem:
The customer was unable to disable a custom code in Toolset settings due to a 403 error caused by their hosting security system, which blocked Ajax requests to admin-ajax.php, labeling it as an exploit attempt. The firewall prevented changes that required Ajax, such as disabling custom code or modifying certain settings within the Toolset plugin.
Solution:
We identified the issue as being related to the firewall blocking Ajax requests. The customer contacted their host to whitelist the necessary URLs, which allowed them to enable and disable custom code successfully. However, the issue persisted when making changes to the search and pagination section in a view. As a workaround, we moved the CSS from the Search and Pagination section to the Loop CSS, and the problem was resolved, allowing the customer to save the changes correctly.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Our next available supporter will start replying to tickets in about 2.43 hours from now. Thank you for your understanding.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| - | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | 9:00 – 12:00 | - |
| - | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | 13:00 – 18:00 | - |
Supporter timezone: America/Sao_Paulo (GMT-03:00)
This topic contains 32 replies, has 3 voices.
Last updated by 2 months, 3 weeks ago.
Assisted by: Mateus Getulio.
Hi there
The message shown in the UI doesn't give details of what the error was.
If you are familiar with your browser dev tools, you could open those, switch to the Network tab, then try one of the actions like activating/de-activating a code snippet.
That will submit an ajax request. If you select that in the Network tab, you can check the Response, as shown in my screenshot (which was for a successful request).
Does that have any more details of the error?
If the request reports a 500 server error then you should be able to find details of the error in your debug.log.
If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DISABLE_FATAL_ERROR_HANDLER',true);
That will create a debug.log file in your /wp-content/ directory which you can examine in any text editor. Try the action again that triggers the error, then inspect the log.
Let me know what you find.
Also, I expect this problem likely occurs because of some conflict with code from another plugin or your theme. You could confirm that by disabling non-Toolset plugins and switching theme and trying again, in which case it should be possible to determine the source of the conflict by a process of elimination.
