Apache/Tomcat AJP connector: mod_jk has been replaced by mod_proxy_ajp in the GCN package.
The installation guide for GCN has been updated. If you want to switch to mod_proxy_ajp now, you just have to replace the file “/Node/etc/apache/apache-vhost-include.conf” with the one from the latest GCN package, disable mod_jk, enable mod_proxy & mod_proxy_ajp and restart your apache.
Bugfix RT58659
Changes to group memberships didn‘t update cached user objects, so the changes wouldn‘t show up in the user/me REST-call. This has been fixed.
Bugfix RT58575
In some cases a jmage.log file would be created in the root directory of the java process. A bugfix has been applied to the jmage library in order to prevent such files from being created.
Bugfix RT58657
Under some circumstances a defective object (e.g. a folder) would be stored in the cache which would prevent it from being listed or otherwise found in the context of multichannelling.
Bugfix RT58620
In rare cases, importing a new template could fail with an “Internal error”, because the folder, where the template was originally created did not exist any more. This has been fixed now.
Bugfix KB2086
The handling of datasource part types (single selection, multiselect, ...) during export and import has been improved to correctly preserve the selection in tags even in rare situations, where the internal id of datasource entries might be different between the source and target system.
It is important to note, that for the improved behaviour both the source and target system must be updated.
Bugfix RT58556
In some implementations, when editing a page in a channel with frontend editing, an SGB could occur when opening the tagfill dialog, if the user had edit permissions restricted to that channel due to incorrect checking of permissions. This has been fixed now, the edit permissions in the tagfill dialog will now always be checked for the page‘s channel.
Bugfix RT58538
When a page contains an image and the user has no page/image/file viewing permissions but only permissions for viewing the folder of the image, the user was not shown any useful error message. Instead the admin got an error log message. Now the user gets an error message indicating that he has no page/image/file viewing permissions in the folder of the image in the page, so that he can contact an group administrator to add the permissions. When editing the page, the user could change the image to another image in the folder that he has no page/image/file viewing permissions. Listing pages and images without said permissions was also possible via the REST-Api. This has been fixed so that the user cannot list images of a folder he has no permission to.
This Gentics Content.Node version includes the Aloha Editor 0.25.20 – 5.11.2014