N1ED versioning and its control
N1ED is a dynamically developed product which updates are published from time to time on its CDN. There are two types of updates:
- Minor updates. Mostly fixes, sometimes tested features from the next release. Deployed every week.
- Major updates. Usually once a month we introduce new important features or make something new our customers asked for.
By default N1ED will update automatically if you use official CDN.
Do you need a smooth migration between versions?
Do you like new features as we are? Probably yes, but not of all your colleagues can share your (and our) enthusiasm.
All the new features are useful and important, but sometimes you just need more time to show to your team how to work with the new version or check yourself does it fit your needs.
We try to make automatic updates (default behaviour) smooth in any case, but we also give you an option to have a control in your hands. That's why you can specify a version to use.
For example current version is "2020.7.6" and you wish to keep it until you tested a new one. No problem, just switch automatically picking the latest version to fixed version. The wat to do it depends of which integration do you use.
Set N1ED version in Drupal installation
Please go to your Drupal control panel on the page of advanced N1ED options. This page is available at the URL
/admin/config/content/n1ed. and fill the field "Version" and save it. Now your Drupal will use exact version of N1ED until you specify another one. If you clear this field, you will go back to using the latest version.
Set N1ED version in other integrations
When you use:
- CKEditor add-on
- TinyMCE add-on
- React integration (based on TinyMCE)
- Snippet integration (based on TinyMCE or CKEditor)
you can just pass a special configuration key to your installation:
Please read according manual of your integration if you have any doubts how to pass it. Syntax may differ depending of the type you declare your configuration, but very similar to example above.
How to know which version to use?
The best way is to keep version you already use (or use auto updates - using the latest version). This screenshot illustrates how to see your N1ED version (open the dialog by pressing "?" button):
Now you can use this version number as configuration parameter and according version will be used.
More stability with self hosted version
We can give you a control not only on version to version migration, but also on keeping CDN always available by creating your own CDN on your side. Please read this article: Self-hosted version of N1ED