Support

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 I 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 and go to the last page. The last log entry should have the date and time of when the issue occurred. Please copy the Reason and Target URL here so that I can 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.

Did you recently upgrade from Joomla! 2.5.11 or earlier to 2.5.14?

All right, join the club. There is an issue that happens when your #__assets table is broken. Due to a bug in Joomla! up to 2.5.13 your site would load even with a broken #__assets table. That bug also caused a huge performance issue so it was fixed. And that's when sites with broken #__assets table stopped working properly. I've been there, our site was one of the affected :(

Temporary solution: edit the #__assets table, find the Root Asset node and set lft=0 (now it's lft=1).

Proper solution: subscribe to ACLManager.net and use ACL Manager to fix your assets table. If that doesn't work Sander will provide you with support in fixing any remaining issues with your assets table.

Even though I have not found any issues with the temporary solution I am aware that it's fixing the symptoms, not the problem. I cannot guarantee that it doesn't cause some unforeseen issue with a future version of Joomla!.

You're welcome!