Support

When you have a very long process (too many files in the tmp directory, too many files/folder levels when fixing permissions, over 50 tables when repairing tables) the progress bar may keep on reloading but stick to the same percentage, appearing as though it never moved at all. This is normal and if left there for a few minutes, it should complete the process.

This works in all browsers EXCEPT Firefox 8 and later. These versions of Firefox are buggy like hell and instead of loading the action page in a modal dialog, they load it in the main window. My suggestion: stop using Firefox! Firefox is the new Internet Explorer: each new version is more bloated, slower, less stable, worse in rendering pages than the previous one and it now disregards common Javascript conventions, the same ones which it followed in previous versions and caused IE and other browsers to adhere to them. Shame on Firefox, it has become a piece of utter junk. So, if something works on Chrome, Safari, Opera and IE9 but breaks in Firefox, I simply won't fix it.

Same browsers, PHP versions and Joomla! versions here as well. The problem is certainly not in Admin Tools' code. It could be a misbehaving Internet security or antivirus programme (AVG Antivirus and it's link checker sorry excuse of a feature are known to kill JavaScript regularly, even on local hosts), a browser plugin which interferes, or even a system plugin in your site screwing up JavaScript. One way to find out is to send me a Pm with Super Admin access to your site and I will tell you what's wrong.

Hi guys,

some hosts have strict limitations. Things like a tight max_execution_time, memory_limit or a very aggressive CPU quota (all far too common on shared hosts) will cause the file scanner to fail. The file scanner is based on the same engine as Akeeba Backup. The difference is that instead of backing up the files, we throw away non-PHP files and run a scan on PHP files. The scan is even more CPU and memory intensive than the backup, so the scanner has a high chance of failing.

The only workaround: move to a decent host. I simply can't work around unrealistic restrictions imposed by hosts who cram 3,000 sites on a single server they bought back in 2005. It's 2012. Our sites have completely different requirements than seven years ago. Is it a coincidence that my software never failed cold on decent hosts like CloudAccess.net, iRedHOST and Rochen – unless the user did something really wrong? I don't think so :)

PS: Saying that you have the "latest" version of PHP is most unhelpful, guys. At the time of this writing, the "latest" version can be 5.2.17 (latest PHP 5.2), 5.3.9 (latest PHP 5.3) or 5.4.0.RC5 (latest PHP 5.4). It could also be PHP 5.1.6 (the latest version Debian stable provides). Or they could be the latest versions provided by your particular pre-packaged server environment, which cover a wide spectrum of all versions from PHP 5.2.9 to 5.3.6. So, which is the "latest" version you have? Same for MySQL. Based on your "latest" non-numbers I am left to wonder which of the hundreds possible combinations of "latest" PHP/MySQL could be. You could just as well not mentioned anything. Next time I see "latest", I swear I will reply "RTFM" and delete the thread :)