Re: [roller-1.3] Themes lost on upgrade

[Allen Gilliland <Al...@Sun.COM>]

upgrading from 0.9.9 directly to 1.3 is not supported, at least as far
as I am concerned.  we just didn't have a clean enough upgrade path in
place before roller 1.2 to make that possible.

i am guessing that if you look in your logs you'll see a line that says
"New installation found, setting db version to 130".  That's because
Roller 1.3 couldn't accurately determine the proper db version, so it
has to assume it's a new install.

i don't know who is still running on pre 1.2 Roller, but i think we
should make it very clear in the upgrade guides that users cannot just
deploy the latest version and expect everything to be okay.  users need
to follow each individual upgrade path until they get to Roller 1.2,
this means running db scripts and actually deploying each version of the
app and starting it up.  After that i think we've got it sorted out so
that you can upgrade multiple versions at a time as long as the db
scripts are run.

-- Allen


On Tue, 2005-11-08 at 10:40, Henri Yandell wrote:
> I just ran a test upgrade of a 0.9.9 install to 1.3. Due to the lack
> of a 0.9.9->1.0 migration script, I ran 0.9.8->1.0, which gives a few
> errors, and then the rest of them.
> 
> Due to not being supported in postgres, I didn't run 1.2->1.3, but I
> don't think it should be a big problem.
> 
> Things look good, the only problem I've noticed is that the theme gets
> lost. You have to login and set your theme to 'Custom' to get the old
> custom theme back (if you customised it). After the migration it gets
> set to Cheb (which might be the one I based the custom version on).
> 
> Carrie's custom theme results in a pretty error page in the IFRAME;
> but that's understandable as her theme is somehow broken on the 0.9.9
> version.
> 
> Hen

Re: [roller-1.3] Themes lost on upgrade

[Henri Yandell <fl...@gmail.com>]

On 11/8/05, Allen Gilliland <Al...@sun.com> wrote:
> upgrading from 0.9.9 directly to 1.3 is not supported, at least as far
> as I am concerned.  we just didn't have a clean enough upgrade path in
> place before roller 1.2 to make that possible.
>
> i am guessing that if you look in your logs you'll see a line that says
> "New installation found, setting db version to 130".  That's because
> Roller 1.3 couldn't accurately determine the proper db version, so it
> has to assume it's a new install.
>
> i don't know who is still running on pre 1.2 Roller, but i think we

Probably just me :) Baby born, time vanished etc etc.

> should make it very clear in the upgrade guides that users cannot just
> deploy the latest version and expect everything to be okay.  users need
> to follow each individual upgrade path until they get to Roller 1.2,
> this means running db scripts and actually deploying each version of the
> app and starting it up.  After that i think we've got it sorted out so
> that you can upgrade multiple versions at a time as long as the db
> scripts are run.

Ouch. It seems to be doing remarkably well for all that, but I'll make
an attempt of the multi-step update.

Thanks,

Hen