etoFork CMS - heavy changes to the Etomite manager and new functionality
JavaScript PHP CSS
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.



Modified 2014-4-25 test changes using github app

Modified 2014-4-24 etoFork v2.52 moved to GitHub

Modified 2010-2-18 [v1.1] by John Carlson

functionality to have new Meta Tags section for documents and also added previous version
of the documents so that you can revert back to a previous version of the document.

Modified 2008-05-08 [v1.1] by Ralph Dahlgren

Etomite Prelude v1.1 installation and upgrade notes

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.

New Installations

IMPORTANT: As of Etomite Prelude v1.1 the code base no longer ships with a
manager/includes/ 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/
and be set to have full read + write permissions before a new installation
can be performed.

* Perform backups just in case something goes wrong. YOU HAVE BEEN WARNED!
* Upload all files to your web server
* Follow the installation procedures described at
* If you don't want to read the instructions simply point your browser to
  http://your_etomite_server/ and follow the installation instructions.
  It'll be easier if you follow the instructions mentioned above, however.
* If you have problems you can seek help in the support forums at

Upgrading Previous Releases

IMPORTANT: As of Etomite Prelude v1.1 you no longer have to manually perform
any manager/includes/ maintenance during upgrades. All that is
required is that the existing file have write permissions so the installer can
make any required changes.

* Perform backups just in case something goes wrong. YOU HAVE BEEN WARNED!
* Upload all files to your web server
* Point your browser to http://your_etomite_server/install/
* Select: Upgrade an existing installation
* Read the entire upgrade document before proceeding. YOU HAVE BEEN WARNED!
* Follow any instructions which pertain to your specific needs based on your
  previous release
* Make sure you click on the link, "v1_db_patches.php", to perform add
  database upgrades! YOU HAVE BEEN WARNED!
* If you didn't go into your [Etomite manager > Configuration] yet to verify
  and save your settings, do so now and then perform a [Clear site cache]
  from the Etomite Main Menu. (There are new settings that should be reviewed
  and set according to your needs!)
* You should have a fully functional Etomite Prelude v1.1 installation
* If you have problems you can seek help in the support forums at

PLEASE NOTE: 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.

The Etomite CMS Project Development Team