Just to clarify what transpired here I checked the installer and forund the following text at the very top of the upgrade page - above the text quoted in the post above... Looks like the configuration notification is in there - before any mention of which previous release being upgrading... The chronological ordering of the text infers that all steps are required before any release-specific steps... Perhaps it could be construed as being a bit vague, but, then again, the person who wrote the text (me) knew what they were doing, which is why multiple people performed test upgrades before the release... The context of the upgrade text was never questioned... The config.inc.php file always
gets overwritten during upgrades... The next major release will use an alternate upgrade method making this a non-issue...Etomite Upgrade
!!! PLEASE READ THIS ENTIRE DOCUMENT BEFORE PROCEEDING !!!
If you have not already done so, please take the time to read the README
file located in the root directory where this package.was installed. Doing so could eliminate the possibility of encountering un-needed problems during your new installation or upgrade of an existing installation.
All existing installations being upgraded which have a release number prior to Etomite Prelude v1.0 will require various database updates. Once you have successfully completed the configuration file modifications listed below
it is mandatory
that you run the script, v1_db_patches.php
, before attempting to access your sites main page or entering your Etomite Manager. You can execute this script now by clicking on the script name above and, upon successful completion, you can return to this script - or you may opt to run the script independently. Attempting to run this script on a previously updated database will not result in any problems - you will simply receive messages stating an OK completion status for each item.
Upgrading from Etomite 0.6.1.3 or 0.6.1.4
<<< SNIP >>>