1. Evo Documentation
      1. Administration
        1. Admin Users
          1. Admin Roles And Groups
          2. Reset your Password - Unblock your User
          3. Why Admin Users, Roles and Groups
        2. Friendly URL Solutions
        3. Moving Site
        4. Taking sites down for maintenance
        5. Upgrading
        6. Web Users
          1. Creating a Web User
          2. Web User Groups and Document Groups
          3. Why Web Users and Groups
      2. Content Editing
        1. Editing Resources
          1. Creating a Resource
          2. Edit a Resource
          3. Move a Resource
          4. Publishing a Resource
          5. Select a Template
        2. Evo Tags
          1. Document Variables
        3. Terminology
        4. The Admin Interface
        5. Who Should Read This
      3. Designing
        1. Adding Chunks
        2. Adding Snippets
        3. Adding Tags
          1. Resource Fields
        4. Cross References
        5. Document Caching
        6. Modifiers
          1. @ Modifiers
        7. Template Basics
      4. Developer's Guide
        1. API Reference
          1. DBAPI
            1. delete
            2. escape
            3. getInsertId
            4. query
            5. select
            6. update
          2. Document Object
          3. DocumentParser Object
            1. addEventListener
            2. changeWebUserPassword
            3. documentContent
            4. documentGenerated
            5. documentIdentifier
            6. documentListing
            7. documentMethod
            8. documentObject
            9. evalSnippet
            10. getAllChildren
            11. getCachePath
            12. getChildIds
            13. getDocumentChildren
            14. getDocumentChildrenTVarOutput
            15. getDocumentChildrenTVars
            16. getLoginUserID
            17. getLoginUserName
            18. getLoginUserType
            19. getManagerPath
            20. getParent
            21. getParentIds
            22. getUserData
            23. hasPermission
            24. isBackend
            25. isFrontend
            26. logEvent
            27. maxParserPasses
            28. minParserPasses
            29. regClientCSS
            30. runSnippet
            31. table_prefix
            32. tstart
            33. webAlert
        2. Chunks
        3. Modules
          1. How to create and run a module from within the Admin Interface
          2. Managing module dependencies
          3. Setting up configuration parameters
          4. Writing the module code
        4. Plugins
        5. Snippets
        6. Template Variables
          1. @ Bindings
            1. (at)CHUNK
            2. (at)DIRECTORY
            3. (at)DOCUMENT
            4. (at)EVAL
            5. (at)FILE
            6. (at)INHERIT
            7. (at)SELECT
            8. What are (at) Bindings
          2. Creating a Template Variable
          3. What are Template Variables
          4. Widgets
            1. DataGrid Widget
            2. Floater Widget
            3. Hyperlink Widget
            4. Marquee Widget
            5. Misc. Widget
            6. RichTextBox Widget
            7. Ticker Widget
            8. Viewport Widget
            9. What are Widgets
      5. Getting Started
        1. About Evo
        2. Basic Installation
    2. Evo Extras
      1. AjaxSearch
      2. AnythingRating
      3. Breadcrumbs
      4. directResize
      5. Ditto
        1. Examples
        2. Extenders
        3. Parameters
        4. Placeholders
      6. DocLister
        1. Examples
        2. Filters
        3. Main Parameters
        4. Notes for Developers
        5. Output Parameters
        6. Processing Before Output
      7. Easy 2 Gallery
      8. eForm
      9. EvoGallery
      10. FirstChildRedirect
      11. Jot
      12. MaxiGallery
      13. multiTV
        1. Examples
        2. Extras
        3. Installation
        4. Module
        5. Snippet
        6. Template Variable
      14. PHx
        1. Custom Modifiers
      15. Quill
      16. tagLinks
      17. TinyMCE
      18. TvTagCloud
      19. Wayfinder
        1. Examples
      20. Weblogin
      21. WebLoginPE
        1. API
        2. Parameters
        3. Placeholders
        4. Typical Errors
        5. Views (Templates)
        6. Working with Forms
      22. YAMS
        1. Configuration
        2. How To
          1. YAMS + Breadcrumbs
          2. YAMS + Ditto
          3. YAMS + Ditto + PHx
          4. YAMS + eForm
          5. YAMS + Jot
          6. YAMS + Snippets
          7. YAMS + Wayfinder
          8. YAMS Custom Multilingual TVs, Chunks, Snippets
          9. YAMS Language Dependent Layout
          10. YAMS Language Flag List
          11. YAMS Language Select Landing Page
          12. YAMS Mime-type Dependent Alias Suffixes
          13. YAMS Multilingual Weblinks
          14. YAMS XML Sitemap
        3. Installation
        4. Language Modes
        5. Language Settings
        6. Placeholders
        7. Setup
        8. Snippet
        9. Technical Details
    3. Evo Tutorials
      1. Extras - How To
        1. Ditto Tutorials
          1. Add Ditto Pagination
          2. Basic RSS feed
          3. Category Tagging with Ditto
          4. Create a Custom Ditto Template
          5. Custom Placeholders
          6. Dropdown Menu with Ditto
          7. Dynamically Show Related Posts
          8. Promote to Home Page
          9. Sort by a date tv
          10. Tagged blogging with Ditto (ex.1)
          11. Tagged blogging with Ditto (ex.2)
          12. Tagging Screencast


