Upgrade an Existing Installation Directory - Mura Docs v7.1

Upgrade an Existing Installation Directory

These are the basic steps for manually upgrading an earlier version of Mura (e.g. 7.0, 6.2 or earlier) to Mura 7.1. 

Following these steps carefully, you will download Mura directly, and copy the new files over the old, then adjust a few things specific to version 7.1. 

*Some of the steps outlined below are optional.

  1. Required: back up files and database  (!important)
    • If something goes wrong, you will want to be able to roll back the changes. Do not skip this step.
    • It is also highly recommended to test the update in a development or staging environment prior to attempting to upgrade your live production installation.
  2. Required: download Mura v7.1: https://github.com/blueriver/MuraCMS/archive/7.1.zip
  3. Required: unzip the downloaded 7.1.zip file and copy the full contents into your Mura site root. Allow for any files to be overwritten or merged, if prompted by your operating system. 

    Note: on Linux and some Windows Server environments, full directories may be overwritten. In this case, it will be critical to restore a copy of the file at /config/settings.ini.cfm from your previous backup. 
  4. *Optional: move the SiteID directories for any sites into the new "{MuraRoot}/sites/" directory (e.g.  /default/ becomes /sites/default/, and /mysite1/ becomes /sites/mysite1/ , etc.)
    • Mura still supports {MuraRoot}/{SiteID} in v7.1, so the traditional structure of having the site folders in the root will still work just fine. However, the directory structure going forward will be {MuraRoot}/sites/{SiteID}, so we recommend doing this step now.
    • 4A.   *Optional: Move site display objects into the theme, to make them globally available 
      • 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.
      • Rename your "display_objects" directory to "modules". See the "Tips for Legacy Display Objects" section for more information.
    • 4B. *Optional: Copy the contents of the /siteid/includes directory into the root of your site directory e.g. {MuraRoot}/sites/{SiteID}/, and delete the "includes" directory.
      • This step 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. (e.g. /mysite1/themes/)
  5. *Optional: 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.
  6. Required: open the file at {MuraRoot}/config/settings.ini.cfm file in your code editor.
    • Add these lines (these settings are new to Mura v7.1, and should be added):
      (note, these settings can be altered to point to alternate archive URLs as a custom option)
    • If you have any legacy plugins installed, you might want to add the following setting if you run into issues, as some plugins may rely on old paths to application-specific files:
      • legacyappcfcsupport=true
    • The following settings should also be reviewed, if you have not already customized them to suit your specific needs:
      • usedefaultsmtpserver=true (specifically uses a boolean value now)
      • javasettingsloadpaths=/core/vendor/lib
      • errortemplate=/muraWRM/core/templates/error.html
      • scriptprotectexceptions=body,source,params,objectlist1,objectlist2,objectlist3,objectlist4,objectlist5,objectlist6,objectlist7

  7. Required: clean out unused files from {MuraRoot}/config/ . Delete all but the following three files from the /config/ directory:
    • Application.cfc
    • cfapplication.cfm
    • settings.ini.cfm
  8. Required: reload Mura, applying database changes:
    • This is done by navigating to http://{yourdomain}/admin/?appreload&applydbupdates. (If you have modified the appreloadkey in your settings.ini.cfm file, you will need to use that setting in place of "appreload".)