Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by nicholas on Thursday, 23 April 2026 10:28 CDT
When using the Live Builder feature of the Avada theme you cannot save the changes. Save button keeps spinning.
This is caused by blocking the admin-ajax.php script.
I've temporarily disabled AdminTools and the problem does not occur.
Is there a way to give acces to the admin-ajax script in this case?
PS: I know that in general the admin-ajax is excluded and accessible but it appears that this is always not the case.
Thank you for the report.
When Admin Tools "excludes" admin-ajax.php, it means the URL itself is never outright blocked — but the WAF still inspects the content of requests sent to it. In your case, the Avada Live Builder is likely sending POST data that triggers one of the WAF's content-inspection rules (e.g. SQLiShield).
To pinpoint the exact rule, please do the following. Go to Admin Tools → Web Application Firewall → Blocked Requests Log. Reproduce the problem (try to save in Avada Live Builder), then refresh the log. You should see a new entry. Note the Reason column — that's the rule that fired.
If you give me the Reason and Target URL I can most likely help you.
Just in case I need more information, you can also open your browser's DevTools (F12), go to the Network tab, and reproduce the save. Find the failing admin-ajax.php request. Click on it and look at the Request tab — this tells us which data was sent to your server. Copy it into a plain text (.txt) file which you can attach with your next reply.
Once I have all the information I can suggest a solution.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Nicholas,
Thanks for the quick response.
I've reproduced the error but there is no log entry in the blocked request list...
The only error I have is in the console (see TXT file).
I see an Internal Server Error (HTTP 500), so it's not actually getting blocked, PHP is crashing out with an error. Can you check your PHP error log and give me the error message and debug backtrace listed there for the request that failed?
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Only error logs I have are from the Plesk logs. There I see the following:
2026-04-23 14:15:25 Error 149.143.107.27 500 POST /wp-admin/admin-ajax.php HTTP/1.0 https://tmpcontrol.maxigraphx.nl/sectoren/?fb-edit=1 Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36 3.93 K SSL/TLS-toegang tot Apache
2026-04-23 14:15:28 Error 149.143.107.27 Premature end of script headers: admin-ajax.php, referer: https://tmpcontrol.maxigraphx.nl/sectoren/?fb-edit=1 Foutmelding van Apache
2026-04-23 14:15:28 Error 149.143.107.27 AH01070: Error parsing script headers, referer: https://tmpcontrol.maxigraphx.nl/sectoren/?fb-edit=1 Foutmelding van Apache
2026-04-23 14:15:28 Error 149.143.107.27 (22)Invalid argument: AH01075: Error dispatching request to : , referer: https://tmpcontrol.maxigraphx.nl/sectoren/?fb-edit=1
If I deactivate the AdminTools it is working perfectly.
This is the Apache (web server) error log. We need the PHP error log. Please ask your host to help you find it. Without the exact error message I cannot tell you what is wrong.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.
Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!