Bloomreach Experience Manager 12 introduced the first version of visual editing. With visual editing, the user can edit content directly within the channel preview without the need to navigate to the Content perspective and perform the editing there. Changes made to the content are reflected in the channel preview directly after saving.
The visual editor is not intended as a replacement for the existing document editor in the Content perspective, but rather as an additional tool to make quick in-page text changes. Its functionality is limited to certain field types only. Users can switch to the full document editor to edit other field types any time.
Document Type Definitions
Like the full document editor, the visual editor renders a document type's editing form based on that document type's definition stored in the repository at:
(where [namespace] is the prefix of the document type's JCR namespace, and [document_type] the JCR node type corresponding to the document type)
Therefore, changes made to a document type using the Document Type Editor are reflected in both the full document editor and the visual editor.
Supported Field Types
The visual editor currently supports the following field types:
- Primitive types:
- Boolean Radio Group (**)
- Decimal Number
- DynamicDropdown (***)
- Radio Group (*)
- StaticDropdown (*)
- Compound types:
- Rich Text Editor
(*) Supported since Bloomreach Experience Manager 13.1
(**) Supported since Bloomreach Experience Manager 13.2
(***) Supported since Bloomreach Experience Manager 13.4
All other field types available in the Document Type Editor can only be edited using the full document editor in the content perspective.
Since Bloomreach Experience Manager 13.3, the visual editor supports all validators provided by the validation service. Wicket-only validators are only supported in the full document editor in the content perspective, so fields with Wicket-only validators can only be edited there.
The order of the fields displayed in the visual editor is determined by the order of the corresponding frontend:plugin nodes in the template definition stored in the repository:
Manage Content Button
The Manage Content button in the channel preview opens the corresponding document in the visual editor. In the visual editor, a link provides users the option to switch to the full document editor.
Currently, it's not possible to link the Manage Content button directly to the full document editor.