With the editing settings and tools you can configure advanced settings related to the content creation and editing.

Using the Editing settings you can:

  • Use the Interface settings to e.g. disable regular paragraphs & pages on item-based solutions
  • Create and configure custom editor configurations
  • Create and manage workflows – a tool which enables you to create and assign roles (e.g. editor or reviewer) to users. Workflows are described in the Drafts & Workflows article under documentation.

Depending on your setup, you may also have access to a number of older settings. These are primarily supported for legacy-reasons, and are documented in the old manual.

The interface settings (Figure 2.1) let you configure various interface settings (no surprises there).

Figure 2.1 The Interface Settings

The User Interface section allows you to select a default interface language.

The Paragraph section controls settings related to standard paragraphs:

  • Max locking (minutes) – controls for how long a paragraph is locked when a user is editing it
  • Space before paragraph – controls how much spacing is inserted before a paragraph. Default is 0
  • Require ALT text and title to be filled out in all editors – makes it obligatory to add alt text and title inserted elements before a paragraph can be saved
  • Warn when closing paragraph without clicking save or cancel – what it says on the tin
  • Disable standard paragaph – disables the standard paragraph. This can be useful if you want to use item-based paragraphs only, or just remove the option of adding new paragraphs completely.
  • Enable focal points for standard paragraphs – enables focal points for the image field on a standard paragraph
  • Paragraph space mode – select a space mode; standard, div, or none (recommended)

The Page sections controls settings related to the standard page: 

  • Disable standard page – disables the standard page. This can be useful if you want to use only item-based pages, or want to disable the creation of new content completely.
  • Default publish mode – set a default publish mode for new pages; Published, Unpublished, or Hide in menu.

The Editor contexts section allows select editor configurations for particular contexts, like the Ecommerce product descriptions.

There are rich text editors all over Dynamicweb – when you create or edit paragraphs, when you work with items, and so forth.

By default, they all use the default editor configuration – but you can create custom configurations and apply them to individual users or user groups.

This lets you hide or add editor buttons, style things differently, and more.

To create a new editor configuration:

  • Go to Settings > Editing > Editor Configurations
  • Click New editor configuration in the toolbar to open the Editor Configuration view (Figure 3.1)
Figure 3.1 The Editor Configurations

On the most basic level, you must name the configuration and select a type – out of the box, Dynamicweb uses CKEditor 4.

You then have access to the configuration parameters.

Using the configuration parameters you can:

  • Specify a custom width and height for the configuration
  • Decide to not load editor.css and styles.xml – if unchecked they are loaded from either /System/ or /Templates/Designs/YourDesign (if available)
  • Select a configuration source – using either configuration file or manual configuration

To use a configuration file select it using the dropdown menu, then save and close the configuration.

If you select manual configuration, you can use the checkboxes to include or exclude individual tools in the editor toolbar, under the following areas:

  • Document
  • Clipboard
  • Editing
  • Basic Styles
  • Paragraph
  • Links
  • Insert
  • Styles
  • Tools
  • Format list
  • Values

Once you’ve created a custom editor configuration, you can apply it for single users or entire user groups.

Using DIV tags and iframes directly in the editor

The advanced.js configuration file lets you use div tags and iframes directly in the editor, but you need to edit the configuration file and remove the relevant tag from the config.removePLugins setting.

In the advanced.js, remove div, iframe – or both – to allow them in the editor.

config.removePlugins = 'save, newpage, preview, print, templates, flash, smiley, pagebreak, iframe, font, forms, colorbutton, bidi, div, table, tabletools, justify, indentblock, blockquote';

Videos from YouTube and other services should not be included by pasting embed codes into a text area - we recommend using items instead. Read more about items here.

The workflows tool, including version control, is described in the content section of this manual - read more.

Anchor tags

Anchor tags set via the Editor only work if the Global setting /Globalsettings/Settings/Designs/DoNotIncludeBaseHref is set to true.