1 Migration
1.1 Aloha Page Link Tag
First make sure that your Aloha Editor Page Link Tag is available and implemented as specified.
1.2 Migrate Constructs
Read this part carefully. Skipping steps can lead to severe problems after enabling Aloha Editor.
- The Table ext Parttype is no longer supported when using Aloha Editor. All tables have to be converted to html code. You can use Postprocessors of the Migration feature or write a custom script that uses the REST API.
- Make sure your Constructs all have a single root tag, as described in Constructs – Single Root Tags.
- In the latest version of Gentics Content.Node, existing Live editable tags must not be converted to use the
HTML (long)
parts for their contents – see Live Editable Tags. It is recommended to not change existing editables, because it would be necessary to migrate all stored contents from newlines to breaks (including versioned content), which is not possible.
When using existing editables with a part like Text
, Text/HTML
or Text/HTML (long)
(which will replace newlines to br-Tags while rendering), it is necessary to have the content being stripped of all newlines before saving. This will be done automatically, but requires that the feature aloha_annotate_editables
is activated (see Annotating Editables for details).
Some tagtype implementations may behave differently when used with Aloha Editor. Reviewing your editing workflows is advised. You should also use the migration to consolidate your implementation – eg. h2 tags do not need a construct anymore as Aloha Editor allows to handle them directly.
1.3 Activate Aloha Editor
Activate Aloha Editor from the Node settings.
1.4 Adapt Plugins and Configuration (optional)
This step ist optional. You can start out with the default set of plugins provided by Gentics Content.Node.
Adapt the list of plugins to be loaded with Aloha Editor and the corresponding plugin settings to match your needs.
Don’t forget to restart the tomcat after updating your configuration settings.