You need to uninstall the old service before upgrading to Ephox Editors for Connections,
understand that role-based deployment cannot be migrated, and understand changes to the
configuration file
- Installation considerations
- The installation of Ephox Editors for Connections for Unix, Linux, and AIX systems automatically
uninstalls EditLive! for Connections version 2.x. For Windows installations and manual
installations, follow the instructions for uninstalling EditLive! for Connections version 2.x before
installing Ephox Editors for Connections.
- Role-based deployment issues
- To get a smooth experience with Ephox Editors for Connections, the old service for role-based
deployment must be removed.
- Roles are not backed up and cannot automatically be transferred from the old service to the new
one. Take a screen shot of the user/group-to-role mappings, print the list, or create some other
form of external backup that can be used to restore the mappings.
- Changes to config.js, the configuration file
- The location and format of the config.js file has changed.
- You might need to review and update this file after installing. The installer removes the old
version and (by default) creates a backup beforehand.
- Old location: (customization
dir)/javascript/ephox/editlive/connections/config.js
- New location: (customization
dir)/javascript/ephox/editors/connections/config.js
- In the config.js file, the boolean enableIntegration
and roleBasedDeployment settings have been removed in favor of a new string
setting editor, which selects the editor in use.
- The default stylesheet file has been renamed from editlive.css to
ephox.css.
Note: If you have customized the cssUrl
setting in config.js or the content of editlive.css, make sure that you transfer those
changes to the new config.js file or to ephox.css, respectively, before installation (see Changing
the Stylesheet).