Technical notes for upgrading to Mura 6

Mura CMS 6 represents one of the biggest releases of Mura CMS ever. As always, we strive for as much backwards compatibilty as possible. Most upgrades from previous versions will be problem-free. However, there are a few minor issues that may arise when upgrading to Mura CMS 6, especially if you're using Microsoft IIS 6.

Important API change:

In Mura 6 the URLs for file and link content types are built in the exact same way as other content types. This allows them to have clean hierachical text based urls instead of relying on LinkServID.  As a consequence, their filename attribute is now populated with its Mura URL.  

For Mura files you now get the name of the associated file with contentBean.getAssocFilename().

For Mura Links you now get the link value from contentBean.getAssocURL().

For Microsoft IIS users: 

Because Mura CMS 6 uses FontAwesome extensively, and IIS doesn't automatically handle this in an elegant way, you may need to make some minor adjustments to your server configuration. For those that don't know yet, FontAwesome is a very cool font-based icon set, based on the Web Open Font Format (WOFF) standard. 

When using IIS the web server needs to be made aware of the  .woff file format. In a effort to do this, Mura CMS 6 will automatically create a web.config file in its root containing the following configuration:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<defaultDocument>
<files>
<remove value="index.cfm" />
<add value="index.cfm" />
</files>
</defaultDocument>
<staticContent>
<remove fileExtension=".woff" />
<mimeMap fileExtension=".woff" mimeType="application/octet-stream" />
</staticContent>
</system.webServer>
</configuration>

In some cases, the explicit mime type mapping can cause a server level error if IIS is configured to not allow the staticContent module to be locally overridden.  If you encounter an IIS configuration error simply edit the newly created web.config file and remove its configuration.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
</configuration>

In addition if you already have a web.config file in your Mura root you will need to manually add the .woff for the mimeMap attribute.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<!-- Existing configuration -->
<staticContent>
<remove fileExtension=".woff" />
<mimeMap fileExtension=".woff" mimeType="application/octet-stream" />
</staticContent>
</system.webServer>
</configuration>

Important other compatibility notes: