Wedge

Public area => The Pub => Topic started by: madfitz on February 18th, 2014, 12:05 AM

Title: Upgrading... how?
Post by: madfitz on February 18th, 2014, 12:05 AM
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:
Title: Re: Upgrading... how?
Post by: Nao on February 18th, 2014, 12:14 AM
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.)
Title: Re: Upgrading... how?
Post by: txcas on February 18th, 2014, 03:22 AM
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.
Title: Re: Upgrading... how?
Post by: txcas on February 18th, 2014, 03:31 AM
Also, I don't see hey_not or hey_pm in the members table.
Title: Re: Upgrading... how?
Post by: live627 on February 18th, 2014, 04:38 AM
Quote from txcas on February 18th, 2014, 03:31 AM
Also, I don't see hey_not or hey_pm in the members table.
CSS classes, not DB columns :)
Title: Re: Upgrading... how?
Post by: txcas on February 18th, 2014, 05:09 AM
Got it, thanks.
Title: Re: Upgrading... how?
Post by: Nao on February 18th, 2014, 07:11 AM
Quote from txcas on February 18th, 2014, 03:22 AM
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.
If you're talking about the version check in the admin area, forget about it. It'll be rewritten when I can be arsed to do it.
Title: Re: Upgrading... how?
Post by: Nao on February 18th, 2014, 07:11 AM
Quote from live627 on February 18th, 2014, 04:38 AM
Quote from txcas on February 18th, 2014, 03:31 AM
Also, I don't see hey_not or hey_pm in the members table.
CSS classes, not DB columns :)
Eh..?
They're DB columns, not CSS classes... :^^;:
Title: Re: Upgrading... how?
Post by: txcas on February 18th, 2014, 02:14 PM
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.
Title: Re: Upgrading... how?
Post by: Nao on February 18th, 2014, 02:52 PM
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.