Support

The one thing which should not have anything to do with that is the .htaccess file.

Do you have an IP block on his IP? You will need to remove him from it if you do.

Do you have an Administrator IP whitelist? You will need to add him there if you do.

Do you have an administrator secret word? You will need to supply it to him.

Do you have administrator password protection? You will need to give him the username/password to see the login page.

Then I am pretty sure the problem is unrelated to Admin Tools. I'll give you the benefit of doubt. 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.

PS: Regarding the browser. The font size 10pt and I can read it, with -3.75/-4.00 degress on each eye and rather old glasses, from 2 meters across the screen on my 15" screen. BTW, in case you missed it, it's the exact same font and size as the editor in your Joomla! backend. In case you also missed it, it's the same size as the letters in the site, albeit solid black instead of dark gray (for better contrast). Not to mention, of course, that you can always use your browser's zoom-in feature: CTRL-+ (Windows, Linux) or CMD-+ (Mac) ;)

Hi Lowtech,

If you don't spend time you'll never know what prevented your user from entering to the backend. It could be the Project Honeypot integration thinking that your other admin has an IP address suspicious for spamming/cracking. It could be the Bad Behaviour kicking him out because, for example, your other admin has installed a User Agent switch extension on his browser and he has set up his browser to pretend to be GoogleBot. There are so many stupid things a third party can do, all the while saying "no, no, I didn't do anything!". I don't have a crystal ball and I don't expect you to have it. Magic left aside, you have to do some troubleshooting, using my very clear, dead easy, extremely quick to carry out instructions:

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.

It should take you all of 2 minutes to carry them out and I could give you a solution or at the very least an explanation of what is going on. So, please, don't sound annoyed that you don't know what happened or if it's a generic issue. If you spend 2 minutes you can find out. Otherwise I will ahve to spend about 5 hours theorising what could have gone wrong and you would have no way to check if my theories are right, wrong or plausible.

Regarding the editor: this is not how the editor is styled. Which browser are you using?

OK, the "Admin Whitelist" means that the IP of that third party is not in the administrator IP whitelist. See the third point in my first reply. Since you've added his IP on the whitelist it can't raise a new Admin Whitelist exception. If this happens it means one of:

• you entered the wrong IP 
• you accidentally typed a comma instead of a dot in the IP address, e.g. 192.168,0.1 instead of 192.168.0.1
• you accidentally typed whitespace before, after or in the middle of the IP, e.g. 192.168. 0.1
• his IP is dynamic

In this case you can always temporarily disable the Administrator Whitelist feature.

Moreover, if his IP got autoblocked you must remove it using the Auto IP Block Administration page, otherwise your user will remain blocked.

Regarding the editor, it doesn't surprise me it only happens in Firefox. A lot of strange issues happen with FF  lately (ever since the 6 week release schedule was adopted) and I've stopped officially supporting it.