Support

Site Restoration

#31983 White screen after restore on localhost

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 on Sunday, 15 December 2019 17:17 CST

TonyGib
Did restore onto localhost without issues then loaded site. Front page = white screen, administrator loads and works fine.
I have tried all your previous suggestions but no luck.
If on the front screen I modify the url and add a page within the system this loads without problems:
using 'http://localhost:8080/SSCzenLive/' I get white screen
using 'http://localhost:8080/SSCzenLive/weather/index2.php' it correctly loads page.

On checking system configuration I found some issues reported under Post-Installation Issues: These relate to one of your modules - do they perhaps have a bearing on the problem I've got?

Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 524



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 529



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 534



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 539



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 552



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 561



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 566



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 580



Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2"? in C:\xampp\htdocs\SSCzenLive\libraries\fof\dispatcher\dispatcher.php on line 609


Any help you can give will be appreciated.

nicholas
Akeeba Staff
Manager
The messages you get do not come from our software. They come from a very old version of FOF (2.x) which is included in Joomla itself. We discontinued FOF 2 in June 2016, more than 3 years ago. These are actually notices thrown by PHP 7.3. As far as I know, they were fixed in Joomla 3.9.12.

I'd also like to note that PHP 3.0.7 is a version from more than 20 years ago and incompatible with any version of Joomla, even 1.0.0 from 15 years ago. Is it possible that the live server's PHP version is different? If so, what is it? If it's a 7.0 release your problem might actually be that your site's extensions are too old for (therefore incompatible with) PHP 7.3.

Otherwise you can follow the standard troubleshooting procedure for white screens. 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.

If you do not know where to find these 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 Development. 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.

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!

TonyGib
Hi Nicholas,
Me being dyslexic again :( - Current live PHP is 7.0.3 not 3.0.7
What I'm trying to do is restore to local server (xampp) so I can update template and restore to live site as PHP 7.3.7.
I have rem'ed out htaccess, I have error reporting set to 'development' but don't get an error message.
So I'm stuck. I'll try disabling modules one at a time to see if I can identify the one causing the issue.
Tony

nicholas
Akeeba Staff
Manager
Did you also add the code to the configuration.php file?

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!

TonyGib
Yes I did (see pic), still just white screen. I've also attached error log and xampp status.
Any further thoughts?
Tony

nicholas
Akeeba Staff
Manager
Unfortunately there is no information there I can use :(

I know for sure that this has not something to do with the restoration itself but I want to help by pointing you to the right direction. For that to happen I need a copy of the backup archive.

Please upload the backup archive somewhere you can share a link to, e.g. Dropbox, OneDrive, Google Drive, ... Then start a new private ticket with the subject "Backup archive for ticket 31983". In the message of the ticket please say that it's the file I asked you on ticket 31983 and paste the link to the file. If I don't see the ticket my staff will assign it to me and I will take a look on it over the weekend.

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!

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!