With the inclusion of an upgrade tool today, what *exactly* is the correct/recommended upgrade method. Before now I have simply overwritten the updated files.
How now? :hmm:
How now? :hmm:
madfitz
-
- Elite Class Non Coder
- Posts: 97
Nao
- Dadman with a boy
-
-
- Posts: 16,079
Still the same.
Update the files.
Go to your forum.
Everything's upgraded transparently. If you're redirected to index.php?upgraded, then it means an upgrade just took place in the background. (I'm pondering whether I should actually show a "Upgraded" message, because even a guest can launch the upgrade process... I'm considering allowing this only for admins, but it means starting the upgrade after I've got proof that you're the admin, and at this point it might be too late to upgrade the database tables.)
Update the files.
Go to your forum.
Everything's upgraded transparently. If you're redirected to index.php?upgraded, then it means an upgrade just took place in the background. (I'm pondering whether I should actually show a "Upgraded" message, because even a guest can launch the upgrade process... I'm considering allowing this only for admins, but it means starting the upgrade after I've got proof that you're the admin, and at this point it might be too late to upgrade the database tables.)
txcas
-
-
- Bug Zapper
- Posts: 202
Should the version number go up to 1.0 or will is stay at 0.1 after the upgrade runs? I copied over the latest commits, but my version is still at 0.1.
Also, I don't see hey_not or hey_pm in the members table.
live627
-
-
- Should five per cent appear too small / Be thankful I don't take it all / 'Cause I'm the taxman, yeah I'm the taxman
- Posts: 1,670
Also, I don't see hey_not or hey_pm in the members table.
A confident man keeps quiet.whereas a frightened man keeps talking, hiding his fear.
txcas
-
-
- Bug Zapper
- Posts: 202
Re: Upgrading... how?
« Reply #5, on February 18th, 2014, 05:09 AM »Last edited on February 18th, 2014, 06:07 AM
Got it, thanks.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
Should the version number go up to 1.0 or will is stay at 0.1 after the upgrade runs? I copied over the latest commits, but my version is still at 0.1.
CSS classes, not DB columns :)Quote from txcas on February 18th, 2014, 03:31 AM Also, I don't see hey_not or hey_pm in the members table.
They're DB columns, not CSS classes... :^^;:
txcas
-
-
- Bug Zapper
- Posts: 202
I thought they were table fields based on the code in the upgrade.php file. Anyway, that means the upgrade did not work at all on my sites.
Nao
- Dadman with a boy
-
-
- Posts: 16,079
They are.
I just don't get why it wouldn't work for you...
Here's what Wedge does.
- define the Wedge constant to an internal version number.
- read $we_shot in settings. If not there, it is zero.
- compare against the constant. If not equal, runs the upgrade file.
- for each value of we_shot, find out if there's a matching numbered step in the function list, run it, increase $we_shot and save it in settings, to avoid re-running the step.
- stop when the variable equals the constant.
Worked just fine on wedge.org and my local install, but your server seems to be non cooperative.
I just don't get why it wouldn't work for you...
Here's what Wedge does.
- define the Wedge constant to an internal version number.
- read $we_shot in settings. If not there, it is zero.
- compare against the constant. If not equal, runs the upgrade file.
- for each value of we_shot, find out if there's a matching numbered step in the function list, run it, increase $we_shot and save it in settings, to avoid re-running the step.
- stop when the variable equals the constant.
Worked just fine on wedge.org and my local install, but your server seems to be non cooperative.