The following known issues are schedule to be fixed in the next release schedule for the summer 2020
This issue will be fixed in the next maintenance release. A database lock happens upon restart of Jahia when using SQL Server as databases. To prevent the lock from happening, set the following environment variables, in setenv.bat.
set LOGGING_CONFIG=-Dnop
set LOGGING_MANAGER=-Dnop
Note: This change will disable some Tomcat logging (the localhost.*, manager.*, host-manager.* and catalina.* logs.)
In Content Editor 2.0, it is not possible to:
Automatic list ordering is not available in Content Editor 2.0 in the Jahia 8.0.0.0 release. Automatic list ordering will be reintroduced in Content Editor 2.1. The Case sensitive option will be removed and automatic list ordering will be case insensitive.
The Move first and Move last options are not available in Content Editor 2.0. If this is an issue for your organization, please contact Jahia support.
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 did in V8.
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 Valid display languages option is not available in Content Editor 2.0. This feature will be implemented in a future version. The legacy interface remains available in Advanced options>Content.
The following features are part of our 2020 roadmap and will be delivered throughout the year.
Template mixins feature is not available in Content Editor 2.0 (released with Jahia 8.0.0.0), it will be reintroduced in Content Editor 2.1. Template mixins are used when generating content editing form from content definition, it allows to display a field depending on the value of a mixin selected in another field. In other words, template mixins allows content editing forms to be dynamic depending on the values that are selected by the user.
To access such fields, you can use the legacy UI, available under "Advanced" tab.
Dependent properties feature is not available in Content Editor 2.0 (released with Jahia 8.0.0.0), it will be reintroduced in Content Editor 2.1. Dependent properties are somewhat similar to template mixins. They're used to filter dropdown values in content editing forms, depending on the values selected in previous field.
Automatic list ordering is not available in Content Editor 2.0 (released with Jahia 8.0.0.0), it will be reintroduced in Content Editor 2.1. The Case sensitive option will be removed and automatic list ordering will be case insensitive.
The mixin mix:title, that ensures that the system name of the content is kept in sync with the title is not supported in Content Editor 2.0 (released with Jahia 8.0.0.0), it will be reintroduced in Content Editor 2.1.
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.
In Content Editor, when you do a change in "advanced options" like in visibility tab, the publication actions are not updated. It is possible to publish from jContent or page composer.
The following modules are not available yet with Jahia 8.