Upgrade to a Fresh Install - Mura Docs v7.1

Upgrade to a Fresh Install

Listed below are the basic steps for upgrading to Mura v7.1 to a "fresh" or "clean" installation directory. Choosing this upgrade path may be a better choice for those who have very few modifications in their legacy installations, and those who have confined their customizations to their "site" or "theme" directories.

Some of the steps outlined below are optional, and if skipped, Mura will still work. However, since the steps below assume you are upgrading to a fresh install, you may not want to skip them.

  1. Backup filesystem and database
    • If something goes wrong, you will want to be able to roll back to your current setup. So, please do not skip this step. It is also highly recommended you do a test run in a development or staging environment prior to attempting to upgrade your production installation(s).
  2. Download Mura v7.1 and extract the contents to your desired directory
  3. Copy each SiteID directory from your legacy installation into the new "{MuraRoot/sites/" directory
    • Mura still supports {MuraRoot}/{SiteID} in v7.1. However, the directory structure going forward will be {MuraRoot}/sites/{SiteID}.
  4. Move legacy site display objects into your theme 
    • For example, your legacy site may have custom display objects located under "{SiteID}/includes/display_objects/custom/". You could just move them into your theme's "display_objects" directory. Or, even rename your "display_objects" directory to "modules". See the "Tips for Legacy Display Objects" section for more information.
  5. Move everything else into the root of your {MuraRoot}/sites/{SiteID}/ directory, and delete the "includes" directory.
    • This is optional. If Mura locates an "includes" directory, it will be used. Again, moving forward though, this directory structure is considered "legacy".
    • If you have a custom "site" contentRenderer.cfc or eventHandler.cfc, move them to the root of your site. For example, {MuraRoot}/sites/{SiteID}/contentRenderer.cfc.
    • Also, move your "themes" directory to the root of your SiteID directory.
  6. If you want your theme to be a "global" theme, move it into the {MuraRoot}/themes/ directory. See The "themes" Directory section for more information about global themes.
  7. Copy your legacy {MuraRoot}/config/settings.ini.cfm file into the new {MuraRoot}/config/settings.ini.cfm file
    • This means Mura will use your existing database connection information, and all other settings too. However, you may need to modify the "context" setting, if it was set in your legacy installation.
    • The following settings are new to Mura v7.1, and should be added:
      • autoupdateurl=https://github.com/blueriver/MuraCMS/archive/7.1.zip
        • You may point this to an alternate URL, if desired
      • defaultthemeurl=https://github.com/blueriver/MuraBootstrap4/archive/master.zip
        • You may point this to an alternate URL, if desired
      • errortemplate=/muraWRM/core/templates/error.html
        • If you have a custom errortemplate from your legacy installation, you may need to copy that file into the new installation, and update this setting to reflect its location.
  8. If your legacy installation includes a custom {MuraRoot}/config/cfapplication.cfm file, you will want to copy it into the same directory of your new installation.
  9. If your legacy installation includes any custom "mappings" in the {MuraRoot}/config/mappings.cfm file, you should copy them into the same file of your new installation.
  10. Mura will need to be reloaded and database changes will need to be applied.
    • This is done by navigating to http://yourdomain/admin/?appreload&applydbupdates. Assuming you have modified the appreloadkey in your settings.ini.cfm file, you will need to use that setting in lieu of "appreload".