Available Renderer Settings - Mura Docs v6

Available Renderer Settings

In addition to being able to redefine or add new methods, the local contentRenderer.cfc allows you to adjust various rendering settings on a per-site basis.

ContentRenderer Settings

// This determines what JavaScript library Mura should use with its built-in display objects. The options are Prototype and jQuery:
// This allows you set start standard navigation behavior at lower navigation levels. For example, this would be useful if you have a section of your site that should have its own primary navigation:
// This sets the maximum depth that standard navigation will follow:
// This allows developers to not rely on Mura to load the default JS framework and simply add it to their theme's HTMLhead:
// This is the default long date format for the site:
// This is the default short date format for the site:
// This is a list of file extensions and content types that will not directly download, but instead will render in an Mura CMS page with summary information:
// This is a list of what image extensions should be shown in built in content listing display objects:
// This tells Mura whether to serve images indirectly through fileManager.renderImage() or create direct links:
// This allow developers to choose whether site personalizations such as ratings and favorites are attached to simple cookies or an actual Mura user. Options are user or cookie. Users do not need to login in order to save cookie-based personalizations:
// This toggles whether the Mura tag call are actually processed by the setDynamicContent() method:
// This toggles whether the front end toolbar should be rendered for administrative users:
// This toggles whether the front end toolbar should be rendered for site members:
// This toggles whether editable display objects like components and content collections should be rendered:
// This toggle whether to render the request's HTMLHeadQueue and HTMLFootQueues render:
// The following settings allow developers to change logical page structure. For example, some developers prefer H1 tags for their page titles, some prefer H2 tags - you can adjust this here:

ShowMeta for Link and File Nodes

The current request's showMeta value is used to determine how Link and File requests are handled. It can be retrieved from the current event scope:

showMeta = $.event('showMeta');

Force All Files to Use a Summary Page

public any function onSiteRequestStart($) {
if ( $.event('showMeta') != 2 ) {
$.event('showMeta', 1);


  • 0 - Files and Links requests are either rendered as an HTML summary page or served directly according to the Site contentRenderer.cfc's showMetaList value.
  • 1 - Files and Links are always render as HTML summary page.
  • 2 - File and Links requests are always served directly.