Time required for forum upgrade process?

[LandyVlad]

AH Ok I misunderstood didn't realise those particular fields were/should be altered, I'll give that a go for sure.

@Neša
actually production forum is /home/gsxowner/public_html/forum

[shawnb61]

Looking at your note above, it looks like your old url is something like:

Code Select Expand

https://gsx1400owners.org/forum
And your old dir is:

Code Select Expand

/home/gsxowner/public_html/forum

[LandyVlad]

Indeed so I did it:
You cannot view this attachment.
Still appears to have the same problem.

[shawnb61]

It really is a very simple search & replace tool.  But you have to get a hit on the searches...  You've got at least two problems:

First, most of the links in your old forum are http, not https:
You cannot view this attachment.

Second, your URL in your signature is incomplete (no scheme - https://):
You cannot view this attachment.

Two actions:
1) On your "old" URL, use http, not https
2) Fix your signature by hand

You might try omitting the scheme altogether.  Just be careful - the more wide open the search, the more likely you'll make some substitutions you weren't planning for!

Hope this helps.

[LandyVlad]

I'll give no 1 a go

[LandyVlad]

OK that worked perfectly thanks

[LandyVlad]

OK so now with a functioning duplicate 2.0.19 forum, I uploaded the 2.1 files and ran the upgrade.php

It got terminally stuck at 7% doing the database tables backup.
I tried to re-run upgrade.php (this time omitting table backup as I had already backed up the database) but it said "Upgrade script already running - Michael is doing an upgrade" or words to that effect.

I don't know how to stop an upgrade script while it's running, in order to re-run it.

Then magically SOMETHING happened, I've no idea what, and I was able to run the upgrade.php again (without backup tables) and it appears to have worked.

Appears to.

I haven't had a look at the actual site yet but that's the next thing (today is my last day working from home so I may get a chance today, but otherwise this evening).

Edit: Quick try from the work computer and it's stuck in maintenance mode..) Sigh.
 

 

[Oldiesmann]

To get rid of that error just delete the $upgrade_data (or whatever it's called) from Settings.php - or just ignore the message and run the upgrade again anyway.

You can get it out of maintenance mode by setting $maintenance to either 0 (normal) or 1 ("regular" maintenance mode like what happens when you enable it from the admin center) in Settings.php

[LandyVlad]

It had paused somewhere where it needed me to press 'continue'. SO I did and it went through rest of process apparently correctly and even deleted upgrade.php etc from the directory.

Was using upgrade.php from the 2.1 upgrade files pack of course.

Anyway that all seems well and good except - it's still stuck in maintenance mode. (for me or anyone else)

[Skhilled]

I know there used to be a db table for that which you could easily change but I no longer see it in my tables...

[shawnb61]

Edit Settings.php as Oldiesmann pointed out above to get out of maint mode.

[Skhilled]

You are both right. I was thinking of something else. LOL

[LandyVlad]

Thanks I couldn't remember which file I needed to edit

[LandyVlad]

OK done and up and running
Now just going through and deleting mod files I don't need/not compatible.