Support

Site Restoration

#14715 After restore with Kickstart, I see a white backendpage after login

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 nicholas on Monday, 21 January 2013 02:27 CST

WoodyF4u

Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?Yes
Joomla! version: 2.5.8
PHP version: (unknown)
MySQL version: (unknown)
Host: deheeg.nl
Akeeba Backup version which took the backup: 3.6.12
Kickstart version used to extract the backup: 3.6.0

Description of my issue:
I have created a backupfile at my testsite.
Then I've uploaded the file and kickstart.php to the new domain.
When I start Kiickstart.php I see an error on top of the first screen of Kickstart.

This is the error:
==============================

Warning: is_file() [function.is-file]: open_basedir restriction in effect. File(..) is not within the allowed path(s): (/www/htdocs/andereko:/tmp:/usr/local/lib/php) in /www/htdocs/andereko/kickstart.php on line 5964
==============================

When I finish the Kickstart-actions, the front-end is running wel.
I can login at the back-end, but the screen is white after login.

What can I do to fix it?
Thanks for your support.

Regards,
Wouter
The Netherlands

Best regards,
Wouter (WoodyF4u)

nicholas
Akeeba Staff
Manager
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!

WoodyF4u

Thanks for your reply.
I think this host is not very frindly for Joomla!
There was a Joomla! 1.5 site running there at that account, so I hoped they are Joomla! 2.5 ready.
I will send the hoster a question about the PHP they use at the moment.
As soon as I know more about that, i will post the results here.

Β 

Best regards,
Wouter (WoodyF4u)

WoodyF4u

Hi Nicholas,
Later today, the provider changed PHP.
It was 5.2 and it is now 5.3.

I've done the procedure with Kickstart again.
I saw the same error about line 5964 of Kickstart.php

I continued the Kickstart and now my site is running well in frontend and backend.
No white screens in the backend anymore.

What do you think about the error?
Is it something of Kickstart.php or is there something more wrong at the server of the provider?

Regards,
Wouter

Best regards,
Wouter (WoodyF4u)

nicholas
Akeeba Staff
Manager

Hello Wouter,

The restoration of the site was completely irrelevant to your issue. PHP 5.2 is a dead version of PHP. It has been end-of-life since January 2011. Yes, two years ago; in computer terms that's a lifetime! In the meantime most software has been designed to require PHP 5.3 or later. That's why restoring your site on a host running on PHP 5.2 doesn't work and why your host upgrading to PHP 5.3 solved the issue.

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!

WoodyF4u

Hi Nicholas,
I know about the idiot way of servermaintanance by this hoster.
The problem is, the customer did paid for another yaear in Dec. 2012.
They don't have the money to switch and pay duble.
That's why I will try to run the site there.
When I posted my first question about this error, I didn't know they were rubnning that old PHP.

The only question I have now is about the errorline.
When I did start Kickstart.php, i saw the errorline at the first page on top.
Even with PHP5.3.19
Did you have received more questions about that error?

Regards,
Wouter

Best regards,
Wouter (WoodyF4u)

nicholas
Akeeba Staff
Manager

What you saw is not an error. It's a warning. But don't worry about it. Kickstart is simply "testing the water", trying to see which backup archive files are available for extraction.

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!

WoodyF4u

Wow, that's very fast!!!
OK, I understand what you mean.
I looks the site is moved with Akeeba backup and Kickstart very good.
If the message is a warning and it is nothing more than that, then we can close this ticket.

Thanks again for your support and your very good extensions.

Regards,
Wouter

Best regards,
Wouter (WoodyF4u)

nicholas
Akeeba Staff
Manager

You're welcome, Wouter :)

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!