Hi Tullio,
To be honest I haven't tried things with the in memory db, so I don't know how
much help I can be, but I'll try.
When you run through the installer, do you get any error messages for any of
the modules being updated? I know that if a module fails to update, it won't
change the version number, so next time you start up, it will attempt to do the
update again.
Could you also check the magnolia.properties file in your custom webapp, and
look for a {{magnolia.update.auto}} property? If this had previously been set
to true, then you would've been able to bias the installer screen when
performing your previous updates.
If you have this file in source control, then you should be able to see if
anything has changed in there.
HTH,
Matt
Sent from my iPhone
On Dec 11, 2010, at 2:29 PM, "Tullio Bettinazzi" <[email protected]> wrote:
>
>
> Yes, in development I use in memory db, however till now, wen I migrated from
> 4.3.3 to 4.3.x I simply started new version.
> Now, in migration to 4.4.1 I'm forced to execute the update every time.
> I don't think this is standard, nor logic.
> I believe I need to save something, or set some parameter, in order to make
> it stable, but I don't know what?
> Tks
> Tullio
> --
> View this message in context:
> http://old.nabble.com/Upgrade-to-4.4---Fails-tp30350370p30434812.html
> Sent from the Magnolia - User mailing list archive at Nabble.com.
>
>
>
> ----------------------------------------------------------------
> For list details see
> http://www.magnolia-cms.com/home/community/mailing-lists.html
> To unsubscribe, E-mail to: <[email protected]>
> ----------------------------------------------------------------
>
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