To upgrade Evo you follow almost exactly the same steps as in the Installation Guide. With one big exception. You do not erase or overwrite the config.inc.php file on your server. Here are the steps:

  1. If you have modified any of the default snippets or plugins, either rename them in the resource manager or be sure to uncheck them when you get to the step in the installation wizard which asks you which snippets and plugins to install. The upgrade process overwrites all the default snippets to ensure you have the latest versions. (If you modify any of the core distribution snippets, it is recommended you save them with a new name to prevent this from happening.)

  2. Backup everything. Download all your files with your FTP client to your hard drive. Use phpMyAdmin or whatever database utility you have to "dump" your entire database to your hard drive.

  3. Make sure everything is backed up! No kidding!

  4. Download and unzip the newer version of Evo.

  5. Upload the contents of the extracted folder to your server. Simply overwrite all the old files. The Evo archive should not contain the config.inc.php file in /manager/includes/ directory, so it won't be overwritten. But it's still good to check before uploading that it's not there, and that you have a backup of your current config.inc.php. (Did you remember to backup the files before doing this?)

  6. Now fire up your web browser and load the index.php file found in the /install/ directory.

  7. Follow the online steps. This time, right after you accept the license agreement, be sure to select the Upgrade radio button.

    NOTE: If your MySQL version is older than 4.1, select the Advanced Upgrade and use cp1251_koi8 as the Connection character set because the the only allowable value for charset_name is cp1251_koi8 before MySQL 4.1. It is possible to add new character set mappings by editing the sql/convert.cc file in the MySQL source distribution though, so you might be possible to use other charsets too.
  8. If you deleted your old files instead of overwriting them, you may have to CHMOD the files and folders that are described in the Installation Guide to make them writable by the server, but the upgrade wizard will tell you if you need to.

  9. Remember to uncheck any resources in the installation what you have modified yourself, if you have not changed their names.

  10. Once you get to a screen that has a checkbox offering to remove install directory, make sure it's checked (This prevents people from running the installation/upgrading process again and doing a hostile take over of your site).

  11. After the you have finished the upgrading wizard, go back to your FTP program and make sure that the "/install/" folder is deleted. If it's not, delete it manually.

  12. Finally, change the permissions of your config.inc.php file in "/manager/includes" folder back to read only. If you had written it down before, use that same CHMOD setting now, or try setting to "444". This is really important, and will help to prevent your site from being hacked.

  13. Finish the upgrading wizard.

  14. Once things are up and running again go to Evo admin interface and clean up your plugin and snippet names if you changed anything in step 1.

  15. That's it, you're done. You've just upgraded Evo.

Alternate Method

Uploading a new version of Evo over the top of an old one will leave you with old files that are no longer used. Evo team members each have different ways that they like to upgrade, but here's a method that will have the least downtime:

  1. Download everything from your site.

  2. Make a copy of your database.

  3. Basically, make sure you have all the old files backed up so that you can restore the old version if you need to.

  4. Create a new local directory called EvoNew (or whatever you prefer).

  5. Extract the new Evo files to that directory.

  6. From your backup, *copy* the config.inc.php file to manager/includes

  7. Copy any snippets, modules, plugins, etc., that you need or have modified into the appropriate parts of EvoNew.

  8. Copy any images, css, template files, documents, etc., into the appropriate parts of EvoNew.

  9. Rename the new folders/files to "index.php-new", "manager-new", "assets-new". Don't rename "install". Upload these folders (including the "install" folder) and the "index.php-new" file. This takes a while.

  10. Switch the names of the existing folders/files to "index.php-old", "manager-old", "assets-old".

  11. From this point, your site is not working.

  12. Change the names of the newfolders/files to "index.php", "manager", "assets".

  13. Run yoursite.com/install in your browser, being sure to select Upgrade. See Installation Guide for more information.

    NOTE:If your MySQL version is older than 4.1, select the Advanced Upgrade and usecp1251_koi8 as the Connection character set because the the only allowable value for charset_name is cp1251_koi8 before MySQL 4.1. It is possible to add new character set mappings by editing the sql/convert.cc file in the MySQL source distribution though, so you might be possible to use other charsets too.
  14. From this point, your site should be working again. If it isn't, switch the folder names back!

  15. You should then be able to delete all the -old directories.

  16. You should also, as a result, have a local backup of the old site, and a local backup of the new site.

Suggest an edit to this page.