Support

Site Restoration

#18397 site restore only displays plain html page

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

Joost
 After problems with a website which was upgarde to joomla 2.5.16 we tried to install a backup of this site in joomla 2.5.14 as a subdomein for testing purposes. But we only get a plain html page with the not-working menu's. We went trough al the troubleshootingpages, re-installed twice after using the latest version of kickstart but noting seems to work.

nicholas
Akeeba Staff
Manager
I guess that by "plain HTML" you mean that the CSS is not loaded. In this case you should be reading this troubleshooter page: https://www.akeebabackup.com/documentation/troubleshooter/prbasicts.html

If you have used Admin Tools' .htaccess Maker please remember that after restoring the site to a different location you will need to go to Components, Admin Tools, .htaccess Maker, then change the domain and directory names at the bottom of the page and finally click on Save & Create .htaccess. This is mandatory every time you move your site.

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!

Joost
I have tried it all your tips but nothing works. I also followed your instruction about admin tools althought we did not use it for htaccess maker. But we guess this instruction is for the settings in the backoffice?
Our site is still flat without showing any css and the adminsitrator page stay compleet blank!

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.

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.

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!

Joost
Hi, I Check all your instructions and tested it without any result.
The error report says (no idea what it means):
[Tue Dec 03 22:47:58 2013] [error] [client 194.123.134.51] Cannot load Zend Extension Manager - it was built with configuration 1.2.0, whereas running engine is API220090626,NTS, referer: http://montessori.studiodrijvers.nl/index.php
[Tue Dec 03 22:47:58 2013] [error] [client 194.123.134.51] PHP Deprecated: Directive 'magic_quotes_gpc' is deprecated in PHP 5.3 and greater in Unknown on line 0, referer: http://montessori.studiodrijvers.nl/index.php
[Tue Dec 03 22:47:58 2013] [error] [client 194.123.134.51] <br />, referer: http://montessori.studiodrijvers.nl/index.php

What I do know is that the original website and the installation of the backup as a subdomain are both running in MSQL version 5.1.47 and PhpMyAdmin version 2.8.2.4

nicholas
Akeeba Staff
Manager
Actually, no error is reported. I would recommend removing the .htaccess file from the restored site's main and "administrator" folders and retry accessing your back-end.

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!

Joost
Problem solved, my provider discovered that the live path was wrong. This was stored in configuration.php document. Mistake was made while reinstalling the site. Once more everyone including myself started thinking too complicated. I was not aware of this tiny little **#@!**issue so I learned again. Thanks for the support anyhow. Without it I wasn't put on the right track!

nicholas
Akeeba Staff
Manager
Now that you solved that, please read https://www.akeebabackup.com/documentation/troubleshooter/prbasicts.html again. Take a look under "THE $LIVE_SITE VARIABLE IN CONFIGURATION.PHP". And please answer this question I have: when I told you to please read that document, did you even click on the URL?

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!

Joost
Hi Nicholas, sure did I click on the link you send en sure I did read al the instructions, I just overlooked one thing: I installed the website as a subdomain not in a subdirectory. And I added index.php behind it which i shouldn't have done. I just overlooked this, sorry, Iam not an allround PHP specialist, mor a designer.

Support Information

Working hours: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.