In the project administration, the feature to export sites directly in a server directory (without creating a zip file) is currently not available. It will be fixed in the next maintenance version.
When creating a new content, only the properties in the current language are initialized with their default values. It is not the case for the other languages.
On creation of i18n autocreated properties an error is thrown by the default value listener when using the API or Content Editor. The node is still created, but default values are only filled in the current language.
The following features are part of our 2020 roadmap and will be delivered throughout the year.
WCAG check for CKEditor is not available with Content Editor 2.0 (released with Jahia 8.0.0.0). An alternative is already available through the Siteimprove connector. Jahia product team is also looking into CKEditor plugins to help editors with accessibility.
The Valid display languages option is not available in Content Editor 2.0. The legacy interface remains available in Advanced options>Content.
In Content Editor 2.0, it is not possible to:
The translate view (side-by-side view of two different languages) has not been implemented in Content Editor 2.0. However, you can still access the legacy UI for translation, as you were in V7.
Note that users with the translators role can access Content Editor. However, by default Content Editor will be empty. To change that experience, add the View content tab permissions for your translators. If needed also add View options tab, View layout tab, and View metadata tab permissions. Even with these permissions, they will only be able to edit the internationalized properties as opposed to Shared by all languages properties.
The following modules are not available yet with Jahia 8.