The Etomite Prelude v1.1 code base includes several database modifications which must be performed on any existing installations prior to v1.0 before the installation will perform properly. New installations will automatically include these modifications so no further action will be required after the installation is complete other than editing and saving the site configuration settings as prompted by the installer.
IMPORTANT: As of Etomite Prelude v1.1 the code base no longer ships with a manager/includes/config.inc.php file. In order to make upgrades easier the package now contains a placeholder file named manager/includes/config.php which needs to be renamed or copied to manager/includes/config.inc.php and be set to have full read + write permissions before a new installation can be performed.
IMPORTANT: As of Etomite Prelude v1.1 you no longer have to manually perform any manager/includes/config.inc.php maintenance during upgrades. All that is required is that the existing file have write permissions so the installer can make any required changes.
When v1_db_patches.php is run it only sets the new chunk and export role permissions for Admin users. If other user roles require chunk or export permissions they must be assigned manually within the >Etomite Manager > Manage Users > Role Management section.
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 by clicking on the script name link in the installer upgrade area, upon successful completion, you can return to the main upgrade script - or you may opt to run the script independently. Attempting to run the 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.
It is advisable that you use the new config file (as it includes some path issues on certain servers).
There are a few DB changes in this version. There is no need to manually make these changes, as there is a script to do it for you, included within the Upgrade page of the installer. Make sure you backup your existing files, just in case, before proceeding. You should also make sure that you have the database setttings located at the top of your manager/includes/config.inc.php file for future reference.
Next, over-write your manager folder and its subdirectories, as well as the index.php file located within the root of your etomite install, and the install folder.
Although you may be able to reuse your original config file it is recommended that you use the new version. To create a new config.inc.php file, edit the new manager/includes/config.inc.generic.php file by changing the database settings to match those in your original config.inc.php file and then save it as manager/includes/config.inc.php.
Looking carefully you will also notice that additonal code and documentation has been added to the config file which can be used to configure custom session handling. Do not attempt to enable custom session handling at this time. Only attempt these changes after you have successfully completed the standard upgrade. If you opt to retain your original config.inc.php file, simply copy the previously backed up file back to its original location.
Finally, login to your manager and refresh the site cache.
There are no DB changes in the new version. Make sure you backup your existing files, just in case, before proceeding. You should also make sure that you have the database setttings located at the top of your manager/includes/config.inc.php file for future reference.
Next, over-write your manager folder and its subdirectories, as well as the index.php file located within the root of your etomite install.
Although you may be able to reuse your original config file it is recommended that you use the new version. To create a new config.inc.php file, edit the new manager/includes/config.inc.generic.php file by changing the database settings to match those in your original config.inc.php file and then save it as manager/includes/config.inc.php.
Looking carefully you will also notice that additonal code and documentation has been added to the config file which can be used to configure custom session handling. Do not attempt to enable custom session handling at this time. Only attempt these changes after you have successfully completed the standard upgrade. If you opt to retain your original config.inc.php file, simply copy the previously backed up file back to its original location.
Finally, login to your manager and refresh the site cache.
There are DB changes in the new version - read the README included within the distribution package for instructions on how to do so.
This guide will assist you in upgrading your Etomite installation. Please note that upgrading to Etomite 0.6 from Phase 0.5.3 requires some manual actions, and that you'll need to rewrite/ upgrade your snippets to work with 0.6.
If you are going to upgrade from 0.5.3 to 0.6, then it is highly advisable you do not do so in a production environment. It is best to do so in a local installation, and then to later, once everything works again, install that upgraded version on your production site. In order to upgrade the exisitng 0.5.3 installation, upload the files in the archive to your server (preferably a testing server ;) ) and then run the installation utility. Choose upgrade, and follow the instructions shown on the page. After you've done that, you can get started on upgrading your snippets. Should you need help doing so, please visit the forums. Please note, that until you've upgraded all the snippets, your site will be broken!
There are no new database changes from RC 2, so you can upload all the files to your site (make a back up of config.inc.php first), and the upgrade is completed! If you are upgrading from RC 1, there is one database change you'll need to make, which is described here.
Hosting Costs Generously Subsidized By:
Präsentationsmappen |
Mousepads |
Frontplatten |
Kennzeichnungssysteme |
Andreas Lewicki
Gaviones |
Schanskorven |
Hydac