Gossamer Forum
Home : Products : Gossamer Links : Discussions :

Upgraded from 2.99.1 -- Installer detects 2.2.1 as starting version

Quote Reply
Upgraded from 2.99.1 -- Installer detects 2.2.1 as starting version
Upgraded 2.99.1 --> 3.0.0
Installer ends up with 2.2.1 upgraded to 3.0.0

Still the wrong version detected as the starting version...
Additionally it seems that now util.js and luna_core.js will have to be edited after every upgrade to remove the details which is not be be displayed in files going to client's disk while accessing Glinks3.X

Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================
Quote Reply
Re: [HyperTherm] Upgraded from 2.99.1 -- Installer detects 2.2.1 as starting version In reply to
It's probably due to the bug in the installer where we forgot to delete the old ConfigData.pm. Delete it before upgrading.

Adrian
Quote Reply
Re: [brewt] Upgraded from 2.99.1 -- Installer detects 2.2.1 as starting version In reply to
Hi.

2.1.2 <-- ConfigData.pm.
2.2.1 <-- Config/Data.pm.
2.99.1 <-- As in Config/Data.pm Pre Upgrade
I never had 2.2.1 as version mentioned in Config/Data.pm.
I never had any ConfiData.pm in the installation upgrade directory anywhere.
And this is reproducible as last time around it showed the same thing 2.2.1 --> 3.0.0 instead of 2.99.1 --> 3.0.0 (where as i was upgrading from 2.99.1).

Though there are no errors noticed post upgrade so far, but it would be nice if the installer picks the correct starting version, which at the moment it is not.

Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================