Upgrade an Existing Installation Directory

Listed below are the basic steps for upgrading to Mura v7.1 over a current legacy installation directory. Choosing this upgrade path may be a better choice for those who have several modifications in their legacy installations, and those who have not 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, 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 over your existing installation.
  3. Optionally, move 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 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.
  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. Review your {MuraRoot}/config/settings.ini.cfm file.
    • 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
    • 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

  8. The only files used in the {MuraRoot}/config/ directory are as follows, and all other directories and files may be deleted:
    • Application.cfc
    • cfapplication.cfm
    • settings.ini.cfm
  9. 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".