News:

Bored?  Looking to kill some time?  Want to chat with other SMF users?  Join us in IRC chat or Discord

Main Menu

Blank pages after restore backup after failed installation 2.1.1

Started by jacbier, February 18, 2022, 11:08:00 AM

Previous topic - Next topic

jacbier

Quote from: Doug Heffernan on February 18, 2022, 04:59:36 PM
Quote from: jacbier on February 18, 2022, 04:40:19 PMI 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

Quote from: jacbier on February 18, 2022, 05:24:59 PM
Quote from: Doug Heffernan on February 18, 2022, 04:59:36 PM
Quote from: jacbier on February 18, 2022, 04:40:19 PMI 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

Quote from: Arantor on February 18, 2022, 05:21:53 PMThat 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

Quote from: jacbier on February 18, 2022, 05:31:10 PM
Quote from: Arantor on February 18, 2022, 05:21:53 PMThat 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

Quote from: Doug Heffernan on February 18, 2022, 05:34:51 PM
Quote from: jacbier on February 18, 2022, 05:31:10 PM
Quote from: Arantor on February 18, 2022, 05:21:53 PMThat 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

Quote from: pikeman on February 18, 2022, 05:36:13 PMIt 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

Quote from: jacbier on February 18, 2022, 05:45:53 PM
Quote from: pikeman on February 18, 2022, 05:36:13 PMIt 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

Quote from: Doug Heffernan on February 18, 2022, 05:52:25 PM
Quote from: jacbier on February 18, 2022, 05:45:53 PM
Quote from: pikeman on February 18, 2022, 05:36:13 PMIt 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...


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
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters


jacbier

Quote from: jacbier on February 18, 2022, 05:59:46 PM
Quote from: Doug Heffernan on February 18, 2022, 05:52:25 PM
Quote from: jacbier on February 18, 2022, 05:45:53 PM
Quote from: pikeman on February 18, 2022, 05:36:13 PMIt 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...
Quote from: Doug Heffernan on February 19, 2022, 05:56:19 PMDid 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


jacbier

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

Doug Heffernan

Quote from: jacbier on February 20, 2022, 05:09:41 AMWhat 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

Quote from: jacbier on February 20, 2022, 03:49:12 PMI 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?
Ashes and diamonds, foe and friend,
 we were all equal in the end.

                                     - R. Waters

jacbier

Quote from: Doug Heffernan on February 20, 2022, 04:47:40 PMYes, 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.

Advertisement: