Migrating to Aloha Editor

As Live Editor support for Gentics Content.Node will be discontinued by the end of 2014 projects will need to be migrated to Aloha Editor.

1 Migration

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.

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.