Blank pages after restore backup after failed installation 2.1.1

[jacbier]

Yesterday I was installing the upgrade 2.1.1 on www.hobbybrouwen.nl/forum

That caused problems due to a lot of server timeouts I got. (It's a very large forum.) Tried several times to connect to the server but at one point installing the upgrade really wouldn't go any further. That's why I aborted the upgrade.

Before the upgrade I had made a backup of my 2.0.19 forum with various mods.
After restoring the backup I get white pages.
The error log shows the following errors

Backend log: PHP Notice:  Undefined index: default_theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 109\n
[Fri Feb 18 15:56:15.358213 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: images_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 110\n
[Fri Feb 18 15:56:15.358497 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 89\n
[Fri Feb 18 15:56:15.358506 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 90\n
[Fri Feb 18 15:56:15.358514 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: default_theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 105\n
[Fri Feb 18 15:56:15.358521 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 106\n
[Fri Feb 18 15:56:15.358529 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 108\n
[Fri Feb 18 15:56:15.358537 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: default_theme_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 109\n
[Fri Feb 18 15:56:15.358545 2022] [lsapi:warn] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend log: PHP Notice:  Undefined index: images_url in /xxxxxxxxxxxxxxxxxxx/Sources/Load.php(2336) : eval()'d code on line 110\n
[Fri Feb 18 15:56:15.358554 2022] [lsapi:error] [pid xxxxxx] xxxx [host www.hobbybrouwen.nl] Backend fatal error: PHP Fatal error:  Uncaught Error: Call to undefined function cls_change_theme_top() in /xxxxxxxxxxxxxxxxxxx/Sources/Subs.php:3428\nStack trace:\n#0 /xxxxxxxxxxxxxxxxxxx/Sources/Subs.php(2868): template_header()\n#1 /xxxxxxxxxxxxxxxxxxx/Sources/Errors.php(337): obExit(NULL, true, false, true)\n#2 /xxxxxxxxxxxxxxxxxxx/Sources/Errors.php(161): setup_fatal_error_context('Call to undefin...')\n#3 /xxxxxxxxxxxxxxxxxxx/index.php(132): fatal_error('Call to undefin...', 'critical')\n#4 [internal function]: {closure}(Object(Error))\n#5 {main}\n  thrown in /xxxxxxxxxxxxxxxxxxx/Sources/Subs.php on line 3428\n


What do I need to do to make 2.0.19 work? After that I can make a second attempt to install 2.1.1

[Shades.]

How did you backup? Admin or phpmyadmin?

[Kindred]

you need to restore BOTH files and database.

[Illori]

What is repair_settings.php?

Looks to me like your paths may be incorrect.

[Arantor]

I'd speculate on a mod having template changes but the underlying file not being loaded for it...

[Sir Osis of Liver]

If the 2.0.19 database backup is complete and undamaged, you can upload clean 2.0.19 files, that should get you up and running, then try 2.1 upgrade again.

https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files

[jacbier]

How did you backup? Admin or phpmyadmin?

How did you backup? Admin or phpmyadmin?

I made a backup with phpmyadmin and a backup was made by the hoster. Both don't want to work

[jacbier]

you need to restore BOTH files and database.

I did...

[jacbier]

What is repair_settings.php?

Looks to me like your paths may be incorrect.

Does this work if you have blank pages?

[jacbier]

If the 2.0.19 database backup is complete and undamaged, you can upload clean 2.0.19 files, that should get you up and running, then try 2.1 upgrade again.

https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files

I will try this tomorrow.


Are there more solutions possible?

[jacbier]

I'd speculate on a mod having template changes but the underlying file not being loaded for it...

I suspect so too. Any idea how to fix that outside of a fresh set of files?

[Doug Heffernan]

I'd speculate on a mod having template changes but the underlying file not being loaded for it...

I suspect so too. Any idea how to fix that outside of a fresh set of files?

It is hard to say if we do not know what mod causes that. Can you post the list of all mods that you have installed?

What method did you use to make the backup btw?

[Illori]

What is repair_settings.php?

Looks to me like your paths may be incorrect.

Does this work if you have blank pages?

yes it does.

[jacbier]

I'd speculate on a mod having template changes but the underlying file not being loaded for it...

I suspect so too. Any idea how to fix that outside of a fresh set of files?

It is hard to say if we do not know what mod causes that. Can you post the list of all mods that you have installed?

Google Member Map
Responsive Curve
SimpleAds
Country Flags
Personalized BBC
EU Cookie
Search Focus Dropdown
Users Online Today
Copy Topics
Recent Topics On Board Index
Upload mod exclusief voor Hobbybrouwen.nl
Aeva ~ Auto-Embed Video & Audio
SMF Gallery Lite
Simple Audio Video Embedder
Tapatalk SMF 2.0 Plugin
SMF 2.0.19 Update
Tabular
Tagging System
Google Analytics Code
Stop Spammer
Confirmation message to Mark as Read
nCode Image Resizer
SMF Theme Changer

I suspect the mod SMF Theme Changer is the culprit.

What method did you use to make the backup btw?

How did you backup? Admin or phpmyadmin?

How did you backup? Admin or phpmyadmin?

I made a backup with phpmyadmin and a backup was made by the hoster. Both don't want to work

[pikeman]

Was maintenance mode turned on before the update?
If yes check config file, it should be set: $maintrance=0; .

[Doug Heffernan]

I suspect the mod SMF Theme Changer is the culprit.

Refreshing your forum files with those from the large upgrade 2.0.19 package, (make really sure that your db and forum files are of the same smfseries), will uninstall your mods automatically and should fix the errors.

Then re-install them one at a time till you find the culprit.

[Arantor]

I was expecting to see a mod with initials around 'cls' but don't see anything that fits :-/

[jacbier]

Was maintenance mode turned on before the update?
If yes check config file, it should be set: $maintrance=0; .

Where can I find that file?

[Arantor]

That file is the master Settings.php file in the main directory of SMF - in it should be a line like that that says $maintenance = 0; or similar. 0 means no maintenance, 1 means soft maintenance (like you set in the admin), 2 means upgrade maintenance but that's not what you're seeing here.

[pikeman]

Setings.php

Code Select Expand

########## Maintenance ##########
# Note: If $maintenance is set to 2, the forum will be unusable!  Change it to 0 to fix it.

########## Maintenance ##########
/**
 * The maintenance "mode"
 * Set to 1 to enable Maintenance Mode, 2 to make the forum untouchable. (you'll have to make it 0 again manually!)
 * 0 is default and disables maintenance mode.
 *
 * @var int 0, 1, 2
 * @global int $maintenance
 */
$maintenance = 0;

        # Set to 1 to enable Maintenance Mode, 2 to make the forum untouchable. (you'll have to make it 0 again manually!)

[jacbier]

I suspect the mod SMF Theme Changer is the culprit.

Refreshing your forum files with those from the large upgrade 2.0.19 package, (make really sure that your db and forum files are of the same smfseries), will uninstall your mods automatically and should fix the errors.

Then re-install them one at a time till you find the culprit.

I will do a refresh tomorrow for 2.0.19.
If the forum works then I'll go straight to 2.1.1

But first I try to adjust the config.

[Doug Heffernan]

I suspect the mod SMF Theme Changer is the culprit.

Refreshing your forum files with those from the large upgrade 2.0.19 package, (make really sure that your db and forum files are of the same smfseries), will uninstall your mods automatically and should fix the errors.

Then re-install them one at a time till you find the culprit.

I will do a refresh tomorrow for 2.0.19.
If the forum works then I'll go straight to 2.1.1

But first I try to adjust the config.

The upgrader will give you the option to close off the forum automatically when being called. But if you want to do that yourself, it is best you do it through the acp before the upgrade, rather than changing it manually at the Settings.php file.

[jacbier]

That file is the master Settings.php file in the main directory of SMF - in it should be a line like that that says $maintenance = 0; or similar. 0 means no maintenance, 1 means soft maintenance (like you set in the admin), 2 means upgrade maintenance but that's not what you're seeing here.

In settings.php there is no line with $maintrance
with the exception of
# Note: If $maintenance is set to 2, the forum will be unusable! Change it to 0 to fix it.

[Doug Heffernan]

That file is the master Settings.php file in the main directory of SMF - in it should be a line like that that says $maintenance = 0; or similar. 0 means no maintenance, 1 means soft maintenance (like you set in the admin), 2 means upgrade maintenance but that's not what you're seeing here.

In settings.php there is no line with $maintrance

The var name is $maintenance and not $maintrance.

[pikeman]

It has to be there, it starts in the 16th row.

During the update, the maintenance mode did not turn itself off, I got a blank page. I set it up manually and the forum worked.

[jacbier]

That file is the master Settings.php file in the main directory of SMF - in it should be a line like that that says $maintenance = 0; or similar. 0 means no maintenance, 1 means soft maintenance (like you set in the admin), 2 means upgrade maintenance but that's not what you're seeing here.

In settings.php there is no line with $maintrance

The var name is $maintenance and not $maintrance.

Sorry for the typo.
I meant $maintenance

[jacbier]

It has to be there, it starts in the 16th row.

During the update, the maintenance mode did not turn itself off, I got a blank page. I set it up manually and the forum worked.

I inserted on line 16
$maintenance = 0;
But this didn't solve the problem.

[Doug Heffernan]

It has to be there, it starts in the 16th row.

During the update, the maintenance mode did not turn itself off, I got a blank page. I set it up manually and the forum worked.

I inserted on line 16
$maintenance = 0;
But this didn't solve the problem.

Of course that that won't solve the problem that you have. And what @pikeman meant is that when they did their upgrade, the upgrader did not place the forum in the maintenance mode automatically. He did that manually and then the upgrade worked. It is something to keep in mind for when you give the upgrader another go.

Reuplaoding a fresh set of files from the large upgrade package, your forum version, has a great chance of fixing the error. That is if it is caused by a mod. Because it can also be a server related issue, which most blank pages are usually.

[jacbier]

It has to be there, it starts in the 16th row.

During the update, the maintenance mode did not turn itself off, I got a blank page. I set it up manually and the forum worked.

I inserted on line 16
$maintenance = 0;
But this didn't solve the problem.

Reuplaoding a fresh set of files from the large upgrade package, your forum version, has a great chance of fixing the error. That is if it is caused by a mod. Because it can also be a server related issue, which most blank pages are usually.

I'll do that tomorrow.
It is now time to go to sleep in the Netherlands...

[Illori]

https://wiki.simplemachines.org/smf/How_to_upload_a_fresh_set_of_files

[Sir Osis of Liver]

If you're intent on upgrading to 2.1, you needn't worry about 2.0 mods, most are not compatible with 2.1, and all will be removed anyway when you do the upgrade.  Uploading clean files should get the forum up and running, but it's not necessary to do the upgrade.  You can just upload the 2.1 upgrade package, existing Settings.php should connect it to 2.0.19 database, then you can run ugrade.php

[Doug Heffernan]

Did you manage to upgrade your forum @jacbier?

[jacbier]

It has to be there, it starts in the 16th row.

During the update, the maintenance mode did not turn itself off, I got a blank page. I set it up manually and the forum worked.

I inserted on line 16
$maintenance = 0;
But this didn't solve the problem.

Reuplaoding a fresh set of files from the large upgrade package, your forum version, has a great chance of fixing the error. That is if it is caused by a mod. Because it can also be a server related issue, which most blank pages are usually.

I'll do that tomorrow.
It is now time to go to sleep in the Netherlands...

Did you manage to upgrade your forum @jacbier?

Finally the upgrade 2.1.1 was done. Each time the upgrade was aborted due to a Gateway timeout. After adjusting the settings of the server, I managed to complete the upgrade last night. There were many interruptions.The time shown was over 80 minutes.

I was equally happy. But quickly found out that the forum display was not good. It seems that the theme is not loading.
The forum moved a few weeks ago. I let the new hoster do that for a fee. But I could have done better myself. A few paths were out of order. I adjusted this myself where I could.

I have used repair settings. No paths for the theme are displayed. I can't edit the paths that way.
Does anyone have an idea how to solve this? It's an old and big forum. A completely fresh installation is therefore not a solution.

[jacbier]

Repair setting...
You cannot view this attachment.

[jacbier]

What I hadn't written yet. The path as you can set it with repair themes is correct.

[Doug Heffernan]

What I hadn't written yet. The path as you can set it with repair themes is correct.

Are we talking about a custom theme? Because themes for 2.0. will not work on 2.1.

[jacbier]

I assumed that the default theme would always be set after performing the upgrade.

After changing the cookie name as recommended by repair_settings, I can no longer log in...
I have changed the cookie name in settings.php again but that does not help.
Cookies have been removed as well as the internet files in the bowser. Using a different browser doesn't help either.
I've been working on the upgrade for several hours now. Just make the upgrade tool work again. It was ready very quickly and didn't seem to make any adjustments.
I've read several threads with similar login issues. Still no solution found.

[Doug Heffernan]

I assumed that the default theme would always be set after performing the upgrade.

After changing the cookie name as recommended by repair_settings, I can no longer log in...
I have changed the cookie name in settings.php again but that does not help.
Cookies have been removed as well as the internet files in the bowser. Using a different browser doesn't help either.
I've been working on the upgrade for several hours now. Just make the upgrade tool work again. It was ready very quickly and didn't seem to make any adjustments.
I've read several threads with similar login issues. Still no solution found.

Yes, the default theme should no problem. The custom 2.0.x themes only will not work with 2.1.

May I ask why did you run repair_settings.php after the upgrade?

[Sir Osis of Liver]

In repair_settings did you set all users to default theme?

[jacbier]

Yes, the default theme should no problem. The custom 2.0.x themes only will not work with 2.1.

May I ask why did you run repair_settings.php after the upgrade?

Because the look of the forum was not as it should be . There was clearly something wrong. I was hoping this could be resolved with repair settings.

[jacbier]

In repair_settings did you set all users to default theme?

I can not do that. Repair settings doesn't show anything about the theme. As a result, simply nothing can be set.
You cannot view this attachment.

[Sir Osis of Liver]

Your forum is loading without css.  Can you login as admin?  If so you should be able to get into ACP (with some difficulty) and check theme settings.  If you can login but can't get to it, pm your admin user/password and I'll have a look.  Just on for a short time right now, will be back on tonight (NY time).

[Kindred]

If repair_settings.php is not showing theme directories, then test indicates that you have bad DATABASE connection information.

The theme data is stored in the database.

[jacbier]

Your forum is loading without css.  Can you login as admin?  If so you should be able to get into ACP (with some difficulty) and check theme settings.  If you can login but can't get to it, pm your admin user/password and I'll have a look.  Just on for a short time right now, will be back on tonight (NY time).

I can no longer log in. This also does not work after restoring old backups. Backups with 2.018 and 2.0.19.
I'm going crazy. How is it possible that you have a working forum, backups are made of it and that if you restore it, the forum no longer works.
Incomprehensible to me.
The backups are made automatically by the hoster and you can restore backups for up to 60 days. But if those backups are not usable, it is of no use...

[jacbier]

If repair_settings.php is not showing theme directories, then test indicates that you have bad DATABASE connection information.

The theme data is stored in the database.

More and more I get the idea that something is wrong at the server level.

The host is not expensive. You get a lot. But the service leaves a lot to be desired.

[Doug Heffernan]

Your forum is loading without css.  Can you login as admin?  If so you should be able to get into ACP (with some difficulty) and check theme settings.  If you can login but can't get to it, pm your admin user/password and I'll have a look.  Just on for a short time right now, will be back on tonight (NY time).

I can no longer log in. This also does not work after restoring old backups. Backups with 2.018 and 2.0.19.
I'm going crazy. How is it possible that you have a working forum, backups are made of it and that if you restore it, the forum no longer works.
Incomprehensible to me.
The backups are made automatically by the hoster and you can restore backups for up to 60 days. But if those backups are not usable, it is of no use...

That is why it is very important to do the backups yourself and check them too to make sure that they are done properly. One must not rely on their host only for backups.

Can you upload the repair_settings.php file and send me the url in a pm so I could have a look for myself and see what info it displays? Or you can post a full screenshot of it here as well, but blur out the db info.

[Sir Osis of Liver]

It's connecting to the database, but db appears to be trashed.  

jacbier, do you have a local db backup?


Preview is hanging again, 61.214 seconds.

[jacbier]

That is why it is very important to do the backups yourself and check them too to make sure that they are done properly. One must not rely on their host only for backups.

Can you upload the repair_settings.php file and send me the url in a pm so I could have a look for myself and see what info it displays? Or you can post a full screenshot of it here as well, but blur out the db info.

I went to another hoster 5 weeks ago. The problem is that I can download backups but not upload. I then get a gateway timeout because the file is too large (570 MB)...
The host is cheap. You get a lot for your money, but some things are not ideal.

It is a very large and old forum with 10,000 members. 1 of the members has offered to help. He has experience as a web designer. I sent my backup to him. It seems he managed to get the forum (SMF 2.1.1) up and running on his server. The paths to the themes were not correct. Furthermore, there were some problems with outdated language files. He also noticed a few errors in the database migration. There are still a few things that need to be sorted out. But it's going in the right direction.
I'll have to ask the hoster to put the database on server when it's ready. So unfortunately I can't.

[@rjen]

There is a tool that can help with uploading a large database: bigdump

I used it before (al be at it was a while ago)

See for explanation (dutch):
https://www.antagonist.nl/help/nl/webhosting/advanced/bigdump

[jacbier]

There is a tool that can help with uploading a large database: bigdump

I used it before (al be at it was a while ago)

See for explanation (dutch):
https://www.antagonist.nl/help/nl/webhosting/advanced/bigdump

Thanks.

[Doug Heffernan]

There is a tool that can help with uploading a large database: bigdump

I used it before (al be at it was a while ago)

See for explanation (dutch):
https://www.antagonist.nl/help/nl/webhosting/advanced/bigdump

Indeed. It handles large db import very well.

[Doug Heffernan]

That is why it is very important to do the backups yourself and check them too to make sure that they are done properly. One must not rely on their host only for backups.

Can you upload the repair_settings.php file and send me the url in a pm so I could have a look for myself and see what info it displays? Or you can post a full screenshot of it here as well, but blur out the db info.

I went to another hoster 5 weeks ago. The problem is that I can download backups but not upload. I then get a gateway timeout because the file is too large (570 MB)...
The host is cheap. You get a lot for your money, but some things are not ideal.

It is a very large and old forum with 10,000 members. 1 of the members has offered to help. He has experience as a web designer. I sent my backup to him. It seems he managed to get the forum (SMF 2.1.1) up and running on his server. The paths to the themes were not correct. Furthermore, there were some problems with outdated language files. He also noticed a few errors in the database migration. There are still a few things that need to be sorted out. But it's going in the right direction.
I'll have to ask the hoster to put the database on server when it's ready. So unfortunately I can't.

It looks like things are going in the right direction then. Glad to hear that.

[Sir Osis of Liver]

Restoring server backups does not require uploading anything, backups are stored on the same or a different server, but it's all in house.  You can increase settings in php.ini (or via cpanel) to allow larger uploads.  Utilities such as BigDump and MySQLDumper do not work on all servers, they may be blocked or timed out, but worth a try.