This system configuration entry, which can be found in the instance-specific config/gui.xml file, configures the properties of the Content Navigator as well as the behaviour of the GUI web applications.

  • customCommands: Determines the custom extensions of the Content Manager pages (see Configuring Custom Commands).

  • dynamicPreviewDirectory: If the dynamic preview has been activated, specify here the directory in which the exported preview files are to be made available to the webserver. Example: /absolute/dirpath

  • The preview web server needs to be configured to read the files from the specified directory using the character set defined in the export.exportCharset system configuration entry. If the Apache web server is used, the configuration explained in the dynamicPreviewUrl section below is sufficient.

  • dynamicPreviewExtensions: List of file name extensions (without the period) to be dealt with by the webserver. If the list is empty, the dynamic preview is deactivated, otherwise the connection to the preview server needs to be configured by means of the dynamicPreviewDirectory and dynamicPreviewUrl entries. Entries in this list are formed using extension elements. Example:

  • dynamicPreviewUrl: URL under which the preview webserver accesses the dynamicPreviewDirectory. To this URL the path of the file whose version is to be further processed dynamically is appended.
    Example: http://localhost:3100/preview. If a file has the path /path/page.php the URL http://localhost:3100/preview/path/page.php is requested. In this case, the preview server needs to be configured in such a way that /preview/ points to the dynamicPreviewDirectory.

    The preview web server needs to deliver files in the character set defined in the export.exportCharset system configuration entry. The character encoding needs to be specified in the Content-Length header. If the Apache web server is used, it is normally sufficient to specify AddDefaultCharset charset in the file httpd.conf, i. e. AddDefaultCharset UTF-8, for example.

  • fontFamily: Fonts from which the user can choose when configuring page display. Each font is defined by specifying its name in an item subelement. Please note that the browser possibly does not support all fonts and replaces missing fonts with existing ones, if necessary.

  • fontSize: Font sizes from which the user can choose when configuring page display. Each font size is defined by specifying its point size in an item subelement (example: 12pt).

  • jreSpecification: Under Windows, the applet for executing local applications requires the Java runtime environment 1.4.2_17 or later (see also the system requirements). If JRE 1.5 or later is installed in addition to JRE 1.4.2_x, this system configuration entry can be used to force the Internet Explorer to nevertheless use JRE 1.4.2_x for this applet. To do this, modify the the predefined entry in the following way:

    <jreSpecification name="1.4.2_17">

    The example above refers to the JRE version 1.4.2_17. If you use a different version, please adapt the version number accordingly.

  • previewMasterTemplates: Names of the layouts that can be selected for the preview. Each layout is defined in a template subelement. Example:

        <title lang="de">Mastertemplate</title>
        <title lang="en">master template</title>
  • roles: This dictionary contains the role definitions. (In the Content Navigator, roles are called user interfaces.) Each role in this dictionary is defined by means of a role element. For the possible values, please refer to the section rolePreferences. Example:

        <title lang="de">Nur Vorschau</title>
        <title lang="en">Preview Only</title>
          <browserName fixed="true">pb</browserName>

    Please note: If you remove a role currently in use by users, these users will not be able to log into the GUI until they have been given an existing role. To do this, use the following command: userConfigForUser login setTexts guiPreferences.currentRole newRoleName

  • tinymceConfig: When TinyMCE is initialized as an editor for the main content, its configuration is passed to it as a JavaScript object. By means of this configuration entry, tinymceConfig, a configuration can be specified as a JSON string for every user role. Furthermore, a (default) configuration can be specified for users with roles not given here. Example:

        theme_advanced_buttons2: ""
        theme_advanced_buttons1: "bold,italic,underline",
        theme_advanced_buttons2: ""

    This system configuration entry is optional. If it is missing or neither includes an entry for the user's role nor a default entry, the presets of TinyMCE are used. If, on the other hand, an entry for the user's role, or, as a fallback, a default entry exists, the settings of this entry extend or replace the presets of the TinyMCE configuration.

  • webDav: When a file is copied to or created in a web folder, the format of the corresponding new CMS file is determined by means of this system configuration entry and the name extension of the new file. The default format for name extensions not listed here is generic. Furthermore, the format of folders (directories in web folders) can be specified here using the defaultPublicationClass subentry. Example:

      <objectClasses type="dictionary">

TinyMCE configuration presets

TinyMCE and its configuration should never be modified since the changes would be reverted the next time CMS Fiona is updated. Essentially, the presets define a toolbar consisting of two rows that include the elements (buttons or drop-down boxes) named below.

    mode: "specific_textareas",
    editor_selector: "mceEditor",
    dialog_type: "modal",
    theme: "advanced",
    plugins: "npsfilebrowser,paste,searchreplace,table",
    theme_advanced_toolbar_location: "top",
    theme_advanced_buttons3: "",
    theme_advanced_toolbar_align: "left",
    theme_advanced_resizing: true,
    theme_advanced_statusbar_location: "bottom",
    skin: "o2k7",
    skin_variant: "silver",
    convert_urls: false,
    valid_elements: "*[*]"