Support

Admin Tools, Web Application Firewall, Configure WAF, Cloaking, set “Block template=foo site template switch” to No.

This is actually a bug / wrong implementation in Joomla's com_ajax. It uses the URL parameter template to communicate which site template it will load to execute the AJAX call but this is actually a reserved Joomla system parameter which is meant to change the site template used to display the page. By repurposing a system parameter it causes a few problems, most of which are invisible and nobody caught them during testing when com_ajax was first implemented. Second order side-effects include security extensions, like ours, blocking that parameter unless otherwise configured. Hence the need to change something in your configuration.

Are you using the .htaccess Maker? If you do, you need to add

templates/corporation/settings/themes/theme.corporate.json

to the "Allow direct access to these files" area.

Moreover, in the Configure WAF page you need to change the "List of allowed tmpl= keywords" to

component,system,raw,koowa,ajax

That is, add a comma and the lowercase word ajax to the end of the comma-separated list there.

Let's make sure that the problem is indeed caused by Admin Tools. In order to do so, try the following:

1. Try setting the Error Reporting level in your Global Configuration to "None". Many errors are caused by harmless PHP Notices and Warnings being output to the browser, breaking anything which requires HTTP header manipulation such as Joomla!'s session management, AJAX calls and download systems.

2. Try to replicate the issue after disabling the "System - Admin Tools" plugin. If you can still replicate the issue, it is not caused by Admin Tools. Disabling that plugin means that Admin Tools code (including the Web Application Firewall) is not running on your site.

3. If you suspect an issue with the .htaccess file, replace its contents with the contents of the stock htaccess.txt file shipped with every version of Joomla!. If you are on GoDaddy please wait for 1-30 minutes for the changes to be effective. Then, retry loading the problem page. If you can still reproduce the error, then it is not caused by .htaccess Maker.

If doing any of the above resulted in the issue still occurring, it's not related with Admin Tools and we can't help you. If doing any of the above did stop the issue from occurring, we'll have to do some troubleshooting.

First go to Admin Tools, Web Application Firewall, Configure WAF. Make sure "Log security exceptions" is set to Yes; if it's not, set it to Yes and click on Save. Now try reproducing your issue. Immediately after that, please go to Admin Tools, Web Application Firewall, Security Exceptions Log. The latest log entry at the top should have the date and time of when the issue occurred. Please copy the Reason and Target URL here so that we can further help you.

If, however, you do not see a log entry, or the Date and/or IP address do not match your last access, this problem is not caused by Admin Tools' WAF. In this case, you will have to do some .htaccess troubleshooting. You may need to read the general .htaccess troubleshooting page, as well as the page on finding out necessary .htaccess exceptions.

You're welcome!