Support

Site Restoration

#22959 Restoration problems after Joomla 3.4.3 update

Posted in ‘Site restoration’
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

PHP version
n/a
CMS Type
Other
CMS Version
n/a
Backup Tool Version
n/a
Kickstart version
n/a

Latest post by tampe125 on Monday, 13 July 2015 07:21 CDT

academiedessciences
 Hello
With two different hosts and 2 different websites, we have a problem to restore the jpa on a local server (one with AMPPS on Mac the other with Xamp on a PC) upon updating Joomla from 3.4.2 to 3.4.3

Before, everything was running smooth, but since Joomla 3.4.3, the back up made with Akeeba appears ok no error, we can unpack it fine, no error messages with the database and so on, but at the last step, when we reach the clean up stage, nothing, we have a blank front end and backend.

One website has only 1 jpa file, it is relatively small, the other ones has 2 JPA files, we tried to split into 3, it did not work... we tried to shift from Ajax to iFrame but this was impossible, it took too long, thus we stopped the process




Thanks for your suggestions

tampe125
Akeeba Staff
Hello,

Akeeba Backup will copy the whole contents of your site and then unpack them into the new location.
This means that no processing is performed on the files and/or the contents of your site; I suspect the error comes from somewhere else.

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.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

academiedessciences
Many thanks, for one site renaming the .htaccess works, but once started locally, the URLs inside the site, do not work, there is a problem with rewriting... the URL, it works if the index.php/... is added in the URLs

For the other site, so far renaming the .htaccess does not work, we ll try some more and we ll check if we see PHP errors as you suggest. We are in a congress for several days but we ll test all these next week end
thanks again

tampe125
Akeeba Staff
  1. Site n°1: if you remove the htaccess file then you have to disable URL rewriting inside Joomla, otherwise you get broken links. Please ask your host to enable support for htaccess files
  2. Site n°2: Please enable error reporting, there is something broken inside your site.


Ok, keep me updated.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
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!