Support

Akeeba Backup for Joomla!

#13408 AkeebaBackup - Blank/White screen after 3.6.3 Update

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Tuesday, 28 August 2012 14:51 CDT

rivermedia
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes -too many
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes -all I could find about installing
Joomla! version: 2.5.6
PHP version: 5.3.5
MySQL version: 5.5.23-55
Host: HostGator
Akeeba Backup version: 3.6.3

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.

(Because of my issue, I can not access the log file)

Description of my issue:
After upgrading to AkeebaBackup Pro 3.6.3 and accepting the default prefs, everytime I attempt to access the extension I get a white/blank screen. I can access rest of Joomla fine, just not AkeebaBackup Pro. I attempted to resinstall over the top, no luck. I removed everything related to AkeebaBackup and reinstalled fresh version 3.6.3, no luck.
Any thoughts? Thanks in advance!

nicholas
Akeeba Staff
Manager
You most likely have a partial installation. Remove the following folders:
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction
Now you can re-install Akeeba Backup.

If you still get a blank page, please note that 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.

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.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

rivermedia
Great, thanks for the direction.
I walked through your steps from the beginning, I didn't get anywhere until narrowing it down to a php Fatal Error. I checked the error_log in the /administrator/ directory and found:
[27-Aug-2012 14:25:13] PHP Fatal error: Call to undefined method AkeebaToolbar::appendLink() in /PATHTOROOT/administrator/components/com_akeeba/toolbar.php on line 260

I also noticed this error too:
[27-Aug-2012 19:24:19 UTC] PHP Warning: mcrypt_generic() [<a href='function.mcrypt-generic'>function.mcrypt-generic</a>]: An empty string was passed in /PATHTOROOT/administrator/components/com_akeeba/akeeba/utils/encrypt.php on line 376

Please let me know where we go from here. Thanks again for the assistance and the quick response!
It's guys like you, that help give us developers a good name!

For the record, yes, I deleted all the mentioned directories and reinstalled 3.6.3.
Then I renamed .htaccess to htaccess.bak

nicholas
Akeeba Staff
Manager
OK, that explains it. One of the files in libraries/fof was not updated during the last update of Akeeba Backup. Extract the com_akeeba-3.6.3-pro.zip file and copy all files from its fof directory into libraries/fof. This should fix the issue.

Regarding the mcrypt warning you can safely ignore it. It occurs when you have a "virgin" profile with no saved configuration data in it. Once you go to the Configuration page and click on Save it should go away.

Thank you for your kind words :)

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

rivermedia
That didn't seem to fix the issue. I still get this error after uploading all of fof directory to library/fof

[28-Aug-2012 12:45:54] PHP Fatal error: Call to undefined method AkeebaToolbar::appendLink() in /PATHTOROOT/administrator/components/com_akeeba/toolbar.php on line 260

nicholas
Akeeba Staff
Manager
It appears that you have a very old version of Admin Tools or Akeeba Subscriptions currently installed on your site. Can you please upgrade?

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

rivermedia
Ok, that did the trick. Thanks again!

nicholas
Akeeba Staff
Manager
You're welcome!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!