Support

EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.

Description of my issue:

I've just upgrade to J2.5.16 and Akeeba Backup 3.9.1
I wanted to fix the Google Recaptcha trouble and found a patch here : http://seepeoplesoftware.com/downloads/patches/patches-recaptchafix1-0.html

But when trying to install it, Akkeba backup shows a Error 500 after doing his Restore Point and I couldn't install the patch.
I tried to temporary disable Restore Point in the Joomla Extension Installation page but it seems it doesn't work.
I finally disable the System plug in and I could install the patch. After that I enable the plugin again.
I don't who of Akeeba Backup, Joomla or the patch installation package is responsible of that but I wanted you to know this issue.

Thanks for your backup component which is really great and useful.

It seems that Restore Point when upgrading a template/plugin/component doesn't work in Akeeba Backup 3.9.1 with Joomla 2.5.16.
I had the same Error 500 (invalid controller akeeba) when trying to install other stuff.
Would you mind to see what's going wrong?
Thanks

First, let's make sure we don't have a problem with the Backup installation. Please install Akeeba Backup 3.9.1 twice. Do not uninstall the extension, that will remove your settings and possibly your stored backups. If you are still getting the 500 error, we'll have to get Nicholas involved.

I've downloaded an other time the AkeebaBackup 3.9.1.zip archive from your site, installed it twice on two Joomla 2.5.16 web sites (using PHP 5.3.16) and it still the same.
When installing or upgrading a plugin/component/template with the Joomla extensions installation page, I have a ERROR 500 at the end of the restore point process and can't achieve the installation.

Backup 3.9.1 and Joomla! 2.5.16 should be a good combination. Let's see if we can get any additional information on the 500 error.

A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

First, let's see if it is a .htaccess issue. Try renaming the .htaccess file in your site's root to htaccess.bak If there is a .htaccess file in the site's administrator directory, try renaming it as well. If that solves the problem, the issue was with a directive in your .htaccess file. We'd like to recommend you to try removing directives from your .htaccess until you find the one which causes the problem.

If that doesn't help, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Maximum (Joomla! 1.5) or Development (Joomla! 2.x and later). Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):

ini_set( 'display_errors', true );
error_reporting( E_ALL ); 

Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:

php_flag display_errors On
php_value error_reporting 32767

and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:

display_errors=on
error_reporting=E_ALL

and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

IMPORTANT: Sometimes the error won't show. Edit your configuration.php and find the line starting with public $error_reporting and set it to:

public $error_reporting = 'development';

This instructs Joomla! to enable maximum error, warnings and notices verbosity. In 99.9% of cases it will result in the error messages being shown on the browser.

If you still get a white page, delete the php.ini files your created and choose a different host. If your host doesn't allow you to debug any PHP-related issues there is no point paying them.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.