Gentics Content.Node 5.28.4
Bugfix SUP-4941
Fixed a bug in the GenticsImageStore that caused images that are cropped to have the wrong width and height. Be careful when updating if you have pages with cropped images and swapped crop width and crop height in the GenticsImagestore URL.
Bugfix SUP-4646
Moving a folder to another channel did not move all objects within that folder to the new channel which could make objects inaccessible in some situations. This has been fixed.
Bugfix SUP-4911
Aloha Editor gcnfileupload-plugin: Uploading a new file did not work when the Fileupload Manipulator previously rejected the file and the dialog has not been closed in between.
New UI Update
- Repository browser supports selecting items from user favourites
- Opening an item in the editor panel highlights it in the list
- Node and base folder properties can now be edited
- Close editor when user deletes opened item
- Correctly update page status after publishing
- Fix taking pages offline where there are no language variants
- Fix runtime error in item list
- Performance improvements
- Improve handling of unknown nodes and folders
Gentics Content.Node 5.28.3
Enhancement SUP-4907
It is now possible to use different Media-RequestTypes in Rest-Requests when using the RestClientManager in Activiti-Tasks
Bugfix SUP-4293
Fixed a bug where duplicate pages with the same name and filename would be created when copying multiple pages to another folder and the user would double click the folder name link.
Bugfix SUP-4308
Fixed that the assigned content repository was not saved when using the rest methods /node/create or /node/save with a new content repository ID.
Bugfix SUP-4363
Fixed that Rest API requests to /auth/login failed when the User-Agent header was empty. A set User-Agent ist not required for HTTP requests.
Bugfix SUP-4867
The fix for SUP-4530 “When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.” has been extended to work under all circumstances.
Bugfix SUP-4824
Some UI errors for export of channels have been fixed:
- It is now possible to select channels also from the list of nodes (not only from the tree)
- Channels will now also be included in the count of objects contained in an export bundle
- Channels will now be shown in the overview and detailed list of objects contained in an export bundle
Bugfix SUP-4910
Clicking ‘Back to the folder‘ before uploading a new file or image did nothing. Now it works as intended.
New UI Update
- Do not hide display fields when right panel is open
- Redirect to previous URL on login
- Improved load times in all browsers
- Fix language comparison mode
- Fix error when searching by page id for a localized page
Gentics Content.Node 5.28.2
Bugfix SUP-4832
Feature invalidpageurlmsg: Fixed that deleting a page from the wastebin generated an inbox message when the page was references by a link in another page. The message will be only sent anymore when the page is moved to the wastebin.
Gentics Content.Node 5.28.1
Documentation SUP-4738
The Guides to install Oracle Server JRE 8 on Debian have been updated to fix errors in Autoupdate due to missing jar tool.
Bugfix SUP-4530
When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.
Bugfix SUP-4638
Fixed user being notified for offline links unnecessarily when the source page also has been taken offline at the same time.
Bugfix SUP-4740
The permission check of the REST API endpoint /user/save/{id} was too restrictive and has been fixed now.
Bugfix SUP-4309
When restarting the Tomcat with the nodectl command, the script could hang in an infinite loop when the PID file doesn‘t exist. This has been fixed.
Gentics Content.Node 5.28.0
Optional Manual Change
Internal Aloha links can now be marked as online/offline via the attribute data-gentics-aloha-object-online.
This will be used in the aloha editor plugin emptylink to highlight links to internal pages that are offline. Check out the (Aloha Page Link Tag Description) for details.
Enhancement GTXPE-74
The list of objects in the wastebin can now also be sorted by folder path.
Enhancement GTXPE-79
The new feature nice_urls allows setting of alternative URLs for pages.
Enhancement GTXPE-52
The tag migration tool now supports custom pre processors, that can modify tags (before they are migrated), skip migration for specific tags or skip migration of objects. Consult the Migration Tool Documentation for details.
Bugfix SUP-4688
Fixed a bug which caused the REST API to reject XML formatted bodies.
New UI Update
- Support for nice urls
- Fix height of multi-select inputs in object properties form
- Clicking Gentics logo clears out the search term
- Fix unwanted switching between edit/list views in IE11
- Fix page scrolling issue in IE11
Gentics Content.Node 5.27.11
Enhancement SUP-4907
It is now possible to use different Media-RequestTypes in Rest-Requests when using the RestClientManager in Activiti-Tasks
Bugfix SUP-4293
Fixed a bug where duplicate pages with the same name and filename would be created when copying multiple pages to another folder and the user would double click the folder name link.
Bugfix SUP-4308
Fixed that the assigned content repository was not saved when using the rest methods /node/create or /node/save with a new content repository ID.
Bugfix SUP-4363
Fixed that Rest API requests to /auth/login failed when the User-Agent header was empty. A set User-Agent ist not required for HTTP requests.
Bugfix SUP-4867
The fix for SUP-4530 “When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.” has been extended to work under all circumstances.
Bugfix SUP-4824
Some UI errors for export of channels have been fixed:
- It is now possible to select channels also from the list of nodes (not only from the tree)
- Channels will now also be included in the count of objects contained in an export bundle
- Channels will now be shown in the overview and detailed list of objects contained in an export bundle
Bugfix SUP-4910
Clicking ‘Back to the folder‘ before uploading a new file or image did nothing. Now it works as intended.
New UI Update
- Do not hide display fields when right panel is open
- Redirect to previous URL on login
- Improved load times in all browsers
- Fix language comparison mode
- Fix error when searching by page id for a localized page
Gentics Content.Node 5.27.10
Bugfix SUP-4832
Feature invalidpageurlmsg: Fixed that deleting a page from the wastebin generated an inbox message when the page was references by a link in another page. The message will be only sent anymore when the page is moved to the wastebin.
Gentics Content.Node 5.27.9
Documentation SUP-4738
The Guides to install Oracle Server JRE 8 on Debian have been updated to fix errors in Autoupdate due to missing jar tool.
Bugfix SUP-4530
When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.
Bugfix SUP-4638
Fixed user being notified for offline links unnecessarily when the source page also has been taken offline at the same time.
Bugfix SUP-4740
The permission check of the REST API endpoint /user/save/{id} was too restrictive and has been fixed now.
Bugfix SUP-4309
When restarting the Tomcat with the nodectl command, the script could hang in an infinite loop when the PID file doesn‘t exist. This has been fixed.
Gentics Content.Node 5.27.8
Documentation SUP-3892
A description for the feature tagfill_light has been added to the Guides
Bugfix SUP-4688
Fixed a bug which caused the REST API to reject XML formatted bodies.
New UI Update
- Support for nice urls
- Fix height of multi-select inputs in object properties form
- Clicking Gentics logo clears out the search term
- Fix unwanted switching between edit/list views in IE11
- Fix page scrolling issue in IE11
Gentics Content.Node 5.27.7
Documentation SUP-4625
Improved translation for documentation of breadcrumb part type.
Documentation SUP-4069
The description for mounting a folder via WebDAV has been updated. Please note that the WebDAV feature is deprecated.
Bugfix SUP-4569
The REST API endpoint /CNPortletapp/rest/info/maintenance returns information about maintenance mode (whether the maintenance mode is active and the maintenance message).
Bugfix SUP-4548
Several fixes have been made to the Java RestClient:
- The call to client.ssologin() failed with “406 Not Acceptable”
- It is now possible to initialize the client with a custom JerseyClient instance, in order to add custom filters and interceptors
- File Upload did not work
- The examples in the Infoportal:http://www.gentics.com/Content.Node/guides/rest_java_client.html have been updated to Jersey 2
Bugfix SUP-4235
When using MariaDB in the backend, the session handling could cause some locks in the database, which caused SGBs. This has been fixed now.
Bugfix SUP-4110
When the license key of an installation was changed during reactivation, the global prefix was not immediately changed to the new license key, but only when the Tomcat was restarted. This has been fixed now.
Bugfix SUP-4017
The check for the DB triggers on JVM startup failed to detect non-existent Definers in triggers. This could happen, when the user with which the database was originally created was dropped, or when the triggers were migrated between systems. The trigger check has been changed now, so that triggers with non-existent Definers will be dropped and recreated upon startup of the CMS JVM.
Bugfix SUP-4545
The contentnode-restapi maven module dependencies have been updated. Various mandatory jersey client libraries are now included via the compile time scope setting.
Bugfix SUP-4492
When the group assignment of users were changed, objects that were created, edited or published by that user were unnecessarily queued for republishing. This has been fixed now.
Bugfix SUP-4236
When the upload of a file fails, because of problems with the file upload manipulator (e.g. timeout), the error message shown to the user has been improved.
Bugfix SUP-4000
Synchronizing pages between channels sometimes produced an error, when they either contained tags from constructs with multiple parts that had no keyword, or when tags with the same name used different constructs. Those issues have been fixed now.
New UI Update
- Display a notification when maintenance mode is active (ContentNode >= 5.27)
- No longer prevent events from implementation-specific scripts in edit frame
- Don‘t mark pages as locked when previewing or when user has no edit permissions
- Fix behavior of “synchronize channel with master” modal
Gentics Content.Node 5.27.5
Bugfix SUP-4274
When copying an existing tag inside the same page (with the copy-tags feature activated) and deleting the original tag afterwards the page could not be saved because of a JavaScript error. This has been fixed now.
Bugfix SUP-4372
When editing a page with Aloha Editor and clicking the “Cancel“ link in the assistant frame, the intermediate state of the page was saved and the page still locked. This has been fixed now, so that “Cancel“ from the assistant frame works exactly like “Cancel” from the main menu.
Bugfix SUP-4430
Under special circumstances, the automatic recreation of missing images in the GenticsImageStore while publishing into the filesystem failed, which caused a failure of the publish process. This has been fixed now.
Bugfix SUP-4360
When a new user was created, the user list fetched from the REST API via /rest/user/list did not show the new user immediately due to caches not being invalidated. This has been fixed now.
Bugfix SUP-4358
Fixed an error in the REST API, which could lead to recurrent NullPointerExceptions.
New UI Update
- Use correct item permissions when searching
- Open page preview when clicking a page in favourites list
- Fix page status after publishing pages with time management
- Fix inbox message parsing for edge-cases
Gentics Content.Node 5.27.4
New UI Update
- Add error message when new passwords do not match
- Fix missing scrollbars in sidebar “messages“ and “favourites” components in FF & IE11
- Correctly detect and handle errors from the REST API
Gentics Content.Node 5.27.3
Bugfix SUP-4193
Fixed logging in not working for IPv6 HTTP clients.
Gentics Content.Node 5.27.2
Deleting an item from the wastebin has been renamed from “Remove from wastebin“ to “Delete“ for usability reasons, so that it‘s better distinguishable from the “Restore” operation.
Optional Manual Change
Changed the Tomcat maxThreads setting to 256 for the AJP connector in server.xml in the default package configuration. If your Apache webserver is allowing more than 200 connections you will need to make sure that the Tomcat can also handle at least as many connections (MaxThreads) as the MaxClients setting in Apache (default 256). Please configure this in server.xml for AJP connector if not already done in order to avoid errors.
Bugfix SUP-4108
Enhanced an error message that occured when deleting on object in the CMS with the UI or pageimport and the object was already deleted.
Bugfix SUP-4135
Under special circumstances, the URL to translate a page could lead to an SGB. This has been fixed now.
Bugfix SUP-3980
Logged rendering errors will now include more specific information, which object was rendered when the error occurred.
New UI Update
- Mark page as changed after submitting tagfill dialog
- Enable publish button when page has unsaved changes
- Don‘t show “save/discard changes?” modal after publishing
Gentics Content.Node 5.27.1
Optional Manual Change
Updated the Oracle JDBC connector to 5.1.41 in order to fix a bug with MySQL 5.7 where the CMS would throw an error when trying to check and update the MySQL database triggers. For newer MySQL server versions the JDBC connector will now use SSL for connections by default. However SSL also comes with a performance impact. If you don‘t need SSL for connections to the MySQL database (eg.: when MySQL is running on the same server), we recommend to turn SSL off by adding useSSL=false to the MySQL JDBC URL.
This is done in the node.conf of your cms installation. By default the configuration file is found at /Node/etc/conf.d/node.db.conf. If there is no such file – create it.
In the node.db.conf create the following entry:
bc. $SETTINGS[“jdbcparameters“] = “useSSL=false“;
If the jdbcparameters index is already set concatenate parameters with “&“ like
bc. $SETTINGS[“jdbcparameters“] = “someOtherParam=1&useSSL=false”;
When using SSL, server certificate verification should be enabled and configured properly according to the MySQL documentation. See Connecting Securely Using SSL for more information.
Bugfix SUP-4082
When the permission to view pages was granted through roles, the pages were not always shown in the page list correctly. Especially the list of pages using other items (like specific images) was not always correct. This has been fixed now.
Bugfix SUP-4121
An error in the Java REST API Client, which was introduced with the Update of Jersey has been fixed.
Bugfix SUP-4081
Some icons in the CMS UI were missing tooltips, which have been added now.
Bugfix SUP-4079
When using the “cancel” action from the related links from the translation split view, the split view was not closed, but showed the page list in the lower part. This has been fixed, cancel will now close the split view and show the page list in the whole frame.
Bugfix SUP-4111
When tags of a template were changed to use a different construct, the synchronization with pages did not change the tags in the page, if the page was imported. This has been fixed now, synchronization of pages with their templates will now work regardless of how the page was created.
Gentics Content.Node 5.27.0
Security SUP-2676
The node user doesn‘t have a password now by default (new CMS installations). See: How can i set the password of the node CMS user?.
Enhancement
The library used to generate the REST API (Jersey) has been updated to Version 2.23.1.
Enhancement
The new feature Devtools allows to edit tagtypes, datasources, templates and object properties in the filesystem.
Possible usecases are
- Developers can use their favourite editors for editing
- Implementations can be versioned and distributed via versioning systems (like git)
- Clean separation of implementation assets (javascript, css, images) from content elements
- Staging of implementations via the filesystem (fully automated)
Enhancement GTXPE-73
The queue for pages which have to be approved for publication will now also show the name of the template for each page.
New UI Update
- Increased performance and responsiveness across all browsers
- Navigation across items and edit modes now persist in the URL and browser history
- Improved confirmation prompt when navigating away from unsaved changes
- Hover intent for item list checkboxes improved
- Page status visible in repository browser
- Fix edge-cases with custom scripts for long-loading pages
- Fix missing cancel button in certain tagfill dialogs
- Fix time management modal inconsistency in edge-cases
- Fix creation & edit date in file/image preview
- Fix file upload issues for Firefox 45
- Fix breadcrumb styling on deep navigation
- Item list no longer jumps when using pagination
- Start page icon now more obvious and added to repository browser
- Buttons in edit panel rearranged & improved
- Publishing a page closes the edit panel
- Folder list is scrolled to top on navigation
- Better error messages for failed file uploads
Gentics Content.Node 5.26.23
Bugfix SUP-4293
Fixed a bug where duplicate pages with the same name and filename would be created when copying multiple pages to another folder and the user would double click the folder name link.
Bugfix SUP-4308
Fixed that the assigned content repository was not saved when using the rest methods /node/create or /node/save with a new content repository ID.
Bugfix SUP-4363
Fixed that Rest API requests to /auth/login failed when the User-Agent header was empty. A set User-Agent ist not required for HTTP requests.
Bugfix SUP-4867
The fix for SUP-4530 “When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.” has been extended to work under all circumstances.
Bugfix SUP-4824
Some UI errors for export of channels have been fixed:
- It is now possible to select channels also from the list of nodes (not only from the tree)
- Channels will now also be included in the count of objects contained in an export bundle
- Channels will now be shown in the overview and detailed list of objects contained in an export bundle
Gentics Content.Node 5.26.22
Enhancement SUP-4907
It is now possible to use different Media-RequestTypes in Rest-Requests when using the RestClientManager in Activiti-Tasks
Bugfix SUP-4910
Clicking ‘Back to the folder‘ before uploading a new file or image did nothing. Now it works as intended.
New UI Update
- Do not hide display fields when right panel is open
- Redirect to previous URL on login
- Improved load times in all browsers
- Fix language comparison mode
- Fix error when searching by page id for a localized page
Gentics Content.Node 5.26.21
Bugfix SUP-4832
Feature invalidpageurlmsg: Fixed that deleting a page from the wastebin generated an inbox message when the page was references by a link in another page. The message will be only sent anymore when the page is moved to the wastebin.
Gentics Content.Node 5.26.20
Documentation SUP-4738
The Guides to install Oracle Server JRE 8 on Debian have been updated to fix errors in Autoupdate due to missing jar tool.
Bugfix SUP-4530
When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.
Bugfix SUP-4638
Fixed user being notified for offline links unnecessarily when the source page also has been taken offline at the same time.
Bugfix SUP-4740
The permission check of the REST API endpoint /user/save/{id} was too restrictive and has been fixed now.
Bugfix SUP-4309
When restarting the Tomcat with the nodectl command, the script could hang in an infinite loop when the PID file doesn‘t exist. This has been fixed.
Gentics Content.Node 5.26.19
Documentation SUP-3892
A description for the feature tagfill_light has been added to the Guides
New UI Update
- Support for nice urls
- Fix height of multi-select inputs in object properties form
- Clicking Gentics logo clears out the search term
- Fix unwanted switching between edit/list views in IE11
- Fix page scrolling issue in IE11
Gentics Content.Node 5.26.18
Documentation SUP-4625
Improved translation for documentation of breadcrumb part type.
Documentation SUP-4069
The description for mounting a folder via WebDAV has been updated. Please note that the WebDAV feature is deprecated.
Bugfix SUP-4235
When using MariaDB in the backend, the session handling could cause some locks in the database, which caused SGBs. This has been fixed now.
Bugfix SUP-4110
When the license key of an installation was changed during reactivation, the global prefix was not immediately changed to the new license key, but only when the Tomcat was restarted. This has been fixed now.
Bugfix SUP-4017
The check for the DB triggers on JVM startup failed to detect non-existent Definers in triggers. This could happen, when the user with which the database was originally created was dropped, or when the triggers were migrated between systems. The trigger check has been changed now, so that triggers with non-existent Definers will be dropped and recreated upon startup of the CMS JVM.
Bugfix SUP-4545
The contentnode-restapi maven module dependencies have been updated. Various mandatory jersey client libraries are now included via the compile time scope setting.
Bugfix SUP-4492
When the group assignment of users were changed, objects that were created, edited or published by that user were unnecessarily queued for republishing. This has been fixed now.
Bugfix SUP-4236
When the upload of a file fails, because of problems with the file upload manipulator (e.g. timeout), the error message shown to the user has been improved.
Bugfix SUP-4000
Synchronizing pages between channels sometimes produced an error, when they either contained tags from constructs with multiple parts that had no keyword, or when tags with the same name used different constructs. Those issues have been fixed now.
New UI Update
- Display a notification when maintenance mode is active (ContentNode >= 5.27)
- No longer prevent events from implementation-specific scripts in edit frame
- Don‘t mark pages as locked when previewing or when user has no edit permissions
- Fix behavior of “synchronize channel with master” modal
Gentics Content.Node 5.26.16
Bugfix SUP-4274
When copying an existing tag inside the same page (with the copy-tags feature activated) and deleting the original tag afterwards the page could not be saved because of a JavaScript error. This has been fixed now.
Bugfix SUP-4372
When editing a page with Aloha Editor and clicking the “Cancel“ link in the assistant frame, the intermediate state of the page was saved and the page still locked. This has been fixed now, so that “Cancel“ from the assistant frame works exactly like “Cancel” from the main menu.
Bugfix SUP-4430
Under special circumstances, the automatic recreation of missing images in the GenticsImageStore while publishing into the filesystem failed, which caused a failure of the publish process. This has been fixed now.
Bugfix SUP-4360
When a new user was created, the user list fetched from the REST API via /rest/user/list did not show the new user immediately due to caches not being invalidated. This has been fixed now.
Bugfix SUP-4358
Fixed an error in the REST API, which could lead to recurrent NullPointerExceptions.
New UI Update
- Use correct item permissions when searching
- Open page preview when clicking a page in favourites list
- Fix page status after publishing pages with time management
- Fix inbox message parsing for edge-cases
Gentics Content.Node 5.26.15
New UI Update
- Add error message when new passwords do not match
- Fix missing scrollbars in sidebar “messages“ and “favourites” components in FF & IE11
- Correctly detect and handle errors from the REST API
New UI Update
- Mark page as changed after submitting tagfill dialog
- Enable publish button when page has unsaved changes
- Don‘t show “save/discard changes?” modal after publishing
New UI Update
- Increased performance and responsiveness across all browsers
- Navigation across items and edit modes now persist in the URL and browser history
- Improved confirmation prompt when navigating away from unsaved changes
- Hover intent for item list checkboxes improved
- Page status visible in repository browser
- Fix edge-cases with custom scripts for long-loading pages
- Fix missing cancel button in certain tagfill dialogs
- Fix time management modal inconsistency in edge-cases
- Fix creation & edit date in file/image preview
- Fix file upload issues for Firefox 45
- Fix breadcrumb styling on deep navigation
- Item list no longer jumps when using pagination
- Start page icon now more obvious and added to repository browser
- Buttons in edit panel rearranged & improved
- Publishing a page closes the edit panel
- Folder list is scrolled to top on navigation
- Better error messages for failed file uploads
Gentics Content.Node 5.26.14
Bugfix SUP-4193
Fixed logging in not working for IPv6 HTTP clients.
Gentics Content.Node 5.26.13
Deleting an item from the wastebin has been renamed from “Remove from wastebin“ to “Delete“ for usability reasons, so that it‘s better distinguishable from the “Restore” operation.
Optional Manual Change
Changed the Tomcat maxThreads setting to 256 for the AJP connector in server.xml in the default package configuration. If your Apache webserver is allowing more than 200 connections you will need to make sure that the Tomcat can also handle at least as many connections (MaxThreads) as the MaxClients setting in Apache (default 256). Please configure this in server.xml for AJP connector if not already done in order to avoid errors.
Bugfix SUP-4108
Enhanced an error message that occured when deleting on object in the CMS with the UI or pageimport and the object was already deleted.
Bugfix SUP-4135
Under special circumstances, the URL to translate a page could lead to an SGB. This has been fixed now.
Bugfix SUP-3980
Logged rendering errors will now include more specific information, which object was rendered when the error occurred.
Gentics Content.Node 5.26.12
Optional Manual Change
Updated the Oracle JDBC connector to 5.1.41 in order to fix a bug with MySQL 5.7 where the CMS would throw an error when trying to check and update the MySQL database triggers. For newer MySQL server versions the JDBC connector will now use SSL for connections by default. However SSL also comes with a performance impact. If you don‘t need SSL for connections to the MySQL database (eg.: when MySQL is running on the same server), we recommend to turn SSL off by adding useSSL=false to the MySQL JDBC URL.
This is done in the node.conf of your cms installation. By default the configuration file is found at /Node/etc/conf.d/node.db.conf. If there is no such file – create it.
In the node.db.conf create the following entry:
bc. $SETTINGS[“jdbcparameters“] = “useSSL=false“;
If the jdbcparameters index is already set concatenate parameters with “&“ like
bc. $SETTINGS[“jdbcparameters“] = “someOtherParam=1&useSSL=false”;
When using SSL, server certificate verification should be enabled and configured properly according to the MySQL documentation. See Connecting Securely Using SSL for more information.
Bugfix SUP-4082
When the permission to view pages was granted through roles, the pages were not always shown in the page list correctly. Especially the list of pages using other items (like specific images) was not always correct. This has been fixed now.
Bugfix SUP-4081
Some icons in the CMS UI were missing tooltips, which have been added now.
Bugfix SUP-4079
When using the “cancel” action from the related links from the translation split view, the split view was not closed, but showed the page list in the lower part. This has been fixed, cancel will now close the split view and show the page list in the whole frame.
Bugfix SUP-4111
When tags of a template were changed to use a different construct, the synchronization with pages did not change the tags in the page, if the page was imported. This has been fixed now, synchronization of pages with their templates will now work regardless of how the page was created.
Gentics Content.Node 5.26.11
Documentation SUP-4037
Added missing documentation for the getItems method in FolderResource.
Documentation SUP-4006
Added MySQL 5.7 to the list of tested database systems in the compatibility documentation.
Bugfix SUP-3543
In certain situations closing the tagfill dialog in a page could cause the scrollbar to jump to the beginning of the page or editable. This has been fixed. After closing the tagfill, the page will now remain on the same positions as before the tagfill was opened.
Bugfix SUP-4021
When objects were moved between channels, the search for conflicting localized copies did not always check the wastebin, which could cause data inconsistencies. When objects were moved between folders, localized copies in the wastebin did not always get the new folder set. Both issues have been fixed now.
Bugfix
Fixed a special case where a language variant page in the wastebin would not be deleted when translating a page with the /page/translate Rest endpoint.
Bugfix SUP-3991
In certain situations, rendering a link to another page with the channel directive would render ‘#‘ even for online pages in the preview and in instant publishing. Rendering the page with the regular publish process always rendered the link correctly. This issue has been fixed now.
Bugfix SUP-3288
When tags in a page were deleted while restoring an older version of the page, some database records in sub tables (like value) where not properly cleaned. This could cause subsequent errors during an import and has been fixed now.
Bugfix SUP-3997
Copying a Node could fail with a NullPointeException. This has been fixed.
Bugfix SUP-3914
Requests to the REST API endpoint /file/save/{id} with Content-Type: multipart/form-data (for fileuploads) with Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 (or something similar, which preferred xml over json as response) always caused an Internal Server Error (500) response. This has been fixed now.
Gentics Content.Node 5.26.10
Documentation SUP-3934
Added missing documentation on how to setup support for Oracle or SQL-Server Content Repositories in the CMS.
Documentation SUP-3952
A page with details on the “ExpressionParser for TagMap Entries” has been added to the documentation.
Bugfix SUP-3915
JavaScript errors thrown in a PubSub-event-handler in the GCN-JS-API caused an immediate stop of the script‘s execution and could lead to an inconsistent state in the JS-API in the browser. This has been fixed: all errors thrown by an event-handler will be catched and logged back to the console.
Bugfix SUP-3926
The permission checks for some rarely used administrative functions have been improved.
Bugfix SUP-3592
When objects were exported that referenced objects of other nodes, an optional reference to the node was created, even if the referenced object was in the wastebin. When objects were exported that contained objects of other nodes in an overview with sticky channel, no optional reference to the other node was created. Both issues have been fixed now.
Bugfix SUP-3301
Fixed the permissions “Create / edit tagtype“ and “Channel sync“ for the “GCN5 Demo” node not being set for the node group.
Gentics Content.Node 5.26.9
Bugfix SUP-3591
When a node is copied (with pages) and objects reference pages in the wastebin, the copies of the objects would reference the same pages, which caused unexpected results, when the reference pages were restored from the wastebin. This has been fixed now, references to pages in the wastebin will be unset for the copied objects.
Bugfix SUP-3867
Some actions in the CMS (like e.g. filling a tagtype) could lead to SGBs, when they were performed with a fresh session without selecting a node first. This has been fixed now.
Bugfix SUP-3908
When groups with subgroups were deleted in the CMS, the Java caches were not properly cleared, which could cause subsequent errors. This has been fixed now.
Bugfix SUP-3871
When using the feature copy_tags to Copy & Paste multiple tags at once, the tags were copied but not inserted at the paste position due to a javascript error. This has been fixed now.
Bugfix SUP-3873
When an update of an import would remove a template in the CMS, which is still used by pages, the resulting conflict could be handled with the behaviour “Overwrite“ which would remove the template and leave the pages in an inconsistent state. This has been fixed now, such conflicts can now only be handled with behaviour “Ignore” (leaving the template untouched).
Bugfix SUP-3876
When translating a page to the same language that already exists in the wastebin and as not deleted page, it was possible that the translation would create a duplicate of that page. This has been fixed now.
Bugfix SUP-3832
The menu items and related links in the assistant frame for tagtypes were inconsistent for users with view but without edit permission. The entries have been changed to be consistent now.
Gentics Content.Node 5.26.8
Enhancement SUP-3699
It is now possible to use a custom location for the configuration file of the Task Management App (gentics-activiti.properties). This is useful when the application server on which the Task Management App is deployed does not have access to the /Node/etc/ directory which is the default location for the configuration file.
Documentation SUP-3884
The documentation of imps has been improved in the Gentics CMS Guides
Bugfix SUP-3897
Some inefficient SQL statements for updating data from the tagfill dialog have been improved.
Bugfix SUP-3878
Some german umlauts were wrongly encoded. This bug only affected the cms webinterface. This has been fixed.
Bugfix SUP-3725
The internal pools for prepared SQL statements used large amounts of Java Heap Space, which could cause memory problems (including OutOfMemory exceptions). Therefore pooling of SQL Statements has been disabled.
Bugfix SUP-3857
Flash movies stored in the CMS could not be viewed in pages in preview-mode or edit-mode because the cms delivered them as attachment to the browser. (HTTP-header “Content-Disposition: attachment; filename=example.swf“) This has been fixed, the CMS will now set the proper HTTP-headers for flash videos. Additionally to get flash videos working in the CMS it is necessary to set the proper “type“ and “data” attributes on the flash OBJECT-html-tag, e.g.: <object type="application/x-shockwave-flash" data="<node videourl>">
Gentics Content.Node 5.26.7
Documentation SUP-2680
Updated documentation to avoid a common mistake in velocity implementions from tagtypes that are editable with the aloha editor.
Bugfix SUP-3601
When a user tried to create a language variant of a page, where this language variant was put into the wastebin before, and the user had no permission to delete pages in the folder, an error occurred. This has been fixed now: The page in the wastebin will be deleted regardless of the user‘s permission and replaced by the node language variant.
Bugfix SUP-3837
Files that were imported from a thirdparty media asset system using the file_fetch feature into folders with restricted inheritance (in a multichannelling environment), were not restricted in their inheritance, which subsequently caused errors in the publish process. This has been fixed now.
Bugfix SUP-3797
When publishing into a content repository with instant publishing, access to the content repository was locked longer and more often than necessary. This could cause congestion of instant publishing requests. This has been fixed now.
Bugfix SUP-3820
Fixed issue where corrupted node-tags (node-notation without tagname and closing bracket: “ If a tag contained javascript the code wasn‘t executed again after opening and closing the tagfill. This bug was introduced with bugfix SUP-3724 in version 5.23.28 and has been fixed. When rendering a tag of another page with the render directive, tags contained in the rendered tag were resolved in the scope of the original page. This has been fixed now. When a node publishes into a multichannelling aware contentrepository, all channels of the node will automatically also publish into that contentrepository. This auto-assignment was not shown in the list of nodes or considered when checking the data of the contentrepository for channels that were created after the node was assigned to the contentrepository. In such cases, the result of the “Check data“ operation for the contentrepository would incorrectly state, that the channel was not assigned to the contentrepository and its data would be removed in the next publish run (which was not the case). This has been fixed now. The “Check data” operation will correctly consider the auto-assignment of channels to multichannelling aware contentrepositories exactly like the publish process does. When objects were exported where the name contained some characters which are not allowed in attribute values of XML nodes, the resulting XML files was invalid. This caused errors while importing. Generation of the XML files has been fixed now, so that the invalid characters will be removed from the names. Additionally, the handling of invalid XML files while importing has been improved to provide explicit error messages hinting at the root cause. When selecting pages for an overview by clicking the language icon of the page in the repository browser, an SGB occurred while saving the tag. This has been fixed now. Objects containing nested object tags were exported and imported in way which could subsequently cause errors when loading those objects via the REST API. This has been fixed now. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated to prevent errors when saving a page. In Detail: The variable “$parts.fileurl.target.id” was used without checking if it was empty. This caused an erroneous rendering when the tag linked to a file that has been deleted preventing users to save a page after editing. The permission checks when localizing objects over the REST API were too restrictive for users with permissions restricted to channels. This has been fixed now. Copying a localized copy of a file always produced an error message. This has been fixed now. When a localized copy of a file is copied, the copy will be created in the same channel now. When publishing files into a ContentRepository, errors like When an object with localized copies in channels was moved (in its master node) and the node published into a Content Repository with Instant Publishing enabled, all localized copies were also instantly written into the Content Repository. This could cause the move process to take longer than expected and was inconsistent behaviour (since Instant Publishing normally does not affect inherited or localized copies in channels, when the master object was changed). This has been fixed now, moving objects will trigger Instant Publishing only for the master object itself. Applying object properties of folders to subfolders did not work for channel local or localized folders and has been fixed now. When a tag in a page is filled with the tagfill dialog, and a part of type The Part Types documentation has been updated. Various documentation issues were fixed. If the startpage of a folder was moved to the wastebin (deleted) the flag symbol indicating the startpage was still visible in the page list for other language variants of the same page. This could lead to the assumption that the folder has a startpage set when the startpage was deleted instead. This has been fixed. After modifying a tag in the tagfill when editing a page the tag in the page was not updated correctly if the root element of the tag changed. For example, if the root element from the tag changes from a When publishing multiple nodes (with their channels) into the same Multichannelling aware ContentRepository, the ContentRepository Maintenance action Fixed taking offline a page in the old UI not being completed via the Rest API. The Activiti trigger “onPageTakeOffline” didn‘t work because of this. When applying this update, the packaged Tomcat will be updated to version 7.0.73 which contains important security and bug fixes. You can delete old Tomcat directories after updating. Support for Red Hat Enterprise Linux 7.3 was added to Gentics CMS 5.25.0 – The RHEL Installation Guide has been updated. Fixed an SGB error when viewing a page in live preview mode in the new UI. The nodeId query parameter of the page resource search endpoint is no longer mandatory. It can now be specified in order to speed up or limit the search to a specific channel. Optional Manual Change The maximum number of clients used by the Apache Web Server for the CMS backend must not exceed 200, since this is the default value of maximum connections Tomcat will accept. Support for SUSE Linux Enterprise Server was added to Gentics CMS 5.25.0 – The SLES Installation Guide has been updated. The backup guide has been updated. Link anchors were removed from external links when saving a page if the Aloha Link Tagtype is missing the “anchor“ part or if the link plugin setting “anchorLinks” is set to false. This bug has been introduced with Gentics CMS 5.22.0. This has been fixed and the documentation for the Aloha Link Tagtype implementation has been updated to address link anchors. The script When the feature Two issues with the feature Showing the tag status failed with an SGB for templates that contain tags with special characters (like The new REST endpoint When uploading new files over the UI or the Rest API, it‘s possible now to overwrite existing files in the same folder that have the same file name. It is now possible to use different Media-RequestTypes in Rest-Requests when using the RestClientManager in Activiti-Tasks Fixed a bug where duplicate pages with the same name and filename would be created when copying multiple pages to another folder and the user would double click the folder name link. Fixed that the assigned content repository was not saved when using the rest methods /node/create or /node/save with a new content repository ID. Fixed that Rest API requests to /auth/login failed when the User-Agent header was empty. A set User-Agent ist not required for HTTP requests. The fix for SUP-4530 “When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now.” has been extended to work under all circumstances. Some UI errors for export of channels have been fixed: Clicking ‘Back to the folder‘ before uploading a new file or image did nothing. Now it works as intended. Feature invalidpageurlmsg: Fixed that deleting a page from the wastebin generated an inbox message when the page was references by a link in another page. The message will be only sent anymore when the page is moved to the wastebin. When using the gcnfileupload Aloha Editor Plugin to upload files, the file upload dialog did not always close after successful upload. This has been fixed now. Fixed user being notified for offline links unnecessarily when the source page also has been taken offline at the same time. The permission check of the REST API endpoint When restarting the Tomcat with the nodectl command, the script could hang in an infinite loop when the PID file doesn‘t exist. This has been fixed. A description for the feature Improved translation for documentation of breadcrumb part type. The description for mounting a folder via WebDAV has been updated. Please note that the WebDAV feature is deprecated. When using MariaDB in the backend, the session handling could cause some locks in the database, which caused SGBs. This has been fixed now. When the license key of an installation was changed during reactivation, the global prefix was not immediately changed to the new license key, but only when the Tomcat was restarted. This has been fixed now. The check for the DB triggers on JVM startup failed to detect non-existent Definers in triggers. This could happen, when the user with which the database was originally created was dropped, or when the triggers were migrated between systems. The trigger check has been changed now, so that triggers with non-existent Definers will be dropped and recreated upon startup of the CMS JVM. The contentnode-restapi maven module dependencies have been updated. Various mandatory jersey client libraries are now included via the compile time scope setting. When the group assignment of users were changed, objects that were created, edited or published by that user were unnecessarily queued for republishing. This has been fixed now. When the upload of a file fails, because of problems with the file upload manipulator (e.g. timeout), the error message shown to the user has been improved. Synchronizing pages between channels sometimes produced an error, when they either contained tags from constructs with multiple parts that had no keyword, or when tags with the same name used different constructs. Those issues have been fixed now. When copying an existing tag inside the same page (with the copy-tags feature activated) and deleting the original tag afterwards the page could not be saved because of a JavaScript error. This has been fixed now. When editing a page with Aloha Editor and clicking the “Cancel“ link in the assistant frame, the intermediate state of the page was saved and the page still locked. This has been fixed now, so that “Cancel“ from the assistant frame works exactly like “Cancel” from the main menu. Under special circumstances, the automatic recreation of missing images in the GenticsImageStore while publishing into the filesystem failed, which caused a failure of the publish process. This has been fixed now. When a new user was created, the user list fetched from the REST API via /rest/user/list did not show the new user immediately due to caches not being invalidated. This has been fixed now. Fixed an error in the REST API, which could lead to recurrent NullPointerExceptions. Fixed logging in not working for IPv6 HTTP clients. Deleting an item from the wastebin has been renamed from “Remove from wastebin“ to “Delete“ for usability reasons, so that it‘s better distinguishable from the “Restore” operation. Optional Manual Change Changed the Tomcat maxThreads setting to 256 for the AJP connector in server.xml in the default package configuration. If your Apache webserver is allowing more than 200 connections you will need to make sure that the Tomcat can also handle at least as many connections (MaxThreads) as the MaxClients setting in Apache (default 256). Please configure this in server.xml for AJP connector if not already done in order to avoid errors. Enhanced an error message that occured when deleting on object in the CMS with the UI or pageimport and the object was already deleted. Under special circumstances, the URL to translate a page could lead to an SGB. This has been fixed now. Logged rendering errors will now include more specific information, which object was rendered when the error occurred. Optional Manual Change Updated the Oracle JDBC connector to 5.1.41 in order to fix a bug with MySQL 5.7 where the CMS would throw an error when trying to check and update the MySQL database triggers. For newer MySQL server versions the JDBC connector will now use SSL for connections by default. However SSL also comes with a performance impact. If you don‘t need SSL for connections to the MySQL database (eg.: when MySQL is running on the same server), we recommend to turn SSL off by adding useSSL=false to the MySQL JDBC URL. This is done in the node.conf of your cms installation. By default the configuration file is found at When the permission to view pages was granted through roles, the pages were not always shown in the page list correctly. Especially the list of pages using other items (like specific images) was not always correct. This has been fixed now. Some icons in the CMS UI were missing tooltips, which have been added now. When using the “cancel” action from the related links from the translation split view, the split view was not closed, but showed the page list in the lower part. This has been fixed, cancel will now close the split view and show the page list in the whole frame. When tags of a template were changed to use a different construct, the synchronization with pages did not change the tags in the page, if the page was imported. This has been fixed now, synchronization of pages with their templates will now work regardless of how the page was created. Added missing documentation for the getItems method in FolderResource. Added MySQL 5.7 to the list of tested database systems in the compatibility documentation. In certain situations closing the tagfill dialog in a page could cause the scrollbar to jump to the beginning of the page or editable. This has been fixed. After closing the tagfill, the page will now remain on the same positions as before the tagfill was opened. When objects were moved between channels, the search for conflicting localized copies did not always check the wastebin, which could cause data inconsistencies. When objects were moved between folders, localized copies in the wastebin did not always get the new folder set. Both issues have been fixed now. Fixed a special case where a language variant page in the wastebin would not be deleted when translating a page with the /page/translate Rest endpoint. In certain situations, rendering a link to another page with the channel directive would render ‘#‘ even for online pages in the preview and in instant publishing. Rendering the page with the regular publish process always rendered the link correctly. This issue has been fixed now. When tags in a page were deleted while restoring an older version of the page, some database records in sub tables (like value) where not properly cleaned. This could cause subsequent errors during an import and has been fixed now. Copying a Node could fail with a NullPointeException. This has been fixed. Requests to the REST API endpoint Added missing documentation on how to setup support for Oracle or SQL-Server Content Repositories in the CMS. A page with details on the “ExpressionParser for TagMap Entries” has been added to the documentation. JavaScript errors thrown in a PubSub-event-handler in the GCN-JS-API caused an immediate stop of the script‘s execution and could lead to an inconsistent state in the JS-API in the browser. This has been fixed: all errors thrown by an event-handler will be catched and logged back to the console. The permission checks for some rarely used administrative functions have been improved. When objects were exported that referenced objects of other nodes, an optional reference to the node was created, even if the referenced object was in the wastebin. When objects were exported that contained objects of other nodes in an overview with sticky channel, no optional reference to the other node was created. Both issues have been fixed now. Fixed the permissions “Create / edit tagtype“ and “Channel sync“ for the “GCN5 Demo” node not being set for the node group. When a node is copied (with pages) and objects reference pages in the wastebin, the copies of the objects would reference the same pages, which caused unexpected results, when the reference pages were restored from the wastebin. This has been fixed now, references to pages in the wastebin will be unset for the copied objects. Some actions in the CMS (like e.g. filling a tagtype) could lead to SGBs, when they were performed with a fresh session without selecting a node first. This has been fixed now. When groups with subgroups were deleted in the CMS, the Java caches were not properly cleared, which could cause subsequent errors. This has been fixed now. When using the feature When an update of an import would remove a template in the CMS, which is still used by pages, the resulting conflict could be handled with the behaviour “Overwrite“ which would remove the template and leave the pages in an inconsistent state. This has been fixed now, such conflicts can now only be handled with behaviour “Ignore” (leaving the template untouched). When translating a page to the same language that already exists in the wastebin and as not deleted page, it was possible that the translation would create a duplicate of that page. This has been fixed now. The menu items and related links in the assistant frame for tagtypes were inconsistent for users with view but without edit permission. The entries have been changed to be consistent now. It is now possible to use a custom location for the configuration file of the Task Management App (gentics-activiti.properties). This is useful when the application server on which the Task Management App is deployed does not have access to the The documentation of imps has been improved in the Gentics CMS Guides Some inefficient SQL statements for updating data from the tagfill dialog have been improved. Some german umlauts were wrongly encoded. This bug only affected the cms webinterface. This has been fixed. The internal pools for prepared SQL statements used large amounts of Java Heap Space, which could cause memory problems (including OutOfMemory exceptions). Therefore pooling of SQL Statements has been disabled. Flash movies stored in the CMS could not be viewed in pages in preview-mode or edit-mode because the cms delivered them as attachment to the browser. (HTTP-header “Content-Disposition: attachment; filename=example.swf“) This has been fixed, the CMS will now set the proper HTTP-headers for flash videos. Additionally to get flash videos working in the CMS it is necessary to set the proper “type“ and “data” attributes on the flash OBJECT-html-tag, e.g.: Updated documentation to avoid a common mistake in velocity implementions from tagtypes that are editable with the aloha editor. When a user tried to create a language variant of a page, where this language variant was put into the wastebin before, and the user had no permission to delete pages in the folder, an error occurred. This has been fixed now: The page in the wastebin will be deleted regardless of the user‘s permission and replaced by the node language variant. Files that were imported from a thirdparty media asset system using the When publishing into a content repository with instant publishing, access to the content repository was locked longer and more often than necessary. This could cause congestion of instant publishing requests. This has been fixed now. Fixed issue where corrupted node-tags (node-notation without tagname and closing bracket: “ If a tag contained javascript the code wasn‘t executed again after opening and closing the tagfill. This bug was introduced with bugfix SUP-3724 in version 5.23.28 and has been fixed. When rendering a tag of another page with the render directive, tags contained in the rendered tag were resolved in the scope of the original page. This has been fixed now. When a node publishes into a multichannelling aware contentrepository, all channels of the node will automatically also publish into that contentrepository. This auto-assignment was not shown in the list of nodes or considered when checking the data of the contentrepository for channels that were created after the node was assigned to the contentrepository. In such cases, the result of the “Check data“ operation for the contentrepository would incorrectly state, that the channel was not assigned to the contentrepository and its data would be removed in the next publish run (which was not the case). This has been fixed now. The “Check data” operation will correctly consider the auto-assignment of channels to multichannelling aware contentrepositories exactly like the publish process does. When objects were exported where the name contained some characters which are not allowed in attribute values of XML nodes, the resulting XML files was invalid. This caused errors while importing. Generation of the XML files has been fixed now, so that the invalid characters will be removed from the names. Additionally, the handling of invalid XML files while importing has been improved to provide explicit error messages hinting at the root cause. When selecting pages for an overview by clicking the language icon of the page in the repository browser, an SGB occurred while saving the tag. This has been fixed now. Objects containing nested object tags were exported and imported in way which could subsequently cause errors when loading those objects via the REST API. This has been fixed now. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated to prevent errors when saving a page. In Detail: The variable “$parts.fileurl.target.id” was used without checking if it was empty. This caused an erroneous rendering when the tag linked to a file that has been deleted preventing users to save a page after editing. The permission checks when localizing objects over the REST API were too restrictive for users with permissions restricted to channels. This has been fixed now. Copying a localized copy of a file always produced an error message. This has been fixed now. When a localized copy of a file is copied, the copy will be created in the same channel now. When publishing files into a ContentRepository, errors like When an object with localized copies in channels was moved (in its master node) and the node published into a Content Repository with Instant Publishing enabled, all localized copies were also instantly written into the Content Repository. This could cause the move process to take longer than expected and was inconsistent behaviour (since Instant Publishing normally does not affect inherited or localized copies in channels, when the master object was changed). This has been fixed now, moving objects will trigger Instant Publishing only for the master object itself. Applying object properties of folders to subfolders did not work for channel local or localized folders and has been fixed now. When a tag in a page is filled with the tagfill dialog, and a part of type The Part Types documentation has been updated. If the startpage of a folder was moved to the wastebin (deleted) the flag symbol indicating the startpage was still visible in the page list for other language variants of the same page. This could lead to the assumption that the folder has a startpage set when the startpage was deleted instead. This has been fixed. After modifying a tag in the tagfill when editing a page the tag in the page was not updated correctly if the root element of the tag changed. For example, if the root element from the tag changes from a When publishing multiple nodes (with their channels) into the same Multichannelling aware ContentRepository, the ContentRepository Maintenance action Fixed taking offline a page in the old UI not being completed via the Rest API. The Activiti trigger “onPageTakeOffline” didn‘t work because of this. When applying this update, the packaged Tomcat will be updated to version 7.0.73 which contains important security and bug fixes. You can delete old Tomcat directories after updating. Fixed an SGB error when viewing a page in live preview mode in the new UI. The nodeId query parameter of the page resource search endpoint is no longer mandatory. It can now be specified in order to speed up or limit the search to a specific channel. Optional Manual Change The maximum number of clients used by the Apache Web Server for the CMS backend must not exceed 200, since this is the default value of maximum connections Tomcat will accept. Support for SUSE Linux Enterprise Server was added to Gentics CMS 5.25.0 – The SLES Installation Guide has been updated. The backup guide has been updated. Link anchors were removed from external links when saving a page if the Aloha Link Tagtype is missing the “anchor“ part or if the link plugin setting “anchorLinks” is set to false. This bug has been introduced with Gentics CMS 5.22.0. This has been fixed and the documentation for the Aloha Link Tagtype implementation has been updated to address link anchors. The script When the feature Two issues with the feature Showing the tag status failed with an SGB for templates that contain tags with special characters (like Optional Manual Change When using Internet Explorer in the Task Management UI, a small ‘x‘ button was shown in the search field, which cleared the search field, but had no effect on the search itself. This ‘x‘ button has now been removed. When opening a page for editing the event aloha-ready was never fired if the page contained no editable tags. This event should be triggered when the Aloha Editor is fully initialized. This has been fixed. When translating a local page inside a channel without specifying the channel, the check whether the translation already exists didn‘t work and another language variant of the same page with the same language was created. This has been fixed. When editing a page with Aloha Editor and an editable is activated, additional paragraphs are added in places where they are necessary in order to place the cursor in front of or after blocks. Those editables were only added to the activated editable and removed from any inactive editable, even if the active editable was nested in a block in another editable. This behaviour has been changed now, so that the paragraphs will be added to all ancestor editables of the active editable. Updated the new CMS UI to version 1.2.3 The guides for the Url Parttypes were updated to describe the size property which is a formatted string in KB or MB and not to be confused with Optional Manual Change In the Task Management the list of Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. When a page was edited outside the backend UI (e.g. via frontend editing or using the new UI) and a new file was uploaded from within the tagfill dialog, an SGB could occur. This has been fixed now. When moving a localized folder in a multichannelling environment, the localized copies did not get their parent‘s folder_id updated in the content repository. This has been fixed now. The maintenance action “Check data“ for multichannelling contentrepositories did not identify objects in channels that should have been overwritten by localized copies. Also, the check only would set the data status to “error” if invalid objects were found in the master node, but not, if invalid objects only existed in channels. Both issues have been fixed now. When using the extended search for pages in the root folder of a channel, it was not possible to restrict to templates, this has been fixed now. Opening the tagfill produced an error if the tagtype contained a non empty Page-URL part linking to an internal page. This has been fixed. Localization of templates failed with an error. This has been fixed now. Saving an overview listing folders in the tagfill dialog failed with an SGB. This has been fixed now. When evaluation of tagmap entries failed with unexpected errors (like NullPointerException) while publishing an object into a content repository, the logged error suppressed the expression causing the error. This has been fixed now. The statement used to get the templates using a specific page (in a pagetag) was inefficient and could cause timeouts in the page list. This has been fixed now. Selecting some text in the tagfill with the chrome browser was not working as expected after opening and closing the RepositoryBrowser without selecting any objects. This has been fixed. Fixed possible NPE in the publish process. Some minor issues with the detection of GCMS version numbers from local updatefiles have been fixed. The regexes contained in the package, which can be used for text parts of constructs did not have proper english translations, which have been added now. When a localized or local page was edited in a channel, the setting for whether to use Aloha Editor was always taken from the master node, not from the channel. This has been fixed now. When a folder was moved into another folder with more restrictive inheritance settings (in a multichannelling environment), and the moved folder When a new tag was created in a page as copy of another tag with the Gentics Content.Node JavaScript API, the internal cache of the page was cleared which could lead to inconsistent behaviour. This has been fixed now. When the tagtype of an object property definition was changed, already existing object tags were not migrated, unless the change was done with the feature “tagtype migration”. This has been changed now. Existing object tags are migrated, when the object properties of an object are shown in the object properties dialog, or the object is loaded for editing. The script When a tagtype contained multiple parts of type The default upload folders for images and files could not be unset, once they were set. This has been fixed now. When the feature When using the feature When the type of a part in a construct was changed from When a page rendered the tag of another page, which rendered a velocity overview containing the original page, and a tag of the original page was rendered that resolved The repository browser didn‘t work in the tagfill dialog when the multichannelling feature was not enabled. This has been fixed. When editing a page with aloha editor, and a tag in an editable was refreshed (e.g. because the tag had been modified using the tagfill dialog), and the tag contained a nested tag in an editable, sometimes the order of initialization of the nested blocks and editables was incorrect and could cause side-effects. One of this side-effects was the automatic modification of editables through the browser when using internet explorer by inserting a br-tag. The initialization order of nested tags has been fixed now. Purging the wastebin from many deleted folders consumed a big amount of memory, which could cause OutOfMemory errors. This has been fixed now. Updated the new CMS UI to version 1.1.0. Resolving the nodeId for The guides on defining velocity macros in a library page were updated. They now recommend using tagtype “html (long)” to contain the velocity-code in the macro library page. If there was a publishrun between two imports of the same contentrepository, the second import would show a conflict for this contentrepository. This has been fixed. When a master object was deleted and localized at the same time (by different users), this could cause a data inconsistency. This has been fixed now. Setting the publish directory for a folder and all its subfolders may take a long time. This action has been modified to be continued in the background if it takes longer than 5 seconds. Before this fix, the long running request could cause a timeout, which was shown as error in the properties dialog of the folder. When copying a node together with its templates and some of the templates were assigned to folders in other nodes, the copies of those templates were also assigned to the folders of the other nodes. This has been fixed now. The copied templates will only be assigned to folders of the node copy. In multichannelling environments, the dependencies of images were sometimes not stored correctly, which could cause the automatic dirting mechanism to fail dirting images. This has been fixed now. This change does not automatically fix probably missing dependencies, in order to recalculate the dependencies, it is necessary to republish all files from the maintenance dialog. When images are uploaded where the DPI cannot be determined, the DPI was set to 72 per default. This has been changed now, so that the DPI is internally set to 0. The image list will now show ‘N/A‘ for the DPI value in such cases. Images that are already uploaded will not be affected by this change, unless they are uploaded again. Manual Change The new Gentics CMS UI requires an additional symlink within the htdocs folder. You can create the needed symlink using the following command: It is now possible to deactivate default Aloha Editor Plugins in general or on a per node basis. Please consult the Guides for further information. The following part types have been extended to store the node from which internal target objects were selected: Those part types will expose the node as attribute The part type The REST responses of FileLoadResponse, ImageLoadResponse, PageLoadResponse and FolderLoadResponse have been enhanced. Additional fields (masterNodeId, inheritedFromId) which identify the corresponding multichanneling nodes via id have been added. The REST API has been enhanced: An additional REST endpoint for users has been added. The endpoint rest/user/save/{id} can be used to update user specific information. The inheritedFromId, and masterNodeId fields have been added to the NodeLoadResponse. These fields contain the structural information that is needed to build up the node/channel tree. A description for the feature Improved translation for documentation of breadcrumb part type. The description for mounting a folder via WebDAV has been updated. Please note that the WebDAV feature is deprecated. When using MariaDB in the backend, the session handling could cause some locks in the database, which caused SGBs. This has been fixed now. When the license key of an installation was changed during reactivation, the global prefix was not immediately changed to the new license key, but only when the Tomcat was restarted. This has been fixed now. The check for the DB triggers on JVM startup failed to detect non-existent Definers in triggers. This could happen, when the user with which the database was originally created was dropped, or when the triggers were migrated between systems. The trigger check has been changed now, so that triggers with non-existent Definers will be dropped and recreated upon startup of the CMS JVM. The contentnode-restapi maven module dependencies have been updated. Various mandatory jersey client libraries are now included via the compile time scope setting. When the group assignment of users were changed, objects that were created, edited or published by that user were unnecessarily queued for republishing. This has been fixed now. When the upload of a file fails, because of problems with the file upload manipulator (e.g. timeout), the error message shown to the user has been improved. Synchronizing pages between channels sometimes produced an error, when they either contained tags from constructs with multiple parts that had no keyword, or when tags with the same name used different constructs. Those issues have been fixed now. When copying an existing tag inside the same page (with the copy-tags feature activated) and deleting the original tag afterwards the page could not be saved because of a JavaScript error. This has been fixed now. When editing a page with Aloha Editor and clicking the “Cancel“ link in the assistant frame, the intermediate state of the page was saved and the page still locked. This has been fixed now, so that “Cancel“ from the assistant frame works exactly like “Cancel” from the main menu. Under special circumstances, the automatic recreation of missing images in the GenticsImageStore while publishing into the filesystem failed, which caused a failure of the publish process. This has been fixed now. When a new user was created, the user list fetched from the REST API via /rest/user/list did not show the new user immediately due to caches not being invalidated. This has been fixed now. Fixed an error in the REST API, which could lead to recurrent NullPointerExceptions. Fixed logging in not working for IPv6 HTTP clients. Deleting an item from the wastebin has been renamed from “Remove from wastebin“ to “Delete“ for usability reasons, so that it‘s better distinguishable from the “Restore” operation. Optional Manual Change Changed the Tomcat maxThreads setting to 256 for the AJP connector in server.xml in the default package configuration. If your Apache webserver is allowing more than 200 connections you will need to make sure that the Tomcat can also handle at least as many connections (MaxThreads) as the MaxClients setting in Apache (default 256). Please configure this in server.xml for AJP connector if not already done in order to avoid errors. Enhanced an error message that occured when deleting on object in the CMS with the UI or pageimport and the object was already deleted. Under special circumstances, the URL to translate a page could lead to an SGB. This has been fixed now. Logged rendering errors will now include more specific information, which object was rendered when the error occurred. Optional Manual Change Updated the Oracle JDBC connector to 5.1.41 in order to fix a bug with MySQL 5.7 where the CMS would throw an error when trying to check and update the MySQL database triggers. For newer MySQL server versions the JDBC connector will now use SSL for connections by default. However SSL also comes with a performance impact. If you don‘t need SSL for connections to the MySQL database (eg.: when MySQL is running on the same server), we recommend to turn SSL off by adding useSSL=false to the MySQL JDBC URL. This is done in the node.conf of your cms installation. By default the configuration file is found at When the permission to view pages was granted through roles, the pages were not always shown in the page list correctly. Especially the list of pages using other items (like specific images) was not always correct. This has been fixed now. Some icons in the CMS UI were missing tooltips, which have been added now. When using the “cancel” action from the related links from the translation split view, the split view was not closed, but showed the page list in the lower part. This has been fixed, cancel will now close the split view and show the page list in the whole frame. When tags of a template were changed to use a different construct, the synchronization with pages did not change the tags in the page, if the page was imported. This has been fixed now, synchronization of pages with their templates will now work regardless of how the page was created. Added missing documentation for the getItems method in FolderResource. Added MySQL 5.7 to the list of tested database systems in the compatibility documentation. In certain situations closing the tagfill dialog in a page could cause the scrollbar to jump to the beginning of the page or editable. This has been fixed. After closing the tagfill, the page will now remain on the same positions as before the tagfill was opened. When objects were moved between channels, the search for conflicting localized copies did not always check the wastebin, which could cause data inconsistencies. When objects were moved between folders, localized copies in the wastebin did not always get the new folder set. Both issues have been fixed now. Fixed a special case where a language variant page in the wastebin would not be deleted when translating a page with the /page/translate Rest endpoint. In certain situations, rendering a link to another page with the channel directive would render ‘#‘ even for online pages in the preview and in instant publishing. Rendering the page with the regular publish process always rendered the link correctly. This issue has been fixed now. When tags in a page were deleted while restoring an older version of the page, some database records in sub tables (like value) where not properly cleaned. This could cause subsequent errors during an import and has been fixed now. Copying a Node could fail with a NullPointeException. This has been fixed. Requests to the REST API endpoint Added missing documentation on how to setup support for Oracle or SQL-Server Content Repositories in the CMS. A page with details on the “ExpressionParser for TagMap Entries” has been added to the documentation. JavaScript errors thrown in a PubSub-event-handler in the GCN-JS-API caused an immediate stop of the script‘s execution and could lead to an inconsistent state in the JS-API in the browser. This has been fixed: all errors thrown by an event-handler will be catched and logged back to the console. The permission checks for some rarely used administrative functions have been improved. Fixed the permissions “Create / edit tagtype“ and “Channel sync“ for the “GCN5 Demo” node not being set for the node group. When a node is copied (with pages) and objects reference pages in the wastebin, the copies of the objects would reference the same pages, which caused unexpected results, when the reference pages were restored from the wastebin. This has been fixed now, references to pages in the wastebin will be unset for the copied objects. Some actions in the CMS (like e.g. filling a tagtype) could lead to SGBs, when they were performed with a fresh session without selecting a node first. This has been fixed now. When groups with subgroups were deleted in the CMS, the Java caches were not properly cleared, which could cause subsequent errors. This has been fixed now. When using the feature When an update of an import would remove a template in the CMS, which is still used by pages, the resulting conflict could be handled with the behaviour “Overwrite“ which would remove the template and leave the pages in an inconsistent state. This has been fixed now, such conflicts can now only be handled with behaviour “Ignore” (leaving the template untouched). When translating a page to the same language that already exists in the wastebin and as not deleted page, it was possible that the translation would create a duplicate of that page. This has been fixed now. The menu items and related links in the assistant frame for tagtypes were inconsistent for users with view but without edit permission. The entries have been changed to be consistent now. It is now possible to use a custom location for the configuration file of the Task Management App (gentics-activiti.properties). This is useful when the application server on which the Task Management App is deployed does not have access to the The documentation of imps has been improved in the Gentics CMS Guides Some inefficient SQL statements for updating data from the tagfill dialog have been improved. Some german umlauts were wrongly encoded. This bug only affected the cms webinterface. This has been fixed. The internal pools for prepared SQL statements used large amounts of Java Heap Space, which could cause memory problems (including OutOfMemory exceptions). Therefore pooling of SQL Statements has been disabled. Flash movies stored in the CMS could not be viewed in pages in preview-mode or edit-mode because the cms delivered them as attachment to the browser. (HTTP-header “Content-Disposition: attachment; filename=example.swf“) This has been fixed, the CMS will now set the proper HTTP-headers for flash videos. Additionally to get flash videos working in the CMS it is necessary to set the proper “type“ and “data” attributes on the flash OBJECT-html-tag, e.g.: Updated documentation to avoid a common mistake in velocity implementions from tagtypes that are editable with the aloha editor. When a user tried to create a language variant of a page, where this language variant was put into the wastebin before, and the user had no permission to delete pages in the folder, an error occurred. This has been fixed now: The page in the wastebin will be deleted regardless of the user‘s permission and replaced by the node language variant. Files that were imported from a thirdparty media asset system using the When publishing into a content repository with instant publishing, access to the content repository was locked longer and more often than necessary. This could cause congestion of instant publishing requests. This has been fixed now. Fixed issue where corrupted node-tags (node-notation without tagname and closing bracket: “ If a tag contained javascript the code wasn‘t executed again after opening and closing the tagfill. This bug was introduced with bugfix SUP-3724 in version 5.23.28 and has been fixed. When rendering a tag of another page with the render directive, tags contained in the rendered tag were resolved in the scope of the original page. This has been fixed now. When a node publishes into a multichannelling aware contentrepository, all channels of the node will automatically also publish into that contentrepository. This auto-assignment was not shown in the list of nodes or considered when checking the data of the contentrepository for channels that were created after the node was assigned to the contentrepository. In such cases, the result of the “Check data“ operation for the contentrepository would incorrectly state, that the channel was not assigned to the contentrepository and its data would be removed in the next publish run (which was not the case). This has been fixed now. The “Check data” operation will correctly consider the auto-assignment of channels to multichannelling aware contentrepositories exactly like the publish process does. When objects were exported where the name contained some characters which are not allowed in attribute values of XML nodes, the resulting XML files was invalid. This caused errors while importing. Generation of the XML files has been fixed now, so that the invalid characters will be removed from the names. Additionally, the handling of invalid XML files while importing has been improved to provide explicit error messages hinting at the root cause. Objects containing nested object tags were exported and imported in way which could subsequently cause errors when loading those objects via the REST API. This has been fixed now. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated to prevent errors when saving a page. In Detail: The variable “$parts.fileurl.target.id” was used without checking if it was empty. This caused an erroneous rendering when the tag linked to a file that has been deleted preventing users to save a page after editing. The permission checks when localizing objects over the REST API were too restrictive for users with permissions restricted to channels. This has been fixed now. Copying a localized copy of a file always produced an error message. This has been fixed now. When a localized copy of a file is copied, the copy will be created in the same channel now. When publishing files into a ContentRepository, errors like When an object with localized copies in channels was moved (in its master node) and the node published into a Content Repository with Instant Publishing enabled, all localized copies were also instantly written into the Content Repository. This could cause the move process to take longer than expected and was inconsistent behaviour (since Instant Publishing normally does not affect inherited or localized copies in channels, when the master object was changed). This has been fixed now, moving objects will trigger Instant Publishing only for the master object itself. Applying object properties of folders to subfolders did not work for channel local or localized folders and has been fixed now. When a tag in a page is filled with the tagfill dialog, and a part of type The Part Types documentation has been updated. If the startpage of a folder was moved to the wastebin (deleted) the flag symbol indicating the startpage was still visible in the page list for other language variants of the same page. This could lead to the assumption that the folder has a startpage set when the startpage was deleted instead. This has been fixed. After modifying a tag in the tagfill when editing a page the tag in the page was not updated correctly if the root element of the tag changed. For example, if the root element from the tag changes from a When publishing multiple nodes (with their channels) into the same Multichannelling aware ContentRepository, the ContentRepository Maintenance action Fixed taking offline a page in the old UI not being completed via the Rest API. The Activiti trigger “onPageTakeOffline” didn‘t work because of this. When applying this update, the packaged Tomcat will be updated to version 7.0.73 which contains important security and bug fixes. You can delete old Tomcat directories after updating. Fixed an SGB error when viewing a page in live preview mode in the new UI. Optional Manual Change The maximum number of clients used by the Apache Web Server for the CMS backend must not exceed 200, since this is the default value of maximum connections Tomcat will accept. The backup guide has been updated. Link anchors were removed from external links when saving a page if the Aloha Link Tagtype is missing the “anchor“ part or if the link plugin setting “anchorLinks” is set to false. This bug has been introduced with Gentics CMS 5.22.0. This has been fixed and the documentation for the Aloha Link Tagtype implementation has been updated to address link anchors. The script When the feature Two issues with the feature Showing the tag status failed with an SGB for templates that contain tags with special characters (like Optional Manual Change When using Internet Explorer in the Task Management UI, a small ‘x‘ button was shown in the search field, which cleared the search field, but had no effect on the search itself. This ‘x‘ button has now been removed. When opening a page for editing the event aloha-ready was never fired if the page contained no editable tags. This event should be triggered when the Aloha Editor is fully initialized. This has been fixed. When translating a local page inside a channel without specifying the channel, the check whether the translation already exists didn‘t work and another language variant of the same page with the same language was created. This has been fixed. When editing a page with Aloha Editor and an editable is activated, additional paragraphs are added in places where they are necessary in order to place the cursor in front of or after blocks. Those editables were only added to the activated editable and removed from any inactive editable, even if the active editable was nested in a block in another editable. This behaviour has been changed now, so that the paragraphs will be added to all ancestor editables of the active editable. Optional Manual Change In the Task Management the list of Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. When a page was edited outside the backend UI (e.g. via frontend editing or using the new UI) and a new file was uploaded from within the tagfill dialog, an SGB could occur. This has been fixed now. When moving a localized folder in a multichannelling environment, the localized copies did not get their parent‘s folder_id updated in the content repository. This has been fixed now. The maintenance action “Check data“ for multichannelling contentrepositories did not identify objects in channels that should have been overwritten by localized copies. Also, the check only would set the data status to “error” if invalid objects were found in the master node, but not, if invalid objects only existed in channels. Both issues have been fixed now. When using the extended search for pages in the root folder of a channel, it was not possible to restrict to templates, this has been fixed now. Localization of templates failed with an error. This has been fixed now. When evaluation of tagmap entries failed with unexpected errors (like NullPointerException) while publishing an object into a content repository, the logged error suppressed the expression causing the error. This has been fixed now. The statement used to get the templates using a specific page (in a pagetag) was inefficient and could cause timeouts in the page list. This has been fixed now. Selecting some text in the tagfill with the chrome browser was not working as expected after opening and closing the RepositoryBrowser without selecting any objects. This has been fixed. Some minor issues with the detection of GCMS version numbers from local updatefiles have been fixed. The regexes contained in the package, which can be used for text parts of constructs did not have proper english translations, which have been added now. When a localized or local page was edited in a channel, the setting for whether to use Aloha Editor was always taken from the master node, not from the channel. This has been fixed now. When a folder was moved into another folder with more restrictive inheritance settings (in a multichannelling environment), and the moved folder When a new tag was created in a page as copy of another tag with the Gentics Content.Node JavaScript API, the internal cache of the page was cleared which could lead to inconsistent behaviour. This has been fixed now. When the tagtype of an object property definition was changed, already existing object tags were not migrated, unless the change was done with the feature “tagtype migration”. This has been changed now. Existing object tags are migrated, when the object properties of an object are shown in the object properties dialog, or the object is loaded for editing. The script When a tagtype contained multiple parts of type The default upload folders for images and files could not be unset, once they were set. This has been fixed now. The guides on defining velocity macros in a library page were updated. They now recommend using tagtype “html (long)” to contain the velocity-code in the macro library page. When the feature When using the feature When the type of a part in a construct was changed from When a page rendered the tag of another page, which rendered a velocity overview containing the original page, and a tag of the original page was rendered that resolved When editing a page with aloha editor, and a tag in an editable was refreshed (e.g. because the tag had been modified using the tagfill dialog), and the tag contained a nested tag in an editable, sometimes the order of initialization of the nested blocks and editables was incorrect and could cause side-effects. One of this side-effects was the automatic modification of editables through the browser when using internet explorer by inserting a br-tag. The initialization order of nested tags has been fixed now. Purging the wastebin from many deleted folders consumed a big amount of memory, which could cause OutOfMemory errors. This has been fixed now. If there was a publishrun between two imports of the same contentrepository, the second import would show a conflict for this contentrepository. This has been fixed. When a master object was deleted and localized at the same time (by different users), this could cause a data inconsistency. This has been fixed now. Setting the publish directory for a folder and all its subfolders may take a long time. This action has been modified to be continued in the background if it takes longer than 5 seconds. Before this fix, the long running request could cause a timeout, which was shown as error in the properties dialog of the folder. When copying a node together with its templates and some of the templates were assigned to folders in other nodes, the copies of those templates were also assigned to the folders of the other nodes. This has been fixed now. The copied templates will only be assigned to folders of the node copy. In multichannelling environments, the dependencies of images were sometimes not stored correctly, which could cause the automatic dirting mechanism to fail dirting images. This has been fixed now. This change does not automatically fix probably missing dependencies, in order to recalculate the dependencies, it is necessary to republish all files from the maintenance dialog. When images are uploaded where the DPI cannot be determined, the DPI was set to 72 per default. This has been changed now, so that the DPI is internally set to 0. The image list will now show ‘N/A‘ for the DPI value in such cases. Images that are already uploaded will not be affected by this change, unless they are uploaded again. The import has been fixed to not fail when an export bundle of a newer version of the Gentics CMS is imported, that contains new references that are marked as optional. The usage overview would always list all language variants of a page even though not all language variants used the object. The presentation has been fixed, so that each page using the object has its own entry in the list, but no symbols in the language column. When editables were modified during the page save process, a dialog could pop up that warns about unsaved changes. In order to prevent this dialog from appearing once the page was saved or published by the user, an additional check has been added. When a link was removed in a page, the corresponding link tag was not deleted when the page was saved. This has been fixed. Removing a localized object could cause multithreaded publish runs to fail when the attribute dirting and resumable publish process features were enabled. This has been fixed. Recursively changing the publish directory of a localized folder with the “include subfolders” option did not change the publish directory of its subfolders if they are also localized. This has been fixed. A possible NullPointerException during the publish run has been fixed. When using the feature Entering URLs in the filter field of the page and template listings could render the filter unusable, and the only way to reset it, was to reset the session. This has been fixed. When applying this update, the packaged Tomcat will be updated to version 7.0.70 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. The documentation of the Aloha Editor configuration has been extended to cover extension of the toolbar settings. A NullPointerException occured in the When an editable part of a construct was deleted, this could cause subsequent errors in the publish process when using the feature publish_cache due to incorrectly cleared caches. This has been fixed now. When using the Feature A tagpart of type “URL (page)“ was only treated as being “internal“, when the radio button for “internal“ was selected AND an actual internal page was selected. This caused new tags being marked as “external“, even if the default value was “internal“, but no default page selected. This has been fixed now, the property “internal” will now exactly reflect the setting of the radio buttons, regardless of whether an actual page is selected or not. A wrong permission check had the effect that the current folder was sometimes selected instead of the standard upload folder when uploading a file or an image in the tagfill. This happened if the user had no permissions for assigning user permission. This has been fixed. Now the current folder is only selected if the user has no permissions to view the standard upload folder. The list of exports was created using inefficient SQL statements. This could cause timeout problems depending on the number of exports on the system and the user‘s paging setting. This update will create an index to speed up calculation of the number of warnings per export. Note that the change in the database structure might take longer than normal updates. When a page is edited using Aloha Editor and the Tagfill Dialog is opened for a tag or the repository browser is opened, scrolling of the page is prevented. Fixed the top menu not changing, after viewing/editing a content page and changing to another CMS page with the assistant. When using the GCN JS API to create tags in pages as copy of other tags, the callback passed to the function When a new editable part is added to the construct used in object properties the existing object tags of objects were not properly updated when the object properties dialog was opened. This has been fixed now. When the feature When a page is opened in edit mode of Aloha Editor and not saved within 10 minutes, the user‘s lock of the page was automatically lifted. This allowed other users to also edit the page, not aware that their changes could be overwritten by the first user. This has been fixed so that the lock on the page is updated on a regular basis as long as the first user keeps the page open in edit mode of Aloha Editor. In some cases, an additional tag was automatically added to rendered page sources, containing a Gentics Copyright notice. This has been removed now. When using multithreaded publishing and a publish process failed, this could cause additional exceptions “Cannot add job to Multiconnection transaction: Worker thread is not running” to be logged. Handling of aborting publish processes with multithreaded publishing has been improved, so that exceptions will only be logged if they are a possible cause but not the consequence of the aborting process. The documentation of the Pageurl/Fileurl parttype now includes the information that the url property is only set for internal links. The scheduler will now show more detailed information (the complete stacktrace with causing exceptions), when the publish run fails with an exception. When a folder is deleted (put into the wastebin), a check was done for objects having localized copies in the structure, which would also be deleted. This check has been extended to also check for local objects (objects that were created in subchannels of the deleted folder‘s channel). When objects in a multichannelling environment were published into a contentrepository with the permission information added, the permissions of localized folders were not correctly inherited from their master folder. This has been fixed now. When the master page of a localized copy was taken offline, editors were notified that pages in the channel linking to the localized copy contained an invalid link now, although the link was still valid (linking the localized copy). This has been fixed now. When a new inline editable part was added to a construct and pages containing tags of that construct were edited using Aloha Editor, the new parts could not be filled unless the page was saved once. This has been fixed now. When saving nodes using the REST API, setting the publish directory to empty did not work. Also when setting the publish directory to “/”, this was not corrected to be saved as empty. Both issues have been fixed. When a specific magiclinkconstruct was configured, the links were still rendered as blocks (with edit icon) in edit mode. This has been fixed now. The synchronization of pages with changes made to template tags was inconsistent and has been modified: This fix contains a change in the database structure, which could cause the update to take longer than usual. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which has been fixed now. When editing the node properties and the checkbox “Separate directories“ is not checked, data entered in the field “Page directory“ should be copied into the (disabled) field “Binary directory”, which did not work. This has been fixed now. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. This has been fixed now. Objects (files, images, pages or folders) that were restored from the wastebin did not automatically republish other objects that directly referenced the restored object. This has been fixed now. The assistant frame would not show the correct number of images in a folder, when there was an active filter for the images. This has been fixed. When applying this update, the packaged Tomcat will be updated to version 7.0.70 which contains important security and bug fixes. You can delete the old Tomcat directories after updating. The instant publishing feature has been improved, so that a concurrent regular publish run will not overwrite its changes. The affected objects will stay marked for publication, and will be processed during the next regular publish run. The scheduler can start Activiti processes now. Please read the documentation for more information. Rest API: The FolderResource now supports sorting by the deletion date and the full user name who deleted an object (wastebin feature). When using the feature Publish Cache, the content maintenance dialog now has an option to clear the publish cache for pages that are dirted using the maintenance tool. Tagfill dialog: Changed the icon for clearing the selection of an URL object (pages, files, ...) to something more intuitive. It‘s now possible to copy an object property from a page language variant to the other language variants from within the pages object property list. The list in the wastebin view is now sortable by name, deletion date and user who deleted the object. The new feature Attribute Dirting can reduce publish times when publishing into Content Repositories by only dirting and rendering attributes, that depend on changed data. The “cancel” option to throw away all changes done to a page is now also available in the assistant frame. Added missing documentation for the getItems method in FolderResource. Added MySQL 5.7 to the list of tested database systems in the compatibility documentation. In certain situations closing the tagfill dialog in a page could cause the scrollbar to jump to the beginning of the page or editable. This has been fixed. After closing the tagfill, the page will now remain on the same positions as before the tagfill was opened. When objects were moved between channels, the search for conflicting localized copies did not always check the wastebin, which could cause data inconsistencies. When objects were moved between folders, localized copies in the wastebin did not always get the new folder set. Both issues have been fixed now. In certain situations, rendering a link to another page with the channel directive would render ‘#‘ even for online pages in the preview and in instant publishing. Rendering the page with the regular publish process always rendered the link correctly. This issue has been fixed now. When tags in a page were deleted while restoring an older version of the page, some database records in sub tables (like value) where not properly cleaned. This could cause subsequent errors during an import and has been fixed now. Copying a Node could fail with a NullPointeException. This has been fixed. Requests to the REST API endpoint Added missing documentation on how to setup support for Oracle or SQL-Server Content Repositories in the CMS. A page with details on the “ExpressionParser for TagMap Entries” has been added to the documentation. JavaScript errors thrown in a PubSub-event-handler in the GCN-JS-API caused an immediate stop of the script‘s execution and could lead to an inconsistent state in the JS-API in the browser. This has been fixed: all errors thrown by an event-handler will be catched and logged back to the console. The permission checks for some rarely used administrative functions have been improved. Fixed the permissions “Create / edit tagtype“ and “Channel sync“ for the “GCN5 Demo” node not being set for the node group. When a node is copied (with pages) and objects reference pages in the wastebin, the copies of the objects would reference the same pages, which caused unexpected results, when the reference pages were restored from the wastebin. This has been fixed now, references to pages in the wastebin will be unset for the copied objects. Some actions in the CMS (like e.g. filling a tagtype) could lead to SGBs, when they were performed with a fresh session without selecting a node first. This has been fixed now. When groups with subgroups were deleted in the CMS, the Java caches were not properly cleared, which could cause subsequent errors. This has been fixed now. When using the feature When an update of an import would remove a template in the CMS, which is still used by pages, the resulting conflict could be handled with the behaviour “Overwrite“ which would remove the template and leave the pages in an inconsistent state. This has been fixed now, such conflicts can now only be handled with behaviour “Ignore” (leaving the template untouched). When translating a page to the same language that already exists in the wastebin and as not deleted page, it was possible that the translation would create a duplicate of that page. This has been fixed now. The menu items and related links in the assistant frame for tagtypes were inconsistent for users with view but without edit permission. The entries have been changed to be consistent now. It is now possible to use a custom location for the configuration file of the Task Management App (gentics-activiti.properties). This is useful when the application server on which the Task Management App is deployed does not have access to the The documentation of imps has been improved in the Gentics CMS Guides Some inefficient SQL statements for updating data from the tagfill dialog have been improved. Some german umlauts were wrongly encoded. This bug only affected the cms webinterface. This has been fixed. The internal pools for prepared SQL statements used large amounts of Java Heap Space, which could cause memory problems (including OutOfMemory exceptions). Therefore pooling of SQL Statements has been disabled. Flash movies stored in the CMS could not be viewed in pages in preview-mode or edit-mode because the cms delivered them as attachment to the browser. (HTTP-header “Content-Disposition: attachment; filename=example.swf“) This has been fixed, the CMS will now set the proper HTTP-headers for flash videos. Additionally to get flash videos working in the CMS it is necessary to set the proper “type“ and “data” attributes on the flash OBJECT-html-tag, e.g.: Updated documentation to avoid a common mistake in velocity implementions from tagtypes that are editable with the aloha editor. When a user tried to create a language variant of a page, where this language variant was put into the wastebin before, and the user had no permission to delete pages in the folder, an error occurred. This has been fixed now: The page in the wastebin will be deleted regardless of the user‘s permission and replaced by the node language variant. Files that were imported from a thirdparty media asset system using the When publishing into a content repository with instant publishing, access to the content repository was locked longer and more often than necessary. This could cause congestion of instant publishing requests. This has been fixed now. Fixed issue where corrupted node-tags (node-notation without tagname and closing bracket: “ If a tag contained javascript the code wasn‘t executed again after opening and closing the tagfill. This bug was introduced with bugfix SUP-3724 in version 5.23.28 and has been fixed. When rendering a tag of another page with the render directive, tags contained in the rendered tag were resolved in the scope of the original page. This has been fixed now. When a node publishes into a multichannelling aware contentrepository, all channels of the node will automatically also publish into that contentrepository. This auto-assignment was not shown in the list of nodes or considered when checking the data of the contentrepository for channels that were created after the node was assigned to the contentrepository. In such cases, the result of the “Check data“ operation for the contentrepository would incorrectly state, that the channel was not assigned to the contentrepository and its data would be removed in the next publish run (which was not the case). This has been fixed now. The “Check data” operation will correctly consider the auto-assignment of channels to multichannelling aware contentrepositories exactly like the publish process does. When objects were exported where the name contained some characters which are not allowed in attribute values of XML nodes, the resulting XML files was invalid. This caused errors while importing. Generation of the XML files has been fixed now, so that the invalid characters will be removed from the names. Additionally, the handling of invalid XML files while importing has been improved to provide explicit error messages hinting at the root cause. Objects containing nested object tags were exported and imported in way which could subsequently cause errors when loading those objects via the REST API. This has been fixed now. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated to prevent errors when saving a page. In Detail: The variable “$parts.fileurl.target.id” was used without checking if it was empty. This caused an erroneous rendering when the tag linked to a file that has been deleted preventing users to save a page after editing. The permission checks when localizing objects over the REST API were too restrictive for users with permissions restricted to channels. This has been fixed now. Copying a localized copy of a file always produced an error message. This has been fixed now. When a localized copy of a file is copied, the copy will be created in the same channel now. When publishing files into a ContentRepository, errors like When an object with localized copies in channels was moved (in its master node) and the node published into a Content Repository with Instant Publishing enabled, all localized copies were also instantly written into the Content Repository. This could cause the move process to take longer than expected and was inconsistent behaviour (since Instant Publishing normally does not affect inherited or localized copies in channels, when the master object was changed). This has been fixed now, moving objects will trigger Instant Publishing only for the master object itself. Applying object properties of folders to subfolders did not work for channel local or localized folders and has been fixed now. When a tag in a page is filled with the tagfill dialog, and a part of type The Part Types documentation has been updated. If the startpage of a folder was moved to the wastebin (deleted) the flag symbol indicating the startpage was still visible in the page list for other language variants of the same page. This could lead to the assumption that the folder has a startpage set when the startpage was deleted instead. This has been fixed. After modifying a tag in the tagfill when editing a page the tag in the page was not updated correctly if the root element of the tag changed. For example, if the root element from the tag changes from a When publishing multiple nodes (with their channels) into the same Multichannelling aware ContentRepository, the ContentRepository Maintenance action Fixed taking offline a page in the old UI not being completed via the Rest API. The Activiti trigger “onPageTakeOffline” didn‘t work because of this. When applying this update, the packaged Tomcat will be updated to version 7.0.73 which contains important security and bug fixes. You can delete old Tomcat directories after updating. Fixed an SGB error when viewing a page in live preview mode in the new UI. Optional Manual Change The maximum number of clients used by the Apache Web Server for the CMS backend must not exceed 200, since this is the default value of maximum connections Tomcat will accept. The backup guide has been updated. Link anchors were removed from external links when saving a page if the Aloha Link Tagtype is missing the “anchor“ part or if the link plugin setting “anchorLinks” is set to false. This bug has been introduced with Gentics CMS 5.22.0. This has been fixed and the documentation for the Aloha Link Tagtype implementation has been updated to address link anchors. The script When the feature Two issues with the feature Showing the tag status failed with an SGB for templates that contain tags with special characters (like Optional Manual Change When using Internet Explorer in the Task Management UI, a small ‘x‘ button was shown in the search field, which cleared the search field, but had no effect on the search itself. This ‘x‘ button has now been removed. When opening a page for editing the event aloha-ready was never fired if the page contained no editable tags. This event should be triggered when the Aloha Editor is fully initialized. This has been fixed. When translating a local page inside a channel without specifying the channel, the check whether the translation already exists didn‘t work and another language variant of the same page with the same language was created. This has been fixed. When editing a page with Aloha Editor and an editable is activated, additional paragraphs are added in places where they are necessary in order to place the cursor in front of or after blocks. Those editables were only added to the activated editable and removed from any inactive editable, even if the active editable was nested in a block in another editable. This behaviour has been changed now, so that the paragraphs will be added to all ancestor editables of the active editable. Optional Manual Change In the Task Management the list of Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. When a page was edited outside the backend UI (e.g. via frontend editing or using the new UI) and a new file was uploaded from within the tagfill dialog, an SGB could occur. This has been fixed now. When moving a localized folder in a multichannelling environment, the localized copies did not get their parent‘s folder_id updated in the content repository. This has been fixed now. The maintenance action “Check data“ for multichannelling contentrepositories did not identify objects in channels that should have been overwritten by localized copies. Also, the check only would set the data status to “error” if invalid objects were found in the master node, but not, if invalid objects only existed in channels. Both issues have been fixed now. When using the extended search for pages in the root folder of a channel, it was not possible to restrict to templates, this has been fixed now. Localization of templates failed with an error. This has been fixed now. When evaluation of tagmap entries failed with unexpected errors (like NullPointerException) while publishing an object into a content repository, the logged error suppressed the expression causing the error. This has been fixed now. The statement used to get the templates using a specific page (in a pagetag) was inefficient and could cause timeouts in the page list. This has been fixed now. Selecting some text in the tagfill with the chrome browser was not working as expected after opening and closing the RepositoryBrowser without selecting any objects. This has been fixed. Some minor issues with the detection of GCMS version numbers from local updatefiles have been fixed. The regexes contained in the package, which can be used for text parts of constructs did not have proper english translations, which have been added now. When a localized or local page was edited in a channel, the setting for whether to use Aloha Editor was always taken from the master node, not from the channel. This has been fixed now. When a folder was moved into another folder with more restrictive inheritance settings (in a multichannelling environment), and the moved folder When a new tag was created in a page as copy of another tag with the Gentics Content.Node JavaScript API, the internal cache of the page was cleared which could lead to inconsistent behaviour. This has been fixed now. When the tagtype of an object property definition was changed, already existing object tags were not migrated, unless the change was done with the feature “tagtype migration”. This has been changed now. Existing object tags are migrated, when the object properties of an object are shown in the object properties dialog, or the object is loaded for editing. The script When a tagtype contained multiple parts of type The default upload folders for images and files could not be unset, once they were set. This has been fixed now. The guides on defining velocity macros in a library page were updated. They now recommend using tagtype “html (long)” to contain the velocity-code in the macro library page. When the feature When the type of a part in a construct was changed from When a page rendered the tag of another page, which rendered a velocity overview containing the original page, and a tag of the original page was rendered that resolved When editing a page with aloha editor, and a tag in an editable was refreshed (e.g. because the tag had been modified using the tagfill dialog), and the tag contained a nested tag in an editable, sometimes the order of initialization of the nested blocks and editables was incorrect and could cause side-effects. One of this side-effects was the automatic modification of editables through the browser when using internet explorer by inserting a br-tag. The initialization order of nested tags has been fixed now. Purging the wastebin from many deleted folders consumed a big amount of memory, which could cause OutOfMemory errors. This has been fixed now. If there was a publishrun between two imports of the same contentrepository, the second import would show a conflict for this contentrepository. This has been fixed. When a master object was deleted and localized at the same time (by different users), this could cause a data inconsistency. This has been fixed now. Setting the publish directory for a folder and all its subfolders may take a long time. This action has been modified to be continued in the background if it takes longer than 5 seconds. Before this fix, the long running request could cause a timeout, which was shown as error in the properties dialog of the folder. When copying a node together with its templates and some of the templates were assigned to folders in other nodes, the copies of those templates were also assigned to the folders of the other nodes. This has been fixed now. The copied templates will only be assigned to folders of the node copy. In multichannelling environments, the dependencies of images were sometimes not stored correctly, which could cause the automatic dirting mechanism to fail dirting images. This has been fixed now. This change does not automatically fix probably missing dependencies, in order to recalculate the dependencies, it is necessary to republish all files from the maintenance dialog. When images are uploaded where the DPI cannot be determined, the DPI was set to 72 per default. This has been changed now, so that the DPI is internally set to 0. The image list will now show ‘N/A‘ for the DPI value in such cases. Images that are already uploaded will not be affected by this change, unless they are uploaded again. The import has been fixed to not fail when an export bundle of a newer version of the Gentics CMS is imported, that contains new references that are marked as optional. The usage overview would always list all language variants of a page even though not all language variants used the object. The presentation has been fixed, so that each page using the object has its own entry in the list, but no symbols in the language column. When editables were modified during the page save process, a dialog could pop up that warns about unsaved changes. In order to prevent this dialog from appearing once the page was saved or published by the user, an additional check has been added. When a link was removed in a page, the corresponding link tag was not deleted when the page was saved. This has been fixed. Recursively changing the publish directory of a localized folder with the “include subfolders” option did not change the publish directory of its subfolders if they are also localized. This has been fixed. A possible NullPointerException during the publish run has been fixed. Entering URLs in the filter field of the page and template listings could render the filter unusable, and the only way to reset it, was to reset the session. This has been fixed. When applying this update, the packaged Tomcat will be updated to version 7.0.70 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. The documentation of the Aloha Editor configuration has been extended to cover extension of the toolbar settings. A NullPointerException occured in the When an editable part of a construct was deleted, this could cause subsequent errors in the publish process when using the feature publish_cache due to incorrectly cleared caches. This has been fixed now. When using the Feature A tagpart of type “URL (page)“ was only treated as being “internal“, when the radio button for “internal“ was selected AND an actual internal page was selected. This caused new tags being marked as “external“, even if the default value was “internal“, but no default page selected. This has been fixed now, the property “internal” will now exactly reflect the setting of the radio buttons, regardless of whether an actual page is selected or not. A wrong permission check had the effect that the current folder was sometimes selected instead of the standard upload folder when uploading a file or an image in the tagfill. This happened if the user had no permissions for assigning user permission. This has been fixed. Now the current folder is only selected if the user has no permissions to view the standard upload folder. The list of exports was created using inefficient SQL statements. This could cause timeout problems depending on the number of exports on the system and the user‘s paging setting. This update will create an index to speed up calculation of the number of warnings per export. Note that the change in the database structure might take longer than normal updates. When a page is edited using Aloha Editor and the Tagfill Dialog is opened for a tag or the repository browser is opened, scrolling of the page is prevented. Fixed the top menu not changing, after viewing/editing a content page and changing to another CMS page with the assistant. When using the GCN JS API to create tags in pages as copy of other tags, the callback passed to the function When a new editable part is added to the construct used in object properties the existing object tags of objects were not properly updated when the object properties dialog was opened. This has been fixed now. When the feature When a page is opened in edit mode of Aloha Editor and not saved within 10 minutes, the user‘s lock of the page was automatically lifted. This allowed other users to also edit the page, not aware that their changes could be overwritten by the first user. This has been fixed so that the lock on the page is updated on a regular basis as long as the first user keeps the page open in edit mode of Aloha Editor. In some cases, an additional tag was automatically added to rendered page sources, containing a Gentics Copyright notice. This has been removed now. When using multithreaded publishing and a publish process failed, this could cause additional exceptions “Cannot add job to Multiconnection transaction: Worker thread is not running” to be logged. Handling of aborting publish processes with multithreaded publishing has been improved, so that exceptions will only be logged if they are a possible cause but not the consequence of the aborting process. The documentation of the Pageurl/Fileurl parttype now includes the information that the url property is only set for internal links. The scheduler will now show more detailed information (the complete stacktrace with causing exceptions), when the publish run fails with an exception. When a folder is deleted (put into the wastebin), a check was done for objects having localized copies in the structure, which would also be deleted. This check has been extended to also check for local objects (objects that were created in subchannels of the deleted folder‘s channel). When objects in a multichannelling environment were published into a contentrepository with the permission information added, the permissions of localized folders were not correctly inherited from their master folder. This has been fixed now. When the master page of a localized copy was taken offline, editors were notified that pages in the channel linking to the localized copy contained an invalid link now, although the link was still valid (linking the localized copy). This has been fixed now. When a new inline editable part was added to a construct and pages containing tags of that construct were edited using Aloha Editor, the new parts could not be filled unless the page was saved once. This has been fixed now. When saving nodes using the REST API, setting the publish directory to empty did not work. Also when setting the publish directory to “/”, this was not corrected to be saved as empty. Both issues have been fixed. When a specific magiclinkconstruct was configured, the links were still rendered as blocks (with edit icon) in edit mode. This has been fixed now. The synchronization of pages with changes made to template tags was inconsistent and has been modified: This fix contains a change in the database structure, which could cause the update to take longer than usual. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which has been fixed now. When editing the node properties and the checkbox “Separate directories“ is not checked, data entered in the field “Page directory“ should be copied into the (disabled) field “Binary directory”, which did not work. This has been fixed now. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. This has been fixed now. Objects (files, images, pages or folders) that were restored from the wastebin did not automatically republish other objects that directly referenced the restored object. This has been fixed now. The assistant frame would not show the correct number of images in a folder, when there was an active filter for the images. This has been fixed. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated because it did not work correctly for links to images. In Detail: the implementation used a fixed type “10008“ for files and images, but images have the type “10011“. The corrected implementation reads the url target type correctly with “${parts.fileurl.target.ttype}“. Please update your implementation of the tagtype “gxtalohapagelink” accordingly to fix this problem. Optional Manual Change Various fixes have been made to the activiti integration: Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. Pagetags were still rendered, even if the targeted page was put into the wastebin. This has been fixed now. When the publish directory of a folder or the hostname of a node was changed, republishing of pages did not always work correctly, when the node published only into the file system. This has been fixed now. Fixed the quickjump also opening deleted pages when pressing enter instead of selecting an autocomplete result. Deleted pages will not be opened anymore. Also disabled the cache for the autocompletion as it could show old search results. Objects that were put into the wastebin and restored from the wastebin between two publish runs where sometimes incorrectly removed from the content repository during the next publish run. This has been fixed now. Rendered plinks always contained the parameter Optional Manual Change Several minor issues in the Activiti UI have been fixed: Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. Files and folders were not correctly published after restoring them from the wastebin. This has been fixed. The SQL Statements used to get the migration status for tagtype migrations was inefficient and could cause long running REST Requests. This has been fixed. Additionally, it is now possible to configure the polling interval for getting the migration status (default is still 1 second). See the guides for details. If the previous request to get the migration status did not return before the next request is due, the next request will be omitted now. An internal pool for prepared database statements was not properly sized and could consume a large amount of memory during a long running publish process. This could lead to memory exhaustion and failing publish processes. The maximum number of pooled connections has been reduced to 10000 by default, and can now be configured as described in the guides. Due to an incorrect consistency check, it was not possible to reinherit an object into a channel, when the parent folder was localized in that channel. This has been fixed now. When using the CASIntegrationFilter or HttpAuthFilter for SSO to the CMS backend, it could be possible that multiple identical users were created in the CMS backend database, if multiple concurrent requests with the same new user where done. This has been fixed now. Removing a construct from a node failed with the incorrect error message “Array”, if the construct would only be linked to nodes that user had no permission to unlink constructs from. This has been fixed now. Requests to the REST API created write locks to the user‘s systemsession entry, that would persist for the whole request duration. This caused parallel requests with the same session to be blocked until the first request was finished. This has been fixed now, the write lock to the systemsession will be lifted as soon as possible. Optional Manual Change The datasource “[Navigation] sortby“ in our Standard CMS installation can‘t be used for folder sorting in navigations unless you change the entry “Folder Sorting / Ordnersortierung“ from “obj.sortby“ to “object.sortorder”. This is fixed in the mysql dump for new installations. ContentRepository browser: An error was printed, when one of the CRs is using the same MySQL username and password like the CMS itself and persistent database connections are activated. This has been fixed. The elements selection of an overview could contain elements that were already put into the wastebin (deleted). This has been fixed. An error in the node library has been fixed, which could cause the CMS to hang when using instant publishing into multichannelling aware contentrepositories. If users where deactivated in the CMS, but not removed from their groups, those users were still returned by the Rest API: Fixed a bug in the auth/validate method where a session with ID -1 was considered as valid. Optional Manual Change Fixed a bug that breaks updating the CMS from the local filesystem. If you currently have a version installed, that has been released between 23.03.2016 and 24.05.2016, please read this page in order to update. Fixed a “Data inconsistent” (missing construct) error that could happen when loading, saving or publishing objects that have been created during the deletion of a tagtype. This affected content tags, template tags and object tags. The activiti integration has been improved: If a user had no paging acitivated he could still only see a maximum of 18 entries in the wastebin. This has been fixed. On some occasions page links where missing in inbox messages. This bug was introduced with GCN Version 5.22.15 and does not affect previous major releases. This has been fixed. The constraint expression in the Activiti configuration was not evaluated in the scope of the triggering object‘s channel. This has been fixed. Added a missing migration step in the package migration guide for “SUSE Enterprise Linux Server”. ImageMagick also has to be installed during the package migration. The publish log will now contain render times for the content and other attributes of pages separately. Enhanced fetching the latest available CMS update from the update server, so it doesn‘t block the CMS start page loading unnecessarily. That means if the update server is unreachable, the start page will still work. Also the current CMS version is now read from the Rest API, and not the database anymore. The error message for duplicate folder names (when creating or updating a folder) will now contain the full path of the conflicting folder. When the conflicting folder exists in another channel, the path will be shown in that channel. When a node was copied, where the source node contained templates that were linked to folders in the wastebin, the copies of the templates were also linked to the source folders in the wastebin. This has been fixed now, the copied templates will only be linked to folders in the target node. Fixed inconsistent user IDs in pages causing the publishing of the demo node to fail. This only affected fresh installations with 5.23.x. The performance for the display of objects in the wastebin has been improved. The object counts in the assistent frame will now be fetched asynchronously. This means that the numbers might appear (or be updated) with a slight delay. The cache for node objects can now be individually configured for object type. See the Guides for details. When selecting objects in the repository browser from a channel in order to create a link to the object, the channel ID will now be set into the link. This allows creation of channel specific links by using a special implementation of the Aloha Link Tagtype. The The DPI value shown for a file in the image list of a folder wasn‘t always correct and sometimes differed from the DPI value from the Rest API/database. The DPI value output is now the same. When using the old archive workflow to move files into another folder (instead of deleting them), the workflow failed, when the archive folder already contained a file with a name that was only different in case. This has been fixed now. When the channel directive Installation: The SQL dump contained trigger information that could cause SQL errors when the MySQL user didn‘t match ‘node_cms@localhost. The triggers have been removed out of the dump file. Installation: Enhanced the database import script to be more bulletproof. When copying a page to the root folder of a channel it was copied to the master of the root folder of the channel instead. This has been fixed. The publish statistics for rendering pages have been improved to distinguish between rendering content and rendering other attributes. When changing the definition of an object property, the internal cache of the definition was not invalidated correctly. This could cause the change not to take effect immediately. When, for example, the “inheritable” flag of folder object property definition was changed, and a new folder was created, it could happen that the old inheritance behavior was executed. This has been fixed now. Multichannelling: Renaming the publish directory of a localized folder back to the one of the master folder didn‘t work in some cases. This has been fixed. Fixed a problem where the permissions of templates linked to a folder in the wastebin only can‘t be determined anymore. This can cause imports to fail with an “Insufficient permissions” error. LDAP: Fixed an issue with Windows 2003 Active Directory referrals when someone tries to login by setting the LDAP_OPT_REFERRALS option to 0. If you encounter an error after updating, please set the setting $LDAP_LOGIN[‘referrals‘] = 1; in the configuration. Previously, templates that were only linked to one folder were wrongly deleted when the folder was moved to the wastebin. Now templates will only be removed when a folder is permanently deleted. A language in a node can‘t be deactivated when there is a page in the wastebin for this language. The error message has been improved to also display the count of pages in the wastebin for this language. Updated compatibility list and installation guide. It is mandatory to use the Oracle JDK with Gentics CMS. A note has been added to the faq for contentrepositories that explains the output of the data check. Changing permissions produced unnecessary database locks. This could cause errors while changing permissions due to lock wait timeouts. The SQL statements for changing permissions have been modified to avoid unnecessary locks and reduce the possibility for lock wait timeout errors. PLinks with attributes other than Aloha links were rendered with the “aloha-block” CSS class, which was removed when the page was fully loaded. This lead Aloha editor to believe pages containing links have been modified, even if nothing was changed. This has been fixed. Fixed the following bugs in the task management view: When applying this update, the packaged Tomcat will be updated to version 7.0.68 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.*) after updating. The REST API has been extended: If the feature Enhanced REST endpoint The endpoint The Activiti Integration Feature can now react to certain “CMS events” like saving, deleting or moving objects and publishing pages. Please refer to the Activiti configuration documentation for further details. A new Velocity directive The new Part Type “Node” allows selection of a Node. Added a new script called “setup-database.php”, that allows you to import the SQL structure needed for the CMS setup. Read the installation documentation for more details. With setting the new JVM parameter com.gentics.contentnode.exitonstartuperror to true the startup behaviour of the Tomcat can be changed: The package contained some default users, which are normally not used. They have been removed from the package now. When updating, those users will also be deactivated, if they never have been used. Installation Package: Correctly install and enable nodectl service. The presence of certain query parameters for the REST endpoint The REST endpoints Optional Manual Change When using Internet Explorer in the Task Management UI, a small ‘x‘ button was shown in the search field, which cleared the search field, but had no effect on the search itself. This ‘x‘ button has now been removed. When opening a page for editing the event aloha-ready was never fired if the page contained no editable tags. This event should be triggered when the Aloha Editor is fully initialized. This has been fixed. When translating a local page inside a channel without specifying the channel, the check whether the translation already exists didn‘t work and another language variant of the same page with the same language was created. This has been fixed. When editing a page with Aloha Editor and an editable is activated, additional paragraphs are added in places where they are necessary in order to place the cursor in front of or after blocks. Those editables were only added to the activated editable and removed from any inactive editable, even if the active editable was nested in a block in another editable. This behaviour has been changed now, so that the paragraphs will be added to all ancestor editables of the active editable. Optional Manual Change In the Task Management the list of Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. When a page was edited outside the backend UI (e.g. via frontend editing or using the new UI) and a new file was uploaded from within the tagfill dialog, an SGB could occur. This has been fixed now. When moving a localized folder in a multichannelling environment, the localized copies did not get their parent‘s folder_id updated in the content repository. This has been fixed now. The maintenance action “Check data“ for multichannelling contentrepositories did not identify objects in channels that should have been overwritten by localized copies. Also, the check only would set the data status to “error” if invalid objects were found in the master node, but not, if invalid objects only existed in channels. Both issues have been fixed now. When using the extended search for pages in the root folder of a channel, it was not possible to restrict to templates, this has been fixed now. Localization of templates failed with an error. This has been fixed now. When evaluation of tagmap entries failed with unexpected errors (like NullPointerException) while publishing an object into a content repository, the logged error suppressed the expression causing the error. This has been fixed now. The statement used to get the templates using a specific page (in a pagetag) was inefficient and could cause timeouts in the page list. This has been fixed now. Selecting some text in the tagfill with the chrome browser was not working as expected after opening and closing the RepositoryBrowser without selecting any objects. This has been fixed. Some minor issues with the detection of GCMS version numbers from local updatefiles have been fixed. The regexes contained in the package, which can be used for text parts of constructs did not have proper english translations, which have been added now. When a localized or local page was edited in a channel, the setting for whether to use Aloha Editor was always taken from the master node, not from the channel. This has been fixed now. When a folder was moved into another folder with more restrictive inheritance settings (in a multichannelling environment), and the moved folder When a new tag was created in a page as copy of another tag with the Gentics Content.Node JavaScript API, the internal cache of the page was cleared which could lead to inconsistent behaviour. This has been fixed now. When the tagtype of an object property definition was changed, already existing object tags were not migrated, unless the change was done with the feature “tagtype migration”. This has been changed now. Existing object tags are migrated, when the object properties of an object are shown in the object properties dialog, or the object is loaded for editing. The script When a tagtype contained multiple parts of type The default upload folders for images and files could not be unset, once they were set. This has been fixed now. The guides on defining velocity macros in a library page were updated. They now recommend using tagtype “html (long)” to contain the velocity-code in the macro library page. When the type of a part in a construct was changed from When a page rendered the tag of another page, which rendered a velocity overview containing the original page, and a tag of the original page was rendered that resolved When editing a page with aloha editor, and a tag in an editable was refreshed (e.g. because the tag had been modified using the tagfill dialog), and the tag contained a nested tag in an editable, sometimes the order of initialization of the nested blocks and editables was incorrect and could cause side-effects. One of this side-effects was the automatic modification of editables through the browser when using internet explorer by inserting a br-tag. The initialization order of nested tags has been fixed now. Purging the wastebin from many deleted folders consumed a big amount of memory, which could cause OutOfMemory errors. This has been fixed now. If there was a publishrun between two imports of the same contentrepository, the second import would show a conflict for this contentrepository. This has been fixed. When a master object was deleted and localized at the same time (by different users), this could cause a data inconsistency. This has been fixed now. Setting the publish directory for a folder and all its subfolders may take a long time. This action has been modified to be continued in the background if it takes longer than 5 seconds. Before this fix, the long running request could cause a timeout, which was shown as error in the properties dialog of the folder. When copying a node together with its templates and some of the templates were assigned to folders in other nodes, the copies of those templates were also assigned to the folders of the other nodes. This has been fixed now. The copied templates will only be assigned to folders of the node copy. In multichannelling environments, the dependencies of images were sometimes not stored correctly, which could cause the automatic dirting mechanism to fail dirting images. This has been fixed now. This change does not automatically fix probably missing dependencies, in order to recalculate the dependencies, it is necessary to republish all files from the maintenance dialog. When images are uploaded where the DPI cannot be determined, the DPI was set to 72 per default. This has been changed now, so that the DPI is internally set to 0. The image list will now show ‘N/A‘ for the DPI value in such cases. Images that are already uploaded will not be affected by this change, unless they are uploaded again. The import has been fixed to not fail when an export bundle of a newer version of the Gentics CMS is imported, that contains new references that are marked as optional. The usage overview would always list all language variants of a page even though not all language variants used the object. The presentation has been fixed, so that each page using the object has its own entry in the list, but no symbols in the language column. When editables were modified during the page save process, a dialog could pop up that warns about unsaved changes. In order to prevent this dialog from appearing once the page was saved or published by the user, an additional check has been added. When a link was removed in a page, the corresponding link tag was not deleted when the page was saved. This has been fixed. Recursively changing the publish directory of a localized folder with the “include subfolders” option did not change the publish directory of its subfolders if they are also localized. This has been fixed. Entering URLs in the filter field of the page and template listings could render the filter unusable, and the only way to reset it, was to reset the session. This has been fixed. A possible NullPointerException during the publish run has been fixed. When applying this update, the packaged Tomcat will be updated to version 7.0.70 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. The documentation of the Aloha Editor configuration has been extended to cover extension of the toolbar settings. A NullPointerException occured in the When an editable part of a construct was deleted, this could cause subsequent errors in the publish process when using the feature publish_cache due to incorrectly cleared caches. This has been fixed now. When using the Feature A tagpart of type “URL (page)“ was only treated as being “internal“, when the radio button for “internal“ was selected AND an actual internal page was selected. This caused new tags being marked as “external“, even if the default value was “internal“, but no default page selected. This has been fixed now, the property “internal” will now exactly reflect the setting of the radio buttons, regardless of whether an actual page is selected or not. A wrong permission check had the effect that the current folder was sometimes selected instead of the standard upload folder when uploading a file or an image in the tagfill. This happened if the user had no permissions for assigning user permission. This has been fixed. Now the current folder is only selected if the user has no permissions to view the standard upload folder. The list of exports was created using inefficient SQL statements. This could cause timeout problems depending on the number of exports on the system and the user‘s paging setting. This update will create an index to speed up calculation of the number of warnings per export. Note that the change in the database structure might take longer than normal updates. When a page is edited using Aloha Editor and the Tagfill Dialog is opened for a tag or the repository browser is opened, scrolling of the page is prevented. Fixed the top menu not changing, after viewing/editing a content page and changing to another CMS page with the assistant. When using the GCN JS API to create tags in pages as copy of other tags, the callback passed to the function When a new editable part is added to the construct used in object properties the existing object tags of objects were not properly updated when the object properties dialog was opened. This has been fixed now. When the feature When a page is opened in edit mode of Aloha Editor and not saved within 10 minutes, the user‘s lock of the page was automatically lifted. This allowed other users to also edit the page, not aware that their changes could be overwritten by the first user. This has been fixed so that the lock on the page is updated on a regular basis as long as the first user keeps the page open in edit mode of Aloha Editor. In some cases, an additional tag was automatically added to rendered page sources, containing a Gentics Copyright notice. This has been removed now. When using multithreaded publishing and a publish process failed, this could cause additional exceptions “Cannot add job to Multiconnection transaction: Worker thread is not running” to be logged. Handling of aborting publish processes with multithreaded publishing has been improved, so that exceptions will only be logged if they are a possible cause but not the consequence of the aborting process. The documentation of the Pageurl/Fileurl parttype now includes the information that the url property is only set for internal links. The scheduler will now show more detailed information (the complete stacktrace with causing exceptions), when the publish run fails with an exception. When a folder is deleted (put into the wastebin), a check was done for objects having localized copies in the structure, which would also be deleted. This check has been extended to also check for local objects (objects that were created in subchannels of the deleted folder‘s channel). When objects in a multichannelling environment were published into a contentrepository with the permission information added, the permissions of localized folders were not correctly inherited from their master folder. This has been fixed now. When the master page of a localized copy was taken offline, editors were notified that pages in the channel linking to the localized copy contained an invalid link now, although the link was still valid (linking the localized copy). This has been fixed now. When a new inline editable part was added to a construct and pages containing tags of that construct were edited using Aloha Editor, the new parts could not be filled unless the page was saved once. This has been fixed now. When saving nodes using the REST API, setting the publish directory to empty did not work. Also when setting the publish directory to “/”, this was not corrected to be saved as empty. Both issues have been fixed. When a specific magiclinkconstruct was configured, the links were still rendered as blocks (with edit icon) in edit mode. This has been fixed now. The synchronization of pages with changes made to template tags was inconsistent and has been modified: This fix contains a change in the database structure, which could cause the update to take longer than usual. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which has been fixed now. When editing the node properties and the checkbox “Separate directories“ is not checked, data entered in the field “Page directory“ should be copied into the (disabled) field “Binary directory”, which did not work. This has been fixed now. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. This has been fixed now. Objects (files, images, pages or folders) that were restored from the wastebin did not automatically republish other objects that directly referenced the restored object. This has been fixed now. The assistant frame would not show the correct number of images in a folder, when there was an active filter for the images. This has been fixed. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated because it did not work correctly for links to images. In Detail: the implementation used a fixed type “10008“ for files and images, but images have the type “10011“. The corrected implementation reads the url target type correctly with “${parts.fileurl.target.ttype}“. Please update your implementation of the tagtype “gxtalohapagelink” accordingly to fix this problem. Optional Manual Change Various fixes have been made to the activiti integration: Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. Pagetags were still rendered, even if the targeted page was put into the wastebin. This has been fixed now. When the publish directory of a folder or the hostname of a node was changed, republishing of pages did not always work correctly, when the node published only into the file system. This has been fixed now. Fixed the quickjump also opening deleted pages when pressing enter instead of selecting an autocomplete result. Deleted pages will not be opened anymore. Also disabled the cache for the autocompletion as it could show old search results. Objects that were put into the wastebin and restored from the wastebin between two publish runs where sometimes incorrectly removed from the content repository during the next publish run. This has been fixed now. Optional Manual Change Several minor issues in the Activiti UI have been fixed: Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes. Files and folders were not correctly published after restoring them from the wastebin. This has been fixed. The SQL Statements used to get the migration status for tagtype migrations was inefficient and could cause long running REST Requests. This has been fixed. Additionally, it is now possible to configure the polling interval for getting the migration status (default is still 1 second). See the guides for details. If the previous request to get the migration status did not return before the next request is due, the next request will be omitted now. An internal pool for prepared database statements was not properly sized and could consume a large amount of memory during a long running publish process. This could lead to memory exhaustion and failing publish processes. The maximum number of pooled connections has been reduced to 10000 by default, and can now be configured as described in the guides. Due to an incorrect consistency check, it was not possible to reinherit an object into a channel, when the parent folder was localized in that channel. This has been fixed now. When using the CASIntegrationFilter or HttpAuthFilter for SSO to the CMS backend, it could be possible that multiple identical users were created in the CMS backend database, if multiple concurrent requests with the same new user where done. This has been fixed now. Removing a construct from a node failed with the incorrect error message “Array”, if the construct would only be linked to nodes that user had no permission to unlink constructs from. This has been fixed now. Requests to the REST API created write locks to the user‘s systemsession entry, that would persist for the whole request duration. This caused parallel requests with the same session to be blocked until the first request was finished. This has been fixed now, the write lock to the systemsession will be lifted as soon as possible. Optional Manual Change The datasource “[Navigation] sortby“ in our Standard CMS installation can‘t be used for folder sorting in navigations unless you change the entry “Folder Sorting / Ordnersortierung“ from “obj.sortby“ to “object.sortorder”. This is fixed in the mysql dump for new installations. ContentRepository browser: An error was printed, when one of the CRs is using the same MySQL username and password like the CMS itself and persistent database connections are activated. This has been fixed. The elements selection of an overview could contain elements that were already put into the wastebin (deleted). This has been fixed. An error in the node library has been fixed, which could cause the CMS to hang when using instant publishing into multichannelling aware contentrepositories. If users where deactivated in the CMS, but not removed from their groups, those users were still returned by the The activiti integration has been improved: Rest API: Fixed a bug in the auth/validate method where a session with ID -1 was considered as valid. Optional Manual Change Fixed a bug that breaks updating the CMS from the local filesystem. If you currently have a version installed, that has been released between 23.03.2016 and 24.05.2016, please read this page in order to update. Fixed a “Data inconsistent” (missing construct) error that could happen when loading, saving or publishing objects that have been created during the deletion of a tagtype. This affected content tags, template tags and object tags. If a user had no paging acitivated he could still only see a maximum of 18 entries in the wastebin. This has been fixed. On some occasions page links where missing in inbox messages. This bug was introduced with GCN Version 5.22.15 and does not affect previous major releases. This has been fixed. Added a missing migration step in the package migration guide for “SUSE Enterprise Linux Server”. ImageMagick also has to be installed during the package migration. The publish log will now contain render times for the content and other attributes of pages separately. Enhanced fetching the latest available CMS update from the update server, so it doesn‘t block the CMS start page loading unnecessarily. That means if the update server is unreachable, the start page will still work. Also the current CMS version is now read from the Rest API, and not the database anymore. The error message for duplicate folder names (when creating or updating a folder) will now contain the full path of the conflicting folder. When the conflicting folder exists in another channel, the path will be shown in that channel. When a node was copied, where the source node contained templates that were linked to folders in the wastebin, the copies of the templates were also linked to the source folders in the wastebin. This has been fixed now, the copied templates will only be linked to folders in the target node. Installation: The SQL dump contained trigger information that could cause SQL errors when the MySQL user didn‘t match ‘node_cms@localhost. The triggers have been removed out of the dump file. The performance for the display of objects in the wastebin has been improved. The object counts in the assistent frame will now be fetched asynchronously. This means that the numbers might appear (or be updated) with a slight delay. The cache for node objects can now be individually configured for object type. See the Guides for details. The The DPI value shown for a file in the image list of a folder wasn‘t always correct and sometimes differed from the DPI value from the Rest API/database. The DPI value output is now the same. When using the old archive workflow to move files into another folder (instead of deleting them), the workflow failed, when the archive folder already contained a file with a name that was only different in case. This has been fixed now. When copying a page to the root folder of a channel it was copied to the master of the root folder of the channel instead. This has been fixed. The publish statistics for rendering pages have been improved to distinguish between rendering content and rendering other attributes. When changing the definition of an object property, the internal cache of the definition was not invalidated correctly. This could cause the change not to take effect immediately. When, for example, the “inheritable” flag of folder object property definition was changed, and a new folder was created, it could happen that the old inheritance behavior was executed. This has been fixed now. Multichannelling: Renaming the publish directory of a localized folder back to the one of the master folder didn‘t work in some cases. This has been fixed. Fixed a problem where the permissions of templates linked to a folder in the wastebin only can‘t be determined anymore. This can cause imports to fail with an “Insufficient permissions” error. LDAP: Fixed an issue with Windows 2003 Active Directory referrals when someone tries to login by setting the LDAP_OPT_REFERRALS option to 0. If you encounter an error after updating, please set the setting $LDAP_LOGIN[‘referrals‘] = 1; in the configuration. Previously, templates that were only linked to one folder were wrongly deleted when the folder was moved to the wastebin. Now templates will only be removed when a folder is permanently deleted. A language in a node can‘t be deactivated when there is a page in the wastebin for this language. The error message has been improved to also display the count of pages in the wastebin for this language. Updated compatibility list and installation guide. It is mandatory to use the Oracle JDK with Gentics CMS. A note has been added to the faq for contentrepositories that explains the output of the data check. Changing permissions produced unnecessary database locks. This could cause errors while changing permissions due to lock wait timeouts. The SQL statements for changing permissions have been modified to avoid unnecessary locks and reduce the possibility for lock wait timeout errors. Installation Package: Correctly install and enable nodectl service. PLinks with attributes other than Aloha links were rendered with the “aloha-block” CSS class, which was removed when the page was fully loaded. This lead Aloha editor to believe pages containing links have been modified, even if nothing was changed. This has been fixed. Fixed the following bugs in the task management view: The documentation of the Import in the Guides has been extended to explain, what will happend during an import. Visiting the startpage caused errors to be logged when trying to get the estimated remaining time of the publishrun. This has been fixed. The paging controls were missing in the usage overviews of files and images. Also the overview of folders using an object did not list those folders, but the subfolders of the objects parent folder. These issues have been fixed. The version diff did not ignore differences in zero-width whitespace characters. This caused diffs shown in places with no visible difference. This has been fixed now, zero-width whitespace characters will now be ignored. Tagtype parts of the type “Text (custom form)” could not be migrated with the migration feature. This has been fixed. Updater: Fixed that the update file is not deleted and downloaded again when it is corrupted. When a master page was deleted from the publish cache, publications of its localized copies failed because dependencies could not be handled properly. This has been fixed. The publish statistics for publishing files into ContentRepositories has been fixed to better distinguish between several steps. The SQL dump file for new CMS installations has been updated in order to fix some issues. The following changes have been done: Fixed a nullpointer-exception that could happen when starting the CMS the first time and the UUID of the demo node is null. The logs view can now be filtered by maintenance actions. When the internal scheduler fails to start upon start of the Tomcat (e.g. due to failures while connecting to the DB), the Tomcat will fail to start with an error message logged. Before this fix, Tomcat would start anyways and some background operations like deleting or localizing objects would only be queued, but never executed. If a User had no viewing permission on Content.Admin then the user could not insert new tags with the aloha editor. This has been fixed. When publishing into a ContentRepository with instant publishing, objects that were disinherited in some channels were incorrectly removed from the ContentRepository completely (for all channels). This has been fixed now. Since changing the inheritance of objects possibly affects many objects, instant publishing has been turned off for changing the inheritance. After changing the inheritance of objects, a publish process is required to add or remove objects to/from the ContentRepository. Links in Messages were HTML-Entity encoded by mistake. This affected the automatic messages that are generated when pages where added to the publish queue. When copying links in the Aloha Editor the second link would not be converted to a new link tag, causing multiple instances of links with the same (tag) ID on the page. This has been fixed. Deleted images were still visible in the minibrowser. This has been fixed. Loading a Template using the REST API produced an error when a request accepted the mimetype “application/xml” for the response. This has been fixed. When restoring a page from the wastebin, the page was not visible in it‘s folder right away because the cache of the parent folder was not refreshed. This has been fixed. Creating a copy of an image immediately after cropping would fail without an error message. This has been fixed. When objects were moved between folders, pages containing automatic overviews were not always dirted. This has been fixed now. Aloha Editor gcn-plugin: When an editable was configured to show no insert buttons (empty array), the arena that contains the buttons normally was still shown. This has been fixed. Aloha Editor gcn-plugin: Since the bugfix for SUP-2365, the editable configuration for the insert-tag buttons didn‘t work correctly anymore. This has been fixed. Image Manipulation: replaced a confusing warning when saving auto-resized images with a clearer info message. Optional Manual Change The implementation of the gtxalohapagelink tag has been updated in the guides to fix the detection of an empty anchor tagpart. When using the velocity code from the guide (or a variation thereof) please make sure to use Fixed a GenticsImageStore bug which caused resizing operations to fail due to a broken dependency of http-client. This also affected the image manipulation tool. The bug affected all GCN versions that were released after 17.02.2016. Aloha Editor gcn-plugin: Inserting new tags didn‘t work anymore because the construct property mayBeSubTag got renamed in the previous bugfix for SUP-2429 but wasn‘t renamed in the gcn-plugin. This has been fixed. The sidebar pannels of the GCN FileLink plugin now look more like their counterparts in the link plugin. When Drag & Drop was disabled and several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in nested editables, the edit and delete icons could be inactive. This has been fixed. Resized images in the GenticsImageStore were not properly updated when the binary contents of an image changed. This has been fixed. The Java REST API client didn‘t correctly define the Maven dependency for jackson-jaxrs. That‘s why this dependency had to be defined manually before. This has been fixed now. Fixed a null pointer exception that sometimes occured when deleting a whole node with templates. Java rest client: Fixed the jackson object mapper throwing a parse error when calling the rest method “construct.list“. In order to fix this the method “Construct.getMayBeSubTag“ has been renamed to “Construct.getMayBeSubtag”. Rest API: Passing global object IDs in the new UUID format didn‘t work. This has been fixed. Installation guides: Changed the text about trigger deletion to be more clear on when it needs to be done and added the — max_allowed_packet option to all mysqldump calls. When editing a page, it was possible to insert new tags inside links. This corrupted the link when saving the page. Inserting tags inside links is not possible anymore now. When the wastebin feature is activated, the startpage flag icon wasn‘t shown correctly when the pages folder was localized and then moved to the wastebin (deleted). This has been fixed. An error was logged when rendering a velocity part that resolved a “Select (single)”-part where nothing was selected. This has been fixed. Fixed the Javascript error “Uncaught TypeError: Cannot read property ‘themes‘ of undefined” that occured when loading or saving a page. Node id and folder id were missing in the php session when editing object properties. This has been fixed. When a new tag was inserted into a page using Aloha Editor and then the user navigated away from the page (without saving first), the page was not saved and the user did not get the notification about unsaved changes in the page. This has been fixed now. The user will get a notification about unsaved changes in such cases. If there are two consecutive tables in an editable, the draghandle of the second table could overlap cells from the first table. This has been fixed. When using the GCN filelink plugin the filelink tag was not removed, when the link was changed to an external URL. This has been fixed. The background job for cleaning old systemsessions could cause deadlocks in the database, which caused errors while users tried to log in into the backend. Those deadlocks have been fixed now. Newlines in Instant Messages where wrongly replaced by HTML-Entity encoded When using the GCN JS API to create a tag in a page, the information about the pages tags was not always properly updated (e.g. when copying a tag containing nested tags). This has been fixed. In the page list view the sequence of the columns was mixed up after a new column was added in bugfix SUP-1815. This has been fixed. When using the features Fixed a bug with siteminder datasources, where the reading of the datasource values didn‘t work, when the publish_cache feature is activated. The version difference view didn‘t correctly work for HTML pages. This has been fixed. After editing the page properties and saving the changes, the page was not unlocked. This has been fixed. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the edit and delete icons could be inactive. This has been fixed. When publishing images/files into a contentrepository and having the attribute binarycontent set to be a filesystem attribute, in some rare cases it could happen, that the attribute contained old data. This has been fixed now. Certain corrupt images files (e.g. empty files) could cause the publish process to fail, when the image needed to be resized by the GenticsImageStore. This has been fixed. When images used in the GenticsImageStore were put into the wastebin, this sometimes could let the publish process fail with “Couldn‘t find image { [ID] } to link”. This has been fixed now. Optional Manual Change For copying Pages with the REST API you can now set multiple SourcePage Ids in the PageCopyRequest When the publish process was interrupted while synchronizing deleted objects with content repositories, the publish process did not stop, but just skipped over to the next step (publishing pages). This has been fixed now, when the publish process is interrupted in that state, it will stop as soon as possible. When inserting a file link, with the FileLink plugin the freshly inserted link was not visible for editing. This has been fixed. When pages were published using the time management (“publish at”), and the publish process needed to create a version, this new version did not have an editor set. This has been changed now, so that the user who last edited the page will be set as editor of the page version. Copying nodes where objects have been moved to the wastebin (deleted) didn‘t work. This has been fixed. The systemsession table was not cleaned regularly from old session data, which could cause the table to grow too big. This has been fixed now. Fixed an SGB error that happened when saving object properties or definitions on systems that got updated from an older GCN version to 5.22.0 or higher. Optional Manual Change The FileLink plugin did not treat images as files. If an image was selected, a normal link to that image was created. This has been fixed now, so that also images will be treated as files. Removed a wrong changelog note from version 5.20.21 In inbox messages the links to pages in multichannel nodes where not resolved correctly. The link would always point to the page in the channel the user last worked in. This has been fixed: links to pages in messages will now always open the page in the channel, where the page can be edited without localizing it. Fixed the tree frame becoming smaller each time it is loaded in Internet Explorer. Also fixed some Javascript errors in the tree. When a page, which is published and is the target of a link in another page is put into the wastebin, the editor of the other page received an inbox message about the invalid link with the reason, that the link target was taken offline. While this is technically correct (the page is first taken offline and then put into the wastebin), it might be misleading. Therefore the inbox message for that case has been changed to be like when the page is deleted and not put into the wastebin. When clicking the “Create copy“ button when editing an image, the button label changed to “Duplicate”. This has been fixed, so that it stays the same. The preview tooltip in the repository browser has been moved, so that it will no longer overlap with nearby filenames. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the Aloha editor would only convert the first one into an aloha-block. This behavior has been changed, so that every occurrence of a tag will become a block and get edit and delete buttons. When linking/unlinking a single template from folders, where the user does not have permission to link the template to a folder where the template is already link, the user would always get an error message stating the missing permission. However, linking/unlinking the template to/from folders where the user has the permission still worked as expected. This issue has been fixed now, so that the unnecessary message will not be shown any more. When the feature Optional Manual Change The GCN link plugin for the Aloha editor now manages anchors in URLs. If this feature should be used, the tagpart Please see the documentation of the Aloha page link tag for more information. Optional Manual Change The rarely used “inpage“ functionality to pass object properties from folders or templates to pages via the context menu has been removed. If you have used the context menu option “in page changeable” on any folders or templates object properties, please create a new object property definition for the page with the same name like for the folder or template object property definition. It is now possible to link the CMS with an external BPM Engine Server, based on the Activiti Business Process Management Platform. The REST API has been extended: Enhanced REST endpoints Enhanced Java REST Client It is now possible to configure the way how URLs to pages, files or folders will be rendered on a per node basis. See the Guides for more information. The context menu in the list of files and images now contains an entry “Properties” which will show the Properties dialog of the selected file or image. The node settings dialog has been cleaned up and now contains a tab for general settings and one for publication settings. It is now possible to configure what kind of objects (pages, files, folders) will be published into the file system or content repository on a per node basis. In implementations of CnMapPublishHandler, it is now possible to access the datasource, using the PortalConnectorFactory. The ID of the datasource will be passed to the CnMapPublishHandler instance in the init() call as parameter with the key CnMapPublishHandler.DS_ID. The file and image lists now show if the object is currently online or not. Furthermore the online status information for pages has been refined to better reflect their online status (e.g. offline files which are locked or worked on now have unique icons). Under specific circumstances, it was possible the normal inbox messages where shown as instant messages. This has been fixed now. The import has been fixed to not fail when an export bundle of a newer version of the Gentics CMS is imported, that contains new references that are marked as optional. The usage overview would always list all language variants of a page even though not all language variants used the object. The presentation has been fixed, so that each page using the object has its own entry in the list, but no symbols in the language column. When editables were modified during the page save process, a dialog could pop up that warns about unsaved changes. In order to prevent this dialog from appearing once the page was saved or published by the user, an additional check has been added. When a link was removed in a page, the corresponding link tag was not deleted when the page was saved. This has been fixed. Recursively changing the publish directory of a localized folder with the “include subfolders” option did not change the publish directory of its subfolders if they are also localized. This has been fixed. A possible NullPointerException during the publish run has been fixed. Entering URLs in the filter field of the page and template listings could render the filter unusable, and the only way to reset it, was to reset the session. This has been fixed. When applying this update, the packaged Tomcat will be updated to version 7.0.70 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. The documentation of the Aloha Editor configuration has been extended to cover extension of the toolbar settings. A NullPointerException occured in the When an editable part of a construct was deleted, this could cause subsequent errors in the publish process when using the feature publish_cache due to incorrectly cleared caches. This has been fixed now. When using the Feature A tagpart of type “URL (page)“ was only treated as being “internal“, when the radio button for “internal“ was selected AND an actual internal page was selected. This caused new tags being marked as “external“, even if the default value was “internal“, but no default page selected. This has been fixed now, the property “internal” will now exactly reflect the setting of the radio buttons, regardless of whether an actual page is selected or not. A wrong permission check had the effect that the current folder was sometimes selected instead of the standard upload folder when uploading a file or an image in the tagfill. This happened if the user had no permissions for assigning user permission. This has been fixed. Now the current folder is only selected if the user has no permissions to view the standard upload folder. The list of exports was created using inefficient SQL statements. This could cause timeout problems depending on the number of exports on the system and the user‘s paging setting. This update will create an index to speed up calculation of the number of warnings per export. Note that the change in the database structure might take longer than normal updates. When a page is edited using Aloha Editor and the Tagfill Dialog is opened for a tag or the repository browser is opened, scrolling of the page is prevented. Fixed the top menu not changing, after viewing/editing a content page and changing to another CMS page with the assistant. When using the GCN JS API to create tags in pages as copy of other tags, the callback passed to the function When a new editable part is added to the construct used in object properties the existing object tags of objects were not properly updated when the object properties dialog was opened. This has been fixed now. When a page is opened in edit mode of Aloha Editor and not saved within 10 minutes, the user‘s lock of the page was automatically lifted. This allowed other users to also edit the page, not aware that their changes could be overwritten by the first user. This has been fixed so that the lock on the page is updated on a regular basis as long as the first user keeps the page open in edit mode of Aloha Editor. In some cases, an additional tag was automatically added to rendered page sources, containing a Gentics Copyright notice. This has been removed now. When using multithreaded publishing and a publish process failed, this could cause additional exceptions “Cannot add job to Multiconnection transaction: Worker thread is not running” to be logged. Handling of aborting publish processes with multithreaded publishing has been improved, so that exceptions will only be logged if they are a possible cause but not the consequence of the aborting process. The documentation of the Pageurl/Fileurl parttype now includes the information that the url property is only set for internal links. The scheduler will now show more detailed information (the complete stacktrace with causing exceptions), when the publish run fails with an exception. When a folder is deleted (put into the wastebin), a check was done for objects having localized copies in the structure, which would also be deleted. This check has been extended to also check for local objects (objects that were created in subchannels of the deleted folder‘s channel). When objects in a multichannelling environment were published into a contentrepository with the permission information added, the permissions of localized folders were not correctly inherited from their master folder. This has been fixed now. When the master page of a localized copy was taken offline, editors were notified that pages in the channel linking to the localized copy contained an invalid link now, although the link was still valid (linking the localized copy). This has been fixed now. When a new inline editable part was added to a construct and pages containing tags of that construct were edited using Aloha Editor, the new parts could not be filled unless the page was saved once. This has been fixed now. When saving nodes using the REST API, setting the publish directory to empty did not work. Also when setting the publish directory to “/”, this was not corrected to be saved as empty. Both issues have been fixed. When a specific magiclinkconstruct was configured, the links were still rendered as blocks (with edit icon) in edit mode. This has been fixed now. The synchronization of pages with changes made to template tags was inconsistent and has been modified: This fix contains a change in the database structure, which could cause the update to take longer than usual. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which has been fixed now. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. This has been fixed now. Objects (files, images, pages or folders) that were restored from the wastebin did not automatically republish other objects that directly referenced the restored object. This has been fixed now. The assistant frame would not show the correct number of images in a folder, when there was an active filter for the images. This has been fixed. Pagetags were still rendered, even if the targeted page was put into the wastebin. This has been fixed now. When the publish directory of a folder or the hostname of a node was changed, republishing of pages did not always work correctly, when the node published only into the file system. This has been fixed now. Fixed the quickjump also opening deleted pages when pressing enter instead of selecting an autocomplete result. Deleted pages will not be opened anymore. Also disabled the cache for the autocompletion as it could show old search results. Objects that were put into the wastebin and restored from the wastebin between two publish runs where sometimes incorrectly removed from the content repository during the next publish run. This has been fixed now. Files and folders were not correctly published after restoring them from the wastebin. This has been fixed. The SQL Statements used to get the migration status for tagtype migrations was inefficient and could cause long running REST Requests. This has been fixed. Additionally, it is now possible to configure the polling interval for getting the migration status (default is still 1 second). See the guides for details. If the previous request to get the migration status did not return before the next request is due, the next request will be omitted now. An internal pool for prepared database statements was not properly sized and could consume a large amount of memory during a long running publish process. This could lead to memory exhaustion and failing publish processes. The maximum number of pooled connections has been reduced to 10000 by default, and can now be configured as described in the guides. Due to an incorrect consistency check, it was not possible to reinherit an object into a channel, when the parent folder was localized in that channel. This has been fixed now. When using the CASIntegrationFilter or HttpAuthFilter for SSO to the CMS backend, it could be possible that multiple identical users were created in the CMS backend database, if multiple concurrent requests with the same new user where done. This has been fixed now. Removing a construct from a node failed with the incorrect error message “Array”, if the construct would only be linked to nodes that user had no permission to unlink constructs from. This has been fixed now. Requests to the REST API created write locks to the user‘s systemsession entry, that would persist for the whole request duration. This caused parallel requests with the same session to be blocked until the first request was finished. This has been fixed now, the write lock to the systemsession will be lifted as soon as possible. Optional Manual Change The datasource “[Navigation] sortby“ in our Standard CMS installation can‘t be used for folder sorting in navigations unless you change the entry “Folder Sorting / Ordnersortierung“ from “obj.sortby“ to “object.sortorder”. This is fixed in the mysql dump for new installations. ContentRepository browser: An error was printed, when one of the CRs is using the same MySQL username and password like the CMS itself and persistent database connections are activated. This has been fixed. The elements selection of an overview could contain elements that were already put into the wastebin (deleted). This has been fixed. An error in the node library has been fixed, which could cause the CMS to hang when using instant publishing into multichannelling aware contentrepositories. If users where deactivated in the CMS, but not removed from their groups, those users were still returned by the Rest API: Fixed a bug in the auth/validate method where a session with ID -1 was considered as valid. Optional Manual Change Fixed a bug that breaks updating the CMS from the local filesystem. If you currently have a version installed, that has been released between 23.03.2016 and 24.05.2016, please read this page in order to update. If a user had no paging acitivated he could still only see a maximum of 18 entries in the wastebin. This has been fixed. Added a missing migration step in the package migration guide for “SUSE Enterprise Linux Server”. ImageMagick also has to be installed during the package migration. The publish log will now contain render times for the content and other attributes of pages separately. Enhanced fetching the latest available CMS update from the update server, so it doesn‘t block the CMS start page loading unnecessarily. That means if the update server is unreachable, the start page will still work. Also the current CMS version is now read from the Rest API, and not the database anymore. The error message for duplicate folder names (when creating or updating a folder) will now contain the full path of the conflicting folder. When the conflicting folder exists in another channel, the path will be shown in that channel. When a node was copied, where the source node contained templates that were linked to folders in the wastebin, the copies of the templates were also linked to the source folders in the wastebin. This has been fixed now, the copied templates will only be linked to folders in the target node. Installation: The SQL dump contained trigger information that could cause SQL errors when the MySQL user didn‘t match ‘node_cms@localhost. The triggers have been removed out of the dump file. The performance for the display of objects in the wastebin has been improved. The object counts in the assistent frame will now be fetched asynchronously. This means that the numbers might appear (or be updated) with a slight delay. The cache for node objects can now be individually configured for object type. See the Guides for details. The The DPI value shown for a file in the image list of a folder wasn‘t always correct and sometimes differed from the DPI value from the Rest API/database. The DPI value output is now the same. When using the old archive workflow to move files into another folder (instead of deleting them), the workflow failed, when the archive folder already contained a file with a name that was only different in case. This has been fixed now. When copying a page to the root folder of a channel it was copied to the master of the root folder of the channel instead. This has been fixed. The publish statistics for rendering pages have been improved to distinguish between rendering content and rendering other attributes. When changing the definition of an object property, the internal cache of the definition was not invalidated correctly. This could cause the change not to take effect immediately. When, for example, the “inheritable” flag of folder object property definition was changed, and a new folder was created, it could happen that the old inheritance behavior was executed. This has been fixed now. Multichannelling: Renaming the publish directory of a localized folder back to the one of the master folder didn‘t work in some cases. This has been fixed. Fixed a problem where the permissions of templates linked to a folder in the wastebin only can‘t be determined anymore. This can cause imports to fail with an “Insufficient permissions” error. LDAP: Fixed an issue with Windows 2003 Active Directory referrals when someone tries to login by setting the LDAP_OPT_REFERRALS option to 0. If you encounter an error after updating, please set the setting $LDAP_LOGIN[‘referrals‘] = 1; in the configuration. Previously, templates that were only linked to one folder were wrongly deleted when the folder was moved to the wastebin. Now templates will only be removed when a folder is permanently deleted. A language in a node can‘t be deactivated when there is a page in the wastebin for this language. The error message has been improved to also display the count of pages in the wastebin for this language. Updated compatibility list and installation guide. It is mandatory to use the Oracle JDK with Gentics CMS. A note has been added to the faq for contentrepositories that explains the output of the data check. Changing permissions produced unnecessary database locks. This could cause errors while changing permissions due to lock wait timeouts. The SQL statements for changing permissions have been modified to avoid unnecessary locks and reduce the possibility for lock wait timeout errors. Installation Package: Correctly install and enable nodectl service. PLinks with attributes other than Aloha links were rendered with the “aloha-block” CSS class, which was removed when the page was fully loaded. This lead Aloha editor to believe pages containing links have been modified, even if nothing was changed. This has been fixed. The documentation of the Import in the Guides has been extended to explain, what will happend during an import. Visiting the startpage caused errors to be logged when trying to get the estimated remaining time of the publishrun. This has been fixed. The paging controls were missing in the usage overviews of files and images. Also the overview of folders using an object did not list those folders, but the subfolders of the objects parent folder. These issues have been fixed. The version diff did not ignore differences in zero-width whitespace characters. This caused diffs shown in places with no visible difference. This has been fixed now, zero-width whitespace characters will now be ignored. When a master page was deleted from the publish cache, publications of its localized copies failed because dependencies could not be handled properly. This has been fixed. The publish statistics for publishing files into ContentRepositories has been fixed to better distinguish between several steps. Tagtype parts of the type “Text (custom form)” could not be migrated with the migration feature. This has been fixed. Updater: Fixed that the update file is not deleted and downloaded again when it is corrupted. The SQL dump file for new CMS installations has been updated in order to fix some issues. The following changes have been done: Fixed a nullpointer-exception that could happen when starting the CMS the first time and the UUID of the demo node is null. The logs view can now be filtered by maintenance actions. When the internal scheduler fails to start upon start of the Tomcat (e.g. due to failures while connecting to the DB), the Tomcat will fail to start with an error message logged. Before this fix, Tomcat would start anyways and some background operations like deleting or localizing objects would only be queued, but never executed. When publishing into a ContentRepository with instant publishing, objects that were disinherited in some channels were incorrectly removed from the ContentRepository completely (for all channels). This has been fixed now. Since changing the inheritance of objects possibly affects many objects, instant publishing has been turned off for changing the inheritance. After changing the inheritance of objects, a publish process is required to add or remove objects to/from the ContentRepository. When copying links in the Aloha Editor the second link would not be converted to a new link tag, causing multiple instances of links with the same (tag) ID on the page. This has been fixed. Deleted images were still visible in the minibrowser. This has been fixed. Loading a Template using the REST API produced an error when a request accepted the mimetype “application/xml” for the response. This has been fixed. When restoring a page from the wastebin, the page was not visible in it‘s folder right away because the cache of the parent folder was not refreshed. This has been fixed. Creating a copy of an image immediately after cropping would fail without an error message. This has been fixed. When objects were moved between folders, pages containing automatic overviews were not always dirted. This has been fixed now. Aloha Editor gcn-plugin: When an editable was configured to show no insert buttons (empty array), the arena that contains the buttons normally was still shown. This has been fixed. Aloha Editor gcn-plugin: Since the bugfix for SUP-2365, the editable configuration for the insert-tag buttons didn‘t work correctly anymore. This has been fixed. Image Manipulation: replaced a confusing warning when saving auto-resized images with a clearer info message. Fixed a GenticsImageStore bug which caused resizing operations to fail due to a broken dependency of http-client. This also affected the image manipulation tool. The bug affected all GCN versions that were released after 17.02.2016. Aloha Editor gcn-plugin: Inserting new tags didn‘t work anymore because the construct property mayBeSubTag got renamed in the previous bugfix for SUP-2429 but wasn‘t renamed in the gcn-plugin. This has been fixed. The sidebar pannels of the GCN FileLink plugin now look more like their counterparts in the link plugin. When Drag & Drop was disabled and several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in nested editables, the edit and delete icons could be inactive. This has been fixed. Resized images in the GenticsImageStore were not properly updated when the binary contents of an image changed. This has been fixed. The Java REST API client didn‘t correctly define the Maven dependency for jackson-jaxrs. That‘s why this dependency had to be defined manually before. This has been fixed now. Fixed a null pointer exception that sometimes occured when deleting a whole node with templates. Java rest client: Fixed the jackson object mapper throwing a parse error when calling the rest method “construct.list“. In order to fix this the method “Construct.getMayBeSubTag“ has been renamed to “Construct.getMayBeSubtag”. Rest API: Passing global object IDs in the new UUID format didn‘t work. This has been fixed. Installation guides: Changed the text about trigger deletion to be more clear on when it needs to be done and added the — max_allowed_packet option to all mysqldump calls. When editing a page, it was possible to insert new tags inside links. This corrupted the link when saving the page. Inserting tags inside links is not possible anymore now. When the wastebin feature is activated, the startpage flag icon wasn‘t shown correctly when the pages folder was localized and then moved to the wastebin (deleted). This has been fixed. An error was logged when rendering a velocity part that resolved a “Select (single)”-part where nothing was selected. This has been fixed. Fixed the Javascript error “Uncaught TypeError: Cannot read property ‘themes‘ of undefined” that occured when loading or saving a page. Node id and folder id were missing in the php session when editing object properties. This has been fixed. When a new tag was inserted into a page using Aloha Editor and then the user navigated away from the page (without saving first), the page was not saved and the user did not get the notification about unsaved changes in the page. This has been fixed now. The user will get a notification about unsaved changes in such cases. If there are two consecutive tables in an editable, the draghandle of the second table could overlap cells from the first table. This has been fixed. When using the GCN filelink plugin the filelink tag was not removed, when the link was changed to an external URL. This has been fixed. The background job for cleaning old systemsessions could cause deadlocks in the database, which caused errors while users tried to log in into the backend. Those deadlocks have been fixed now. When using the GCN JS API to create a tag in a page, the information about the pages tags was not always properly updated (e.g. when copying a tag containing nested tags). This has been fixed. In the page list view the sequence of the columns was mixed up after a new column was added in bugfix SUP-1815. This has been fixed. When using the features Fixed a bug with siteminder datasources, where the reading of the datasource values didn‘t work, when the publish_cache feature is activated. The version difference view didn‘t correctly work for HTML pages. This has been fixed. After editing the page properties and saving the changes, the page was not unlocked. This has been fixed. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the edit and delete icons could be inactive. This has been fixed. When publishing images/files into a contentrepository and having the attribute binarycontent set to be a filesystem attribute, in some rare cases it could happen, that the attribute contained old data. This has been fixed now. Certain corrupt images files (e.g. empty files) could cause the publish process to fail, when the image needed to be resized by the GenticsImageStore. This has been fixed. When images used in the GenticsImageStore were put into the wastebin, this sometimes could let the publish process fail with “Couldn‘t find image { [ID] } to link”. This has been fixed now. Optional Manual Change For copying Pages with the REST API you can now set multiple SourcePage Ids in the PageCopyRequest When the publish process was interrupted while synchronizing deleted objects with content repositories, the publish process did not stop, but just skipped over to the next step (publishing pages). This has been fixed now, when the publish process is interrupted in that state, it will stop as soon as possible. When inserting a file link, with the FileLink plugin the freshly inserted link was not visible for editing. This has been fixed. When pages were published using the time management (“publish at”), and the publish process needed to create a version, this new version did not have an editor set. This has been changed now, so that the user who last edited the page will be set as editor of the page version. Copying nodes where objects have been moved to the wastebin (deleted) didn‘t work. This has been fixed. The systemsession table was not cleaned regularly from old session data, which could cause the table to grow too big. This has been fixed now. Optional Manual Change The FileLink plugin did not treat images as files. If an image was selected, a normal link to that image was created. This has been fixed now, so that also images will be treated as files. In inbox messages the links to pages in multichannel nodes where not resolved correctly. The link would always point to the page in the channel the user last worked in. This has been fixed: links to pages in messages will now always open the page in the channel, where the page can be edited without localizing it. Fixed the tree frame becoming smaller each time it is loaded in Internet Explorer. Also fixed some Javascript errors in the tree. When a page, which is published and is the target of a link in another page is put into the wastebin, the editor of the other page received an inbox message about the invalid link with the reason, that the link target was taken offline. While this is technically correct (the page is first taken offline and then put into the wastebin), it might be misleading. Therefore the inbox message for that case has been changed to be like when the page is deleted and not put into the wastebin. When clicking the “Create copy“ button when editing an image, the button label changed to “Duplicate”. This has been fixed, so that it stays the same. The preview tooltip in the repository browser has been moved, so that it will no longer overlap with nearby filenames. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the Aloha editor would only convert the first one into an aloha-block. This behavior has been changed, so that every occurrence of a tag will become a block and get edit and delete buttons. When linking/unlinking a single template from folders, where the user does not have permission to link the template to a folder where the template is already link, the user would always get an error message stating the missing permission. However, linking/unlinking the template to/from folders where the user has the permission still worked as expected. This issue has been fixed now, so that the unnecessary message will not be shown any more. When the feature The guides on using meta attributes were updated to include a warning about using the Node-Style syntax in templates containing “<” characters. When deleting tags in a page the page status was not updated to “modified”. This has been fixed. The maintenance details in the administration menu listed pages which were to be taken offline as pages to be published. This has been fixed. When opening the object properties of a file and then navigating to the properties using the link in the assistent frame, the dialog possibly showed properties of another file. When clicking “Cancel” from the properties dialog, the list of images was shown instead of the list of files. Both issues have been fixed now. Pages with special regular expression characters in their names (or filenames) could not be saved sometimes. This has been fixed. Some object attributes that should be displayed in the Aloha editor sidebar where missing in certain renditions of the GCN link browser, so the displayed information was not updated properly. This has been fixed. When the list of object properties of an object is sorted by name, the list will not be grouped by object categories. It is now possible to restore the original grouped display by repeatedly clicking on the column header. Each click on the column header will change the sorting state between # Sorted in ascending order # Sorted in descending order # Grouped by category Fixed the error “Error while getting timestamp of last publish process” that can happen when the DirtQueue worker runs the publish queue migration. An internal error while exporting objects due to missing translatable names has been fixed. When the tagfill dialog of an overview tag is opened, where the options to select type and source of the listed objects was restricted, so that the current data in the tag is not valid any more, the tagfill dialog will be opened at step 1 and the list of currently selected objects will be cleared. On some systems (depending on the PHP version and environment settings), the maintenance message was show in the banner with incorrect UTF-8 encoding. This has been fixed now. When publishing a page with more than 16MB of content into the filesystem using multithreaded publishing, the page was not written into the filesystem, but no error was logged and the publish run did not fail. This has been changed now, so that the publish run will fail with an error like When importing bundles using an export URL, the global ID of the bundle to import was not generated correctly in response to the request of the download URL. This caused the check whether the bundle was already installed on the system to fail. This has been fixed now. It is important to note, that the system providing the export has to be updated for this fix. When the feature The Workflow Timetrigger has been fixed to ignore pages in the wastebin. When using the publish_cache, rendering a page in a channel in publish mode using the REST API failed with an Internal Error. This has been fixed now. When a node was deleted, the objects in the wastebin of that node were left behind. This could cause subsequent errors and has been fixed now. The gcn-linkbrowser plugin would filter out attributes from repository elements, even if the link plugin was configured to display them in the sidebar. This has been fixed. Under special circumstances, an import could fail with an Internal Error, due to a NullPointerException in UnlockContentTransactional.onDBCommit (while commiting the transaction). This has been fixed now. The missing REST API methods Resolving properties of tag parts during rendering a velocity part could fail without any exception logged. This has been fixed now. When working with the CMS backend, some unnecessary data was permanently stored in the user session. This could lead to problems, if the session grew too big. The behaviour has been changed now, so that some session data will be cleared from the session if the user logs out. The following tagmap entries are no longer reserved and can be modified or deleted: No newlines were allowed in the system maintenance message. This has been fixed. Updating the tomcat to a newer version sometimes did not work due to an error in the version number comparison. With this update, the tomcat version will be updated to the last recent version, if this failed to happen during previous updates due to this bug. This has been fixed now. When applying this update, the packaged Tomcat will be updated to version 7.0.65 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-x.x.x) after updating. Sometimes when closing a page that was opened in edit mode using Aloha Editor without any changes, Aloha Editor incorrectly detected a content change. This has been fixed now. For ContentRepositories that have attributes like e.g. the content of pages optimized, the ContentRepository browser would always display the content when querying the Contentmap, even if the checkbox labelled “Also display large contents.” was not checked. The HTML tags in the content were not escaped, which caused HTML in the content to be interpreted. Both issues have been fixed now. The GCN integration plugin for the Aloha editor used the CSS class When using the Java Rest Client to update pages, an error occurred, unless the mediatype of the posted entity was explicitly forced to MediaType.APPLICATION_JSON_TYPE. The error has been fixed now. However, forcing the mediatype to MediaType.APPLICATION_JSON_TYPE is recommended nevertheless. The documentation of the REST API Java Client now contains examples for handling binary data of files. Fixed two occurences of a wrong proxy prefix for Gentics-Imagestore-URLs in frontend editing. This fixes two errors when doing Image Manipulation with frontend editing: The usageinfo for pages also considered objects in the wastebin, which has been fixed now. When opening a page from the queue, the related links were missing. They have been added now. It was not possible to create page variants of a page in another folder, if the other folder contained a page in the wastebin having the same name as the original page. This has been fixed now. In some cases, when maintenance mode was active users could not log in anymore. Also the maintenance banner would cover up the login fields preventing clicks on the login form. These issues have been fixed. The pageimport possibly imported objects into folders in the wastebin. This has been fixed now. When the GenticsImageStore runs out of sync and holds references to resized images, that do not exist in the filesystem, the publish process failed with an error. This has been fixed now, so that missing resized images will be recreated on demand, without failing publish process. When objects contained in an import were deleted, viewing the list of imported objects could lead to an SGB. The same error could happen when trying to delete the import. Those issues have been fixed now. The recursive search for files or images did not find files/images in subfolders of folders, where the user did not have permission to view files/images. This also affected the wastebin (deleted files/images were not shown in the wastebin if the user did not have permission to view files/images in one of the superfolders). This has been fixed now. When using multichanneling, restoring a localized object from the wastebin would also restore the corresponding master object, even if the user had no permission to do so. This has been fixed and the behavior of the wastebin feature has been changed, so that the overview of deleted objects shows if any other objects would be implicitly restored. When using multichanneling the usage overview would not list some objects in other channel structures. When using the Some fields for REST API requests were not documented, this has been fixed. Some fields for REST API requests were not documented, this has been fixed. When taking pages offline or deleting them, the notification about invalidated links would sometimes display the wrong path when using multichanneling. This has been fixed. The purgewastebin job will no longer try to instantly remove purged objects from content repositories, if they have instant publishing enabled. Setting of a target folder in an import did not work. This bug was introduced in 5.20.0 and has been fixed now. The Sometimes, deleting an import did not work and caused an SGB. This has been fixed now. When saving pages containing links in editables with Aloha Editor, links to internal pages, that are incorrectly rendered as external links will now also be transformed to internal links, if the URL does not start with http:// but directly with /CNPortletapp. The internal handling of PreparedStatements used an unnecessary large amount of memory in long running transaction (like an import), which could lead to performance problems and even OutOfMemory errors. This has been fixed now. The purgewastebin job would fail when purging pages that are linked in still published pages. This has been fixed now. When configuring custom columns for the repository browser, they were always made sortable, even if “sortable” was set to false. This has been fixed now. The detection of GenticsImageStore URLs has been improved to fix some special cases Sometimes an error during a publish run did not cause a rollback of the current transaction (which could in turn cause subsequent publish runs to stall indefinitely). This has been fixed. The possible values for the “sortby” query parameter has been documented in the REST API documentation for methods that return sorted lists of elements. Pages containing tags that have values referencing a part of the construct which no longer exists could not be saved any more. This has been fixed now, such data inconsistencies will be cleaned automatically while saving. When using login via SSO, sometimes user session were completely reset between logins. Custom settings like the current content language, the paging or open folders in the tree were lost in such cases. This has been fixed now. When an editor entered more than 255 characters into the description field for pages, folders or files, this either caused an SGB or superfluous characters were silently removed (depending on the database configuration). This has been changed now, so that the user will get a descriptive error message. When a page is modified because the tagtype of a template tag (editable in pages) was changed, the editor and edate were changed, if the page was also missing some editable tags from the template. This has been fixed now. Sometimes when multichanneling was used, user permissions for the wastebin were not checked correctly and users could not restore or delete objects from the wastebin. This has been fixed. Optional Manual Change This change only applies when not using the packaged JAVA (/Node/java doesn‘t exist). The java.sh script has been updated in order to allow using own JAVA installations. AFTER updating, the java.sh file has to be replaced: The new setting $NO_MAX_FILESIZE allows to disable the file upload limit for specific groups. See the Gentics Content.Node Guides for details. The publish process now prints the number of successfully published folders, pages and files after completion. This information will be output in the scheduler. Additional search filters in the following folder Rest API methods now allow to search for items which were created, edited or published before a certain timestamp. The following new Any objects that are not found, or for which the user does not have the necessary permissions, are ignored and will not be part of the resulting list. The REST API has been extended, to allow saving and creating nodes: A new flag “disinherit default“ has been added for all disinheritable objects. When creating a new channel, all objects with this flag will be automatically disinherited. It can be set in the “inheritance” dialog. The documentation of the Pageurl/Fileurl parttype now includes the information that the url property is only set for internal links. The scheduler will now show more detailed information (the complete stacktrace with causing exceptions), when the publish run fails with an exception. When a folder is deleted (put into the wastebin), a check was done for objects having localized copies in the structure, which would also be deleted. This check has been extended to also check for local objects (objects that were created in subchannels of the deleted folder‘s channel). When objects in a multichannelling environment were published into a contentrepository with the permission information added, the permissions of localized folders were not correctly inherited from their master folder. This has been fixed now. When the master page of a localized copy was taken offline, editors were notified that pages in the channel linking to the localized copy contained an invalid link now, although the link was still valid (linking the localized copy). This has been fixed now. When a new inline editable part was added to a construct and pages containing tags of that construct were edited using Aloha Editor, the new parts could not be filled unless the page was saved once. This has been fixed now. When a specific magiclinkconstruct was configured, the links were still rendered as blocks (with edit icon) in edit mode. This has been fixed now. The synchronization of pages with changes made to template tags was inconsistent and has been modified: This fix contains a change in the database structure, which could cause the update to take longer than usual. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which has been fixed now. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. This has been fixed now. Objects (files, images, pages or folders) that were restored from the wastebin did not automatically republish other objects that directly referenced the restored object. This has been fixed now. The assistant frame would not show the correct number of images in a folder, when there was an active filter for the images. This has been fixed. Pagetags were still rendered, even if the targeted page was put into the wastebin. This has been fixed now. When the publish directory of a folder or the hostname of a node was changed, republishing of pages did not always work correctly, when the node published only into the file system. This has been fixed now. Fixed the quickjump also opening deleted pages when pressing enter instead of selecting an autocomplete result. Deleted pages will not be opened anymore. Also disabled the cache for the autocompletion as it could show old search results. Objects that were put into the wastebin and restored from the wastebin between two publish runs where sometimes incorrectly removed from the content repository during the next publish run. This has been fixed now. Files and folders were not correctly published after restoring them from the wastebin. This has been fixed. The SQL Statements used to get the migration status for tagtype migrations was inefficient and could cause long running REST Requests. This has been fixed. Additionally, it is now possible to configure the polling interval for getting the migration status (default is still 1 second). See the guides for details. If the previous request to get the migration status did not return before the next request is due, the next request will be omitted now. An internal pool for prepared database statements was not properly sized and could consume a large amount of memory during a long running publish process. This could lead to memory exhaustion and failing publish processes. The maximum number of pooled connections has been reduced to 10000 by default, and can now be configured as described in the guides. Due to an incorrect consistency check, it was not possible to reinherit an object into a channel, when the parent folder was localized in that channel. This has been fixed now. When using the CASIntegrationFilter or HttpAuthFilter for SSO to the CMS backend, it could be possible that multiple identical users were created in the CMS backend database, if multiple concurrent requests with the same new user where done. This has been fixed now. Removing a construct from a node failed with the incorrect error message “Array”, if the construct would only be linked to nodes that user had no permission to unlink constructs from. This has been fixed now. Requests to the REST API created write locks to the user‘s systemsession entry, that would persist for the whole request duration. This caused parallel requests with the same session to be blocked until the first request was finished. This has been fixed now, the write lock to the systemsession will be lifted as soon as possible. Optional Manual Change The datasource “[Navigation] sortby“ in our Standard CMS installation can‘t be used for folder sorting in navigations unless you change the entry “Folder Sorting / Ordnersortierung“ from “obj.sortby“ to “object.sortorder”. This is fixed in the mysql dump for new installations. ContentRepository browser: An error was printed, when one of the CRs is using the same MySQL username and password like the CMS itself and persistent database connections are activated. This has been fixed. The elements selection of an overview could contain elements that were already put into the wastebin (deleted). This has been fixed. An error in the node library has been fixed, which could cause the CMS to hang when using instant publishing into multichannelling aware contentrepositories. If users where deactivated in the CMS, but not removed from their groups, those users were still returned by the Rest API: Fixed a bug in the auth/validate method where a session with ID -1 was considered as valid. Optional Manual Change Fixed a bug that breaks updating the CMS from the local filesystem. If you currently have a version installed, that has been released between 23.03.2016 and 24.05.2016, please read this page in order to update. Fixed a “Data inconsistent” (missing construct) error that could happen when loading, saving or publishing objects that have been created during the deletion of a tagtype. This affected content tags, template tags and object tags. If a user had no paging acitivated he could still only see a maximum of 18 entries in the wastebin. This has been fixed. Added a missing migration step in the package migration guide for “SUSE Enterprise Linux Server”. ImageMagick also has to be installed during the package migration. The publish log will now contain render times for the content and other attributes of pages separately. Enhanced fetching the latest available CMS update from the update server, so it doesn‘t block the CMS start page loading unnecessarily. That means if the update server is unreachable, the start page will still work. Also the current CMS version is now read from the Rest API, and not the database anymore. The error message for duplicate folder names (when creating or updating a folder) will now contain the full path of the conflicting folder. When the conflicting folder exists in another channel, the path will be shown in that channel. When a node was copied, where the source node contained templates that were linked to folders in the wastebin, the copies of the templates were also linked to the source folders in the wastebin. This has been fixed now, the copied templates will only be linked to folders in the target node. Installation: The SQL dump contained trigger information that could cause SQL errors when the MySQL user didn‘t match ‘node_cms@localhost. The triggers have been removed out of the dump file. The performance for the display of objects in the wastebin has been improved. The object counts in the assistent frame will now be fetched asynchronously. This means that the numbers might appear (or be updated) with a slight delay. The cache for node objects can now be individually configured for object type. See the Guides for details. The The DPI value shown for a file in the image list of a folder wasn‘t always correct and sometimes differed from the DPI value from the Rest API/database. The DPI value output is now the same. When using the old archive workflow to move files into another folder (instead of deleting them), the workflow failed, when the archive folder already contained a file with a name that was only different in case. This has been fixed now. When copying a page to the root folder of a channel it was copied to the master of the root folder of the channel instead. This has been fixed. The publish statistics for rendering pages have been improved to distinguish between rendering content and rendering other attributes. When changing the definition of an object property, the internal cache of the definition was not invalidated correctly. This could cause the change not to take effect immediately. When, for example, the “inheritable” flag of folder object property definition was changed, and a new folder was created, it could happen that the old inheritance behavior was executed. This has been fixed now. Multichannelling: Renaming the publish directory of a localized folder back to the one of the master folder didn‘t work in some cases. This has been fixed. Fixed a problem where the permissions of templates linked to a folder in the wastebin only can‘t be determined anymore. This can cause imports to fail with an “Insufficient permissions” error. LDAP: Fixed an issue with Windows 2003 Active Directory referrals when someone tries to login by setting the LDAP_OPT_REFERRALS option to 0. If you encounter an error after updating, please set the setting $LDAP_LOGIN[‘referrals‘] = 1; in the configuration. Previously, templates that were only linked to one folder were wrongly deleted when the folder was moved to the wastebin. Now templates will only be removed when a folder is permanently deleted. A language in a node can‘t be deactivated when there is a page in the wastebin for this language. The error message has been improved to also display the count of pages in the wastebin for this language. Updated compatibility list and installation guide. It is mandatory to use the Oracle JDK with Gentics CMS. A note has been added to the faq for contentrepositories that explains the output of the data check. Changing permissions produced unnecessary database locks. This could cause errors while changing permissions due to lock wait timeouts. The SQL statements for changing permissions have been modified to avoid unnecessary locks and reduce the possibility for lock wait timeout errors. Installation Package: Correctly install and enable nodectl service. PLinks with attributes other than Aloha links were rendered with the “aloha-block” CSS class, which was removed when the page was fully loaded. This lead Aloha editor to believe pages containing links have been modified, even if nothing was changed. This has been fixed. The documentation of the Import in the Guides has been extended to explain, what will happend during an import. Visiting the startpage caused errors to be logged when trying to get the estimated remaining time of the publishrun. This has been fixed. The paging controls were missing in the usage overviews of files and images. Also the overview of folders using an object did not list those folders, but the subfolders of the objects parent folder. These issues have been fixed. The version diff did not ignore differences in zero-width whitespace characters. This caused diffs shown in places with no visible difference. This has been fixed now, zero-width whitespace characters will now be ignored. When a master page was deleted from the publish cache, publications of its localized copies failed because dependencies could not be handled properly. This has been fixed. The publish statistics for publishing files into ContentRepositories has been fixed to better distinguish between several steps. Tagtype parts of the type “Text (custom form)” could not be migrated with the migration feature. This has been fixed. Updater: Fixed that the update file is not deleted and downloaded again when it is corrupted. The SQL dump file for new CMS installations has been updated in order to fix some issues. The following changes have been done: Fixed a nullpointer-exception that could happen when starting the CMS the first time and the UUID of the demo node is null. The logs view can now be filtered by maintenance actions. When the internal scheduler fails to start upon start of the Tomcat (e.g. due to failures while connecting to the DB), the Tomcat will fail to start with an error message logged. Before this fix, Tomcat would start anyways and some background operations like deleting or localizing objects would only be queued, but never executed. When publishing into a ContentRepository with instant publishing, objects that were disinherited in some channels were incorrectly removed from the ContentRepository completely (for all channels). This has been fixed now. Since changing the inheritance of objects possibly affects many objects, instant publishing has been turned off for changing the inheritance. After changing the inheritance of objects, a publish process is required to add or remove objects to/from the ContentRepository. When copying links in the Aloha Editor the second link would not be converted to a new link tag, causing multiple instances of links with the same (tag) ID on the page. This has been fixed. Deleted images were still visible in the minibrowser. This has been fixed. Loading a Template using the REST API produced an error when a request accepted the mimetype “application/xml” for the response. This has been fixed. When restoring a page from the wastebin, the page was not visible in it‘s folder right away because the cache of the parent folder was not refreshed. This has been fixed. Creating a copy of an image immediately after cropping would fail without an error message. This has been fixed. When objects were moved between folders, pages containing automatic overviews were not always dirted. This has been fixed now. Aloha Editor gcn-plugin: When an editable was configured to show no insert buttons (empty array), the arena that contains the buttons normally was still shown. This has been fixed. Aloha Editor gcn-plugin: Since the bugfix for SUP-2365, the editable configuration for the insert-tag buttons didn‘t work correctly anymore. This has been fixed. Image Manipulation: replaced a confusing warning when saving auto-resized images with a clearer info message. Fixed a GenticsImageStore bug which caused resizing operations to fail due to a broken dependency of http-client. This also affected the image manipulation tool. The bug affected all GCN versions that were released after 17.02.2016. Aloha Editor gcn-plugin: Inserting new tags didn‘t work anymore because the construct property mayBeSubTag got renamed in the previous bugfix for SUP-2429 but wasn‘t renamed in the gcn-plugin. This has been fixed. The sidebar pannels of the GCN FileLink plugin now look more like their counterparts in the link plugin. When Drag & Drop was disabled and several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in nested editables, the edit and delete icons could be inactive. This has been fixed. Resized images in the GenticsImageStore were not properly updated when the binary contents of an image changed. This has been fixed. The Java REST API client didn‘t correctly define the Maven dependency for jackson-jaxrs. That‘s why this dependency had to be defined manually before. This has been fixed now. Fixed a null pointer exception that sometimes occured when deleting a whole node with templates. Java rest client: Fixed the jackson object mapper throwing a parse error when calling the rest method “construct.list“. In order to fix this the method “Construct.getMayBeSubTag“ has been renamed to “Construct.getMayBeSubtag”. Rest API: Passing global object IDs in the new UUID format didn‘t work. This has been fixed. Installation guides: Changed the text about trigger deletion to be more clear on when it needs to be done and added the — max_allowed_packet option to all mysqldump calls. When editing a page, it was possible to insert new tags inside links. This corrupted the link when saving the page. Inserting tags inside links is not possible anymore now. When the wastebin feature is activated, the startpage flag icon wasn‘t shown correctly when the pages folder was localized and then moved to the wastebin (deleted). This has been fixed. An error was logged when rendering a velocity part that resolved a “Select (single)”-part where nothing was selected. This has been fixed. Fixed the Javascript error “Uncaught TypeError: Cannot read property ‘themes‘ of undefined” that occured when loading or saving a page. Node id and folder id were missing in the php session when editing object properties. This has been fixed. When a new tag was inserted into a page using Aloha Editor and then the user navigated away from the page (without saving first), the page was not saved and the user did not get the notification about unsaved changes in the page. This has been fixed now. The user will get a notification about unsaved changes in such cases. If there are two consecutive tables in an editable, the draghandle of the second table could overlap cells from the first table. This has been fixed. When using the GCN filelink plugin the filelink tag was not removed, when the link was changed to an external URL. This has been fixed. The background job for cleaning old systemsessions could cause deadlocks in the database, which caused errors while users tried to log in into the backend. Those deadlocks have been fixed now. When using the GCN JS API to create a tag in a page, the information about the pages tags was not always properly updated (e.g. when copying a tag containing nested tags). This has been fixed. When using the features Fixed a bug with siteminder datasources, where the reading of the datasource values didn‘t work, when the publish_cache feature is activated. The version difference view didn‘t correctly work for HTML pages. This has been fixed. After editing the page properties and saving the changes, the page was not unlocked. This has been fixed. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the edit and delete icons could be inactive. This has been fixed. When publishing images/files into a contentrepository and having the attribute binarycontent set to be a filesystem attribute, in some rare cases it could happen, that the attribute contained old data. This has been fixed now. Certain corrupt images files (e.g. empty files) could cause the publish process to fail, when the image needed to be resized by the GenticsImageStore. This has been fixed. When images used in the GenticsImageStore were put into the wastebin, this sometimes could let the publish process fail with “Couldn‘t find image { [ID] } to link”. This has been fixed now. In the page list view the sequence of the columns was mixed up after a new column was added in bugfix SUP-1815. This has been fixed. Optional Manual Change For copying Pages with the REST API you can now set multiple SourcePage Ids in the PageCopyRequest When the publish process was interrupted while synchronizing deleted objects with content repositories, the publish process did not stop, but just skipped over to the next step (publishing pages). This has been fixed now, when the publish process is interrupted in that state, it will stop as soon as possible. When inserting a file link, with the FileLink plugin the freshly inserted link was not visible for editing. This has been fixed. When pages were published using the time management (“publish at”), and the publish process needed to create a version, this new version did not have an editor set. This has been changed now, so that the user who last edited the page will be set as editor of the page version. Copying nodes where objects have been moved to the wastebin (deleted) didn‘t work. This has been fixed. The systemsession table was not cleaned regularly from old session data, which could cause the table to grow too big. This has been fixed now. Optional Manual Change The FileLink plugin did not treat images as files. If an image was selected, a normal link to that image was created. This has been fixed now, so that also images will be treated as files. In inbox messages the links to pages in multichannel nodes where not resolved correctly. The link would always point to the page in the channel the user last worked in. This has been fixed: links to pages in messages will now always open the page in the channel, where the page can be edited without localizing it. Fixed the tree frame becoming smaller each time it is loaded in Internet Explorer. Also fixed some Javascript errors in the tree. When a page, which is published and is the target of a link in another page is put into the wastebin, the editor of the other page received an inbox message about the invalid link with the reason, that the link target was taken offline. While this is technically correct (the page is first taken offline and then put into the wastebin), it might be misleading. Therefore the inbox message for that case has been changed to be like when the page is deleted and not put into the wastebin. When clicking the “Create copy“ button when editing an image, the button label changed to “Duplicate”. This has been fixed, so that it stays the same. The preview tooltip in the repository browser has been moved, so that it will no longer overlap with nearby filenames. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the Aloha editor would only convert the first one into an aloha-block. This behavior has been changed, so that every occurrence of a tag will become a block and get edit and delete buttons. When linking/unlinking a single template from folders, where the user does not have permission to link the template to a folder where the template is already link, the user would always get an error message stating the missing permission. However, linking/unlinking the template to/from folders where the user has the permission still worked as expected. This issue has been fixed now, so that the unnecessary message will not be shown any more. When the feature The guides on using meta attributes were updated to include a warning about using the Node-Style syntax in templates containing “<” characters. When deleting tags in a page the page status was not updated to “modified”. This has been fixed. The maintenance details in the administration menu listed pages which were to be taken offline as pages to be published. This has been fixed. When opening the object properties of a file and then navigating to the properties using the link in the assistent frame, the dialog possibly showed properties of another file. When clicking “Cancel” from the properties dialog, the list of images was shown instead of the list of files. Both issues have been fixed now. Pages with special regular expression characters in their names (or filenames) could not be saved sometimes. This has been fixed. Some object attributes that should be displayed in the Aloha editor sidebar where missing in certain renditions of the GCN link browser, so the displayed information was not updated properly. This has been fixed. When the list of object properties of an object is sorted by name, the list will not be grouped by object categories. It is now possible to restore the original grouped display by repeatedly clicking on the column header. Each click on the column header will change the sorting state between # Sorted in ascending order # Sorted in descending order # Grouped by category Fixed the error “Error while getting timestamp of last publish process” that can happen when the DirtQueue worker runs the publish queue migration. Removed a wrong changelog note from version 5.20.21 An internal error while exporting objects due to missing translatable names has been fixed. When the tagfill dialog of an overview tag is opened, where the options to select type and source of the listed objects was restricted, so that the current data in the tag is not valid any more, the tagfill dialog will be opened at step 1 and the list of currently selected objects will be cleared. On some systems (depending on the PHP version and environment settings), the maintenance message was show in the banner with incorrect UTF-8 encoding. This has been fixed now. When publishing a page with more than 16MB of content into the filesystem using multithreaded publishing, the page was not written into the filesystem, but no error was logged and the publish run did not fail. This has been changed now, so that the publish run will fail with an error like When importing bundles using an export URL, the global ID of the bundle to import was not generated correctly in response to the request of the download URL. This caused the check whether the bundle was already installed on the system to fail. This has been fixed now. It is important to note, that the system providing the export has to be updated for this fix. When the feature The Workflow Timetrigger has been fixed to ignore pages in the wastebin. When using the publish_cache, rendering a page in a channel in publish mode using the REST API failed with an Internal Error. This has been fixed now. When a node was deleted, the objects in the wastebin of that node were left behind. This could cause subsequent errors and has been fixed now. The gcn-linkbrowser plugin would filter out attributes from repository elements, even if the link plugin was configured to display them in the sidebar. This has been fixed. Under special circumstances, an import could fail with an Internal Error, due to a NullPointerException in UnlockContentTransactional.onDBCommit (while commiting the transaction). This has been fixed now. The missing REST API methods Resolving properties of tag parts during rendering a velocity part could fail without any exception logged. This has been fixed now. When working with the CMS backend, some unnecessary data was permanently stored in the user session. This could lead to problems, if the session grew too big. The behaviour has been changed now, so that some session data will be cleared from the session if the user logs out. The following tagmap entries are no longer reserved and can be modified or deleted: No newlines were allowed in the system maintenance message. This has been fixed. Updating the tomcat to a newer version sometimes did not work due to an error in the version number comparison. With this update, the tomcat version will be updated to the last recent version, if this failed to happen during previous updates due to this bug. This has been fixed now. When applying this update, the packaged Tomcat will be updated to version 7.0.65 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-x.x.x) after updating. Sometimes when closing a page that was opened in edit mode using Aloha Editor without any changes, Aloha Editor incorrectly detected a content change. This has been fixed now. For ContentRepositories that have attributes like e.g. the content of pages optimized, the ContentRepository browser would always display the content when querying the Contentmap, even if the checkbox labelled “Also display large contents.” was not checked. The HTML tags in the content were not escaped, which caused HTML in the content to be interpreted. Both issues have been fixed now. The GCN integration plugin for the Aloha editor used the CSS class When using the Java Rest Client to update pages, an error occurred, unless the mediatype of the posted entity was explicitly forced to MediaType.APPLICATION_JSON_TYPE. The error has been fixed now. However, forcing the mediatype to MediaType.APPLICATION_JSON_TYPE is recommended nevertheless. The documentation of the REST API Java Client now contains examples for handling binary data of files. Fixed two occurences of a wrong proxy prefix for Gentics-Imagestore-URLs in frontend editing. This fixes two errors when doing Image Manipulation with frontend editing: The usageinfo for pages also considered objects in the wastebin, which has been fixed now. When opening a page from the queue, the related links were missing. They have been added now. It was not possible to create page variants of a page in another folder, if the other folder contained a page in the wastebin having the same name as the original page. This has been fixed now. In some cases, when maintenance mode was active users could not log in anymore. Also the maintenance banner would cover up the login fields preventing clicks on the login form. These issues have been fixed. The pageimport possibly imported objects into folders in the wastebin. This has been fixed now. When the GenticsImageStore runs out of sync and holds references to resized images, that do not exist in the filesystem, the publish process failed with an error. This has been fixed now, so that missing resized images will be recreated on demand, without failing publish process. When objects contained in an import were deleted, viewing the list of imported objects could lead to an SGB. The same error could happen when trying to delete the import. Those issues have been fixed now. The recursive search for files or images did not find files/images in subfolders of folders, where the user did not have permission to view files/images. This also affected the wastebin (deleted files/images were not shown in the wastebin if the user did not have permission to view files/images in one of the superfolders). This has been fixed now. When using multichanneling, restoring a localized object from the wastebin would also restore the corresponding master object, even if the user had no permission to do so. This has been fixed and the behavior of the wastebin feature has been changed, so that the overview of deleted objects shows if any other objects would be implicitly restored. When using multichanneling the usage overview would not list some objects in other channel structures. Some fields for REST API requests were not documented, this has been fixed. When taking pages offline or deleting them, the notification about invalidated links would sometimes display the wrong path when using multichanneling. This has been fixed. The purgewastebin job will no longer try to instantly remove purged objects from content repositories, if they have instant publishing enabled. Setting of a target folder in an import did not work. This bug was introduced in 5.20.0 and has been fixed now. The Sometimes, deleting an import did not work and caused an SGB. This has been fixed now. When saving pages containing links in editables with Aloha Editor, links to internal pages, that are incorrectly rendered as external links will now also be transformed to internal links, if the URL does not start with http:// but directly with /CNPortletapp. The internal handling of PreparedStatements used an unnecessary large amount of memory in long running transaction (like an import), which could lead to performance problems and even OutOfMemory errors. This has been fixed now. The purgewastebin job would fail when purging pages that are linked in still published pages. This has been fixed now. When configuring custom columns for the repository browser, they were always made sortable, even if “sortable” was set to false. This has been fixed now. The detection of GenticsImageStore URLs has been improved to fix some special cases Sometimes an error during a publish run did not cause a rollback of the current transaction (which could in turn cause subsequent publish runs to stall indefinitely). This has been fixed. The possible values for the “sortby” query parameter has been documented in the REST API documentation for methods that return sorted lists of elements. Pages containing tags that have values referencing a part of the construct which no longer exists could not be saved any more. This has been fixed now, such data inconsistencies will be cleaned automatically while saving. When using login via SSO, sometimes user session were completely reset between logins. Custom settings like the current content language, the paging or open folders in the tree were lost in such cases. This has been fixed now. When an editor entered more than 255 characters into the description field for pages, folders or files, this either caused an SGB or superfluous characters were silently removed (depending on the database configuration). This has been changed now, so that the user will get a descriptive error message. When a page is modified because the tagtype of a template tag (editable in pages) was changed, the editor and edate were changed, if the page was also missing some editable tags from the template. This has been fixed now. Sometimes when multichanneling was used, user permissions for the wastebin were not checked correctly and users could not restore or delete objects from the wastebin. This has been fixed. The default values of the variables “langvars“ and “pagevars“ in the PageAPI of the GCN Javascript API were wrongly documented as “false”. This has been corrected. Links could be created by pressing the insert link buttons, or by inserting a magic link tag from the insert tag menu. The later method was not intended, so the link tag is no longer shown in the insert menu. When DeleteInfo-objects where cached in the filesystem cache a NotSerializableException was thrown. This has been fixed: the class DeleteInfo is now serializable. When publishing pages using multichannelling and multithreaded publishing, where localized copies of pages were put into the wastebin, some errors could occur. The publish process could fail with an InconsistentDataException or inherited pages were sometimes not published into channels. These errors have been fixed now. When the feature Fixed an internal server error (white page) when administrating users in the GCN user management. Fixed some issues with activated maintenance mode: When CR publishing is enabled for a node, The RestAPI PageResource method /render rendered static links instead of Fixed the feature “move_perm_with_edit” not being respected anymore since 5.19.0, when moving a file. Also fixed an error message printing the wrong source folder, when the user has insufficient permissions to move an object in the source folder. Fixed a bug where Aloha Editor blocks (i.e. links) would be removed when saving the page, when a tag with the same name existed previously, but was removed by the editor. This only happened when the the page was not reloaded after saving. This can happen with Frontend editing and the Real editor mode. Fixed the approval of page publish requests not always working for pages in channels. The error message “Page not found” was displayed. The memory consumption for publishing pages that contain sorted overviews over pages when using publish cache has been reduced. Installation Package: Added execution of the database migration changelog to the documentation and the debian package. The documentation of the feature Publish Cache now contains a note about when the Publish Cache needs to be cleared and how this can be done. The performance of listing objects in the wastebin has been improved. When using the publish cache and a page was republished with modified content, the page variants of the page were also republished, but the publish cache of the page variants were not cleared. As a result, the page variants were republished with their old content. This has been fixed now. Creating a page could fail while making the proposed filename unique if too many other pages with similar filenames exist. This has been fixed now. Users with language specific edit permissions (given from roles) could see some actions in the menu for page lists, which they were not allowed to perform. Clicking on one of those menu items resulted in an error. This has been fixed now. The GenticsImageStore did not recognize URLs that started with //[hostname]/GenticsImageStore (without the protocol http: or https:). This has been fixed now. When updating Gentics Content.Node to a newer version, the progress display didn‘t work correctly sometimes. When using the feature publish_cache and only changing an object property of a page (without changing or manually republishing the page itself), the page was republished with the old object property value. This has been fixed now. When dirting pages using the maintenance dialog, the publish cache of the dirted pages were not renewed. This could cause pages to be published with old content. This has been fixed now. The automatic tomcat update failed on RHEL 5 because this system does not support the parameter “-V” of the sort command. This has been fixed. The GenticsImageStore failed to detect image URLs enclosed in cdata, which has been fixed now. When deleting a folder containing objects, it could happen that the following publish process failed with an “InconsistentDataException” while checking the dirted objects, which has been fixed now. When using the publish cache publishing pages with big page overviews could cause OutOfMemory errors. This has been fixed now. When publishing pages - using the publish cache - with tags where the Tagtype has been deleted, an error message was printed to the log file. This error has been removed. Fixed error when reading the XNL Configuration. This bug has been introduced in version 5.17.0. It is now possible to import objects from CMS versions >= 5.19.3 to CMS versions >= 5.18.44 although the format of global IDs is different. The performance of publish runs with many pages has been improved, when the GenticsImageStore is used. The REST API documentation incorrectly statet, that the nodeId for the call The Admin Info on the start screen of the CMS backend probably showed incorrect number of remaining objects during a publish process, which has been corrected now. When a node was deleted, the entries in the publish table for pages of that node were left behind. Such entries will now be removed at the start of every publish process. When the wastebin feature is activated, deleting a whole node didn‘t work correctly in some cases. This has been fixed now. When using the feature publish_cache, the publish process used too much memory which probably caused OutOfMemory errors. This has been fixed now. When importing a new Node containing an object with an overview, where the root folder of the new Node was selected, a NullPointerException could occur, which has been fixed now. Fixed pages being rendered with the wrong DOCTYPE sometimes when comparing 2 page versions and the page does not define a HTML 4 Doctype (but HTML 5 for example). Some internal Locks have been made less restrictive to avoid unnecessary locking of threads. When editing links with Aloha Editor and entering data containing special URL characters (like ‘#‘) the resulting query sent to the server was incorrect. Especially when the character ‘#‘ was used, the resulting query was an unbounded recursive search for all pages, which could lead to performance problems on the server and timeout errors in the client. This has been fixed now. On some occasions the publish process could fail with a NullPointerException when processing GenticsImageStore Urls. This has been fixed. When using Internet Explorer, the page would scroll to the top of the currently active editable when closing the tagfill dialog. This has been fixed now. Fixed a bug in the package, that would prevent the Tomcat from starting again when updating Gentics Content.Node. When publishing pages with tags where the Tagtype has been deleted, an error message was printed to the log file. This error has been removed. When applying this update, the packaged Tomcat will be updated to version 7.0.63 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. Added documentation in the faq-section for the correct start order of mysql, apache and tomcat When using Internet Explorer to insert tags into editables with a visible scrollbar, the page was scrolled to the top of the editable. This has been fixed now. When inserting tags in tables, the delete button was missing. Also tags with script elements, could be missing all their edit buttons. These issues have been fixed. When inserting inline tag elements, sometimes superfluous wrapper tags where inserted before and after the tag. This has been fixed. When using instant publishing and publish handlers, the publish handlers were not called for deleted objects are pages that were taken offline. This has been fixed now. When installing via the debian package, no sudoers configuration would be set at all. The package now correctly installs the needed settings and permissions. When a folder structure is deleted, in some circumstances, templates that would neither be linked nor used any more would not be deleted but remained in the database. This has been fixed now. When a language variant of a page with restricted inheritance was created, the new language variant did not have the same inheritance restrictions set. This has been fixed now. The update of the Java libraries while Tomcat is still running could cause errors (though Tomcat would start again cleanly after the update). When the CMS was in maintenance mode users could still login via SSO. The corresponding check has been added to the SSO login, to ensure that only the user who activated maintenance mode can access the CMS backend. When using the feature publish_cache, the property ttype for pages would resolve to The log entries for changing the inheritance of objects did not show the correct action in the log view, which has been fixed now. The log entries for start and end of the publish process did not show the correct action in the log view, which has been fixed now. When editing a page with the Aloha editor, the cursor would disappear in some browsers after inserting an inline tag, which prevented further editing. This has been fixed. Manual Change On systems running PHP Version 5.3.9 or higher, there is a new configuration option max_input_vars which should be set to a higher number. This setting limits the number of input variables, that can be posted to the server. The default setting (1000) prevents e.g. successful linking of templates to folders, if the folder tree shows more than 500 folders. We therefore recommend to raise the value of max_input_vars to e.g. 10000 in the file gtx_gcn_custom.ini. You have to restart the apache webserver after that. The path to this file varies between distributions: Sometimes, handling dependencies caused errors due to stale database connections. This has been fixed now. When deleted objects are shown in the object lists of channels, only the wastebin related actions will be available. The activated display of deleted objects will now be indicated by a label. In cases where the publish process is interrupted (cancelled) while waiting for a semaphore to write into a contentrepository, additional information about the thread which last acquired that semaphore will now be logged. When exporting objects with translatable names (like tagtypes or object property definitions), the export file could contain an inconsistency due to missing translations. This subsequently caused an “Internal Error” during import. This issue has been fixed. When changing the name of a construct part, the name was also changed for other newly created parts. This is because all newly created construct parts had the name id 1. This bug has been introduced in version 5.20.0. When using the GenticsImageStore for images published into the filesystem across nodes that share the same hostname or use a separate publish directory for binary contents, the resized images were not published into the correct paths. This could lead to errors in the publish process in cases of duplicate filenames. After this update, all published pages will be searched for images to be resized in order to correct incorrectly written resized images. This could cause the next publish run to take longer than usual. Saving of pages that contain lot‘s of new links may take some time. During this time, the editor has no indication that the new links are currently processed and prepared to be saved. The behaviour has been changed now, so that a progress information is shown during page save and preparing new links to be saved is done much more efficient. When closing the node properties dialog, an SGB occurred, which has been fixed now. The columns for storing dirt analysis information in the backend database sometimes where too small and have been extended now. Fixed possible javascript error on the CMS start page. For parts of type “File (Upload)”, the button to upload a new file was missing and has been readded. Fixed the file/image usage overview always showing 0 for each count and an SQL error being logged. Links to an anchor on the current page will be made absolute by the browser when they are pasted or moved within the same page. Those absolute URLs will now be fixed during saving. Sometimes a user who had all the required privileges could still get an error about insufficient permissions when trying to move a file. This has been fixed. When configuring a fixed pageSize for the repository browser, paging did not work as expected and has been fixed now. Saving values with a large number of characters could result in an error. This has been fixed. Making object properties of templates or folders editable in pages is deprecated and will be removed in a future version. Implementations that rely on this feature should be changed by creating object property definitions for pages with the same name as the object properties of folders or templates. Manual Change Java 8 Update Please update the used Java version to Server JRE 8u25 64 bit. Download the ‘Server JRE 8‘ package and extract it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the apache tomcat server once you finished this step using the /Node/bin/nodectl script. All direct dependencies on “/Node/java“ have been removed. It is now possible to use a system-wide installation of Java via the JAVA_HOME environment variable. An existing symlink or directory “/Node/java” will still take precedence over JAVA_HOME. The retry timeout for connections from the webserver to the tomcat has been disabled. This ensures availability after a restart of the CMS. It is now possible to install the Gentics CMS using a debian package. The publish performance when the feature “contentfile_auto_offline” is disabled has been improved. Import/Export: Enhanced the error handling of imports. The following conflicts now don‘t cause an “internal error“ anymore: Additionally, if an “internal error” occurs, the exception and the stacktrace are now directly visible in the UI. There is now also a new button to restart failed imports. The GenticsImageStore used during publication to the file system has been migrated to a new data structure, which allows for better performance. Also, periodic re-calculation of the images (whenever their cache entry expired) will not happen anymore. The migration takes place during the first publish run. Added a new query parameter “publish” to the Rest method /page/render that allows rendering a page or content in publish mode. It is now possible to show the system maintenance message in the banner above the menu, even if the maintenance mode is not activated. The display of the system maintenance message in the banner can be switched on and off in the systme maintenance dialog. Added a configurable threshold for the tagtype list in the Administration. The new setting $TAGTYPE_LIST_THRESHOLD has a default value of 1000. If the total number of tagtypes exceeds $TAGTYPE_LIST_THRESHOLD, the user has to enter a search term in the filter first in order to display tagtypes. When saving Aloha Editor pages, there will be a notification now after saving, that the page was saved successfully. In the user properties dialog, it is now possible to collapse or expand all nodes in the group tree. Enhanced the compatibility with Apache modules and any other things that inject variables into the apache _SERVER array. Added a new option “used” to the Rest API methods /folder/getFiles and /folder/getImages which allows to list files that are in use or not in use. The scheduler.log log file now logs the start and the end time for executed tasks. The names and descriptions of tagtypes and their parts can now be edited in both languages (German and English) directly without changing the language of the logged in user. A new Velocity directive #gtx_gis has been added, which allows using the GenticsImagesStore in a more reliable way. This is now the recommended way of using the GenticsImageStore. Please read the GenticsImageStore documentation for more information. The REST API has been enhanced: The feature list for nodes will now show more descriptive feature names. With the new Wastebin feature, deleted objects will be put into the wastebin instead of permanently deleting them. See the Wastebin Feature documentation for more details. In rare cases a NullPointerException could occur when uploading a file. This happened if the language id in the session of the user was invalid. This has been fixed. When saving page properties with an empty filename, the filename was not automatically generated from the (possibly changed) page name. This has been fixed. The documentation of the Import in the Guides has been extended to explain, what will happend during an import. Visiting the startpage caused errors to be logged when trying to get the estimated remaining time of the publishrun. This has been fixed. The paging controls were missing in the usage overviews of files and images. Also the overview of folders using an object did not list those folders, but the subfolders of the objects parent folder. These issues have been fixed. The version diff did not ignore differences in zero-width whitespace characters. This caused diffs shown in places with no visible difference. This has been fixed now, zero-width whitespace characters will now be ignored. When a master page was deleted from the publish cache, publications of its localized copies failed because dependencies could not be handled properly. This has been fixed. The publish statistics for publishing files into ContentRepositories has been fixed to better distinguish between several steps. Tagtype parts of the type “Text (custom form)” could not be migrated with the migration feature. This has been fixed. Updater: Fixed that the update file is not deleted and downloaded again when it is corrupted. The SQL dump file for new CMS installations has been updated in order to fix some issues. The following changes have been done: Fixed a nullpointer-exception that could happen when starting the CMS the first time and the UUID of the demo node is null. The logs view can now be filtered by maintenance actions. When the internal scheduler fails to start upon start of the Tomcat (e.g. due to failures while connecting to the DB), the Tomcat will fail to start with an error message logged. Before this fix, Tomcat would start anyways and some background operations like deleting or localizing objects would only be queued, but never executed. When publishing into a ContentRepository with instant publishing, objects that were disinherited in some channels were incorrectly removed from the ContentRepository completely (for all channels). This has been fixed now. Since changing the inheritance of objects possibly affects many objects, instant publishing has been turned off for changing the inheritance. After changing the inheritance of objects, a publish process is required to add or remove objects to/from the ContentRepository. When copying links in the Aloha Editor the second link would not be converted to a new link tag, causing multiple instances of links with the same (tag) ID on the page. This has been fixed. Loading a Template using the REST API produced an error when a request accepted the mimetype “application/xml” for the response. This has been fixed. Creating a copy of an image immediately after cropping would fail without an error message. This has been fixed. When objects were moved between folders, pages containing automatic overviews were not always dirted. This has been fixed now. Aloha Editor gcn-plugin: When an editable was configured to show no insert buttons (empty array), the arena that contains the buttons normally was still shown. This has been fixed. Aloha Editor gcn-plugin: Since the bugfix for SUP-2365, the editable configuration for the insert-tag buttons didn‘t work correctly anymore. This has been fixed. Image Manipulation: replaced a confusing warning when saving auto-resized images with a clearer info message. Fixed a GenticsImageStore bug which caused resizing operations to fail due to a broken dependency of http-client. This also affected the image manipulation tool. The bug affected all GCN versions that were released after 17.02.2016. Aloha Editor gcn-plugin: Inserting new tags didn‘t work anymore because the construct property mayBeSubTag got renamed in the previous bugfix for SUP-2429 but wasn‘t renamed in the gcn-plugin. This has been fixed. The sidebar pannels of the GCN FileLink plugin now look more like their counterparts in the link plugin. When Drag & Drop was disabled and several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in nested editables, the edit and delete icons could be inactive. This has been fixed. The Java REST API client didn‘t correctly define the Maven dependency for jackson-jaxrs. That‘s why this dependency had to be defined manually before. This has been fixed now. Fixed a null pointer exception that sometimes occured when deleting a whole node with templates. Java rest client: Fixed the jackson object mapper throwing a parse error when calling the rest method “construct.list“. In order to fix this the method “Construct.getMayBeSubTag“ has been renamed to “Construct.getMayBeSubtag”. Rest API: Passing global object IDs in the new UUID format didn‘t work. This has been fixed. Installation guides: Changed the text about trigger deletion to be more clear on when it needs to be done and added the — max_allowed_packet option to all mysqldump calls. When editing a page, it was possible to insert new tags inside links. This corrupted the link when saving the page. Inserting tags inside links is not possible anymore now. An error was logged when rendering a velocity part that resolved a “Select (single)”-part where nothing was selected. This has been fixed. Node id and folder id were missing in the php session when editing object properties. This has been fixed. When a new tag was inserted into a page using Aloha Editor and then the user navigated away from the page (without saving first), the page was not saved and the user did not get the notification about unsaved changes in the page. This has been fixed now. The user will get a notification about unsaved changes in such cases. If there are two consecutive tables in an editable, the draghandle of the second table could overlap cells from the first table. This has been fixed. When using the GCN filelink plugin the filelink tag was not removed, when the link was changed to an external URL. This has been fixed. The background job for cleaning old systemsessions could cause deadlocks in the database, which caused errors while users tried to log in into the backend. Those deadlocks have been fixed now. When using the GCN JS API to create a tag in a page, the information about the pages tags was not always properly updated (e.g. when copying a tag containing nested tags). This has been fixed. Fixed a bug with siteminder datasources, where the reading of the datasource values didn‘t work, when the publish_cache feature is activated. The version difference view didn‘t correctly work for HTML pages. This has been fixed. After editing the page properties and saving the changes, the page was not unlocked. This has been fixed. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the edit and delete icons could be inactive. This has been fixed. When publishing images/files into a contentrepository and having the attribute binarycontent set to be a filesystem attribute, in some rare cases it could happen, that the attribute contained old data. This has been fixed now. Optional Manual Change For copying Pages with the REST API you can now set multiple SourcePage Ids in the PageCopyRequest When the publish process was interrupted while synchronizing deleted objects with content repositories, the publish process did not stop, but just skipped over to the next step (publishing pages). This has been fixed now, when the publish process is interrupted in that state, it will stop as soon as possible. When inserting a file link, with the FileLink plugin the freshly inserted link was not visible for editing. This has been fixed. When pages were published using the time management (“publish at”), and the publish process needed to create a version, this new version did not have an editor set. This has been changed now, so that the user who last edited the page will be set as editor of the page version. The systemsession table was not cleaned regularly from old session data, which could cause the table to grow too big. This has been fixed now. Optional Manual Change The FileLink plugin did not treat images as files. If an image was selected, a normal link to that image was created. This has been fixed now, so that also images will be treated as files. In inbox messages the links to pages in multichannel nodes where not resolved correctly. The link would always point to the page in the channel the user last worked in. This has been fixed: links to pages in messages will now always open the page in the channel, where the page can be edited without localizing it. Fixed the tree frame becoming smaller each time it is loaded in Internet Explorer. Also fixed some Javascript errors in the tree. When clicking the “Create copy“ button when editing an image, the button label changed to “Duplicate”. This has been fixed, so that it stays the same. The preview tooltip in the repository browser has been moved, so that it will no longer overlap with nearby filenames. When several occurrences of the same tag (that is with the same tag ID, not just the same tag type) were present in a page, the Aloha editor would only convert the first one into an aloha-block. This behavior has been changed, so that every occurrence of a tag will become a block and get edit and delete buttons. When linking/unlinking a single template from folders, where the user does not have permission to link the template to a folder where the template is already link, the user would always get an error message stating the missing permission. However, linking/unlinking the template to/from folders where the user has the permission still worked as expected. This issue has been fixed now, so that the unnecessary message will not be shown any more. The guides on using meta attributes were updated to include a warning about using the Node-Style syntax in templates containing “<” characters. When deleting tags in a page the page status was not updated to “modified”. This has been fixed. The maintenance details in the administration menu listed pages which were to be taken offline as pages to be published. This has been fixed. When opening the object properties of a file and then navigating to the properties using the link in the assistent frame, the dialog possibly showed properties of another file. When clicking “Cancel” from the properties dialog, the list of images was shown instead of the list of files. Both issues have been fixed now. Pages with special regular expression characters in their names (or filenames) could not be saved sometimes. This has been fixed. Some object attributes that should be displayed in the Aloha editor sidebar where missing in certain renditions of the GCN link browser, so the displayed information was not updated properly. This has been fixed. When the list of object properties of an object is sorted by name, the list will not be grouped by object categories. It is now possible to restore the original grouped display by repeatedly clicking on the column header. Each click on the column header will change the sorting state between # Sorted in ascending order # Sorted in descending order # Grouped by category Fixed the error “Error while getting timestamp of last publish process” that can happen when the DirtQueue worker runs the publish queue migration. An internal error while exporting objects due to missing translatable names has been fixed. When the tagfill dialog of an overview tag is opened, where the options to select type and source of the listed objects was restricted, so that the current data in the tag is not valid any more, the tagfill dialog will be opened at step 1 and the list of currently selected objects will be cleared. When publishing a page with more than 16MB of content into the filesystem using multithreaded publishing, the page was not written into the filesystem, but no error was logged and the publish run did not fail. This has been changed now, so that the publish run will fail with an error like When importing bundles using an export URL, the global ID of the bundle to import was not generated correctly in response to the request of the download URL. This caused the check whether the bundle was already installed on the system to fail. This has been fixed now. It is important to note, that the system providing the export has to be updated for this fix. When the feature When using the publish_cache, rendering a page in a channel in publish mode using the REST API failed with an Internal Error. This has been fixed now. The gcn-linkbrowser plugin would filter out attributes from repository elements, even if the link plugin was configured to display them in the sidebar. This has been fixed. Under special circumstances, an import could fail with an Internal Error, due to a NullPointerException in UnlockContentTransactional.onDBCommit (while commiting the transaction). This has been fixed now. The missing REST API methods Resolving properties of tag parts during rendering a velocity part could fail without any exception logged. This has been fixed now. When working with the CMS backend, some unnecessary data was permanently stored in the user session. This could lead to problems, if the session grew too big. The behaviour has been changed now, so that some session data will be cleared from the session if the user logs out. The following tagmap entries are no longer reserved and can be modified or deleted: No newlines were allowed in the system maintenance message. This has been fixed. Updating the tomcat to a newer version sometimes did not work due to an error in the version number comparison. With this update, the tomcat version will be updated to the last recent version, if this failed to happen during previous updates due to this bug. This has been fixed now. When applying this update, the packaged Tomcat will be updated to version 7.0.65 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-x.x.x) after updating. Sometimes when closing a page that was opened in edit mode using Aloha Editor without any changes, Aloha Editor incorrectly detected a content change. This has been fixed now. For ContentRepositories that have attributes like e.g. the content of pages optimized, the ContentRepository browser would always display the content when querying the Contentmap, even if the checkbox labelled “Also display large contents.” was not checked. The HTML tags in the content were not escaped, which caused HTML in the content to be interpreted. Both issues have been fixed now. The GCN integration plugin for the Aloha editor used the CSS class When using the Java Rest Client to update pages, an error occurred, unless the mediatype of the posted entity was explicitly forced to MediaType.APPLICATION_JSON_TYPE. The error has been fixed now. However, forcing the mediatype to MediaType.APPLICATION_JSON_TYPE is recommended nevertheless. The documentation of the REST API Java Client now contains examples for handling binary data of files. Fixed two occurences of a wrong proxy prefix for Gentics-Imagestore-URLs in frontend editing. This fixes two errors when doing Image Manipulation with frontend editing: When opening a page from the queue, the related links were missing. They have been added now. In some cases, when maintenance mode was active users could not log in anymore. Also the maintenance banner would cover up the login fields preventing clicks on the login form. These issues have been fixed. When objects contained in an import were deleted, viewing the list of imported objects could lead to an SGB. The same error could happen when trying to delete the import. Those issues have been fixed now. The recursive search for files or images did not find files/images in subfolders of folders, where the user did not have permission to view files/images. This also affected the wastebin (deleted files/images were not shown in the wastebin if the user did not have permission to view files/images in one of the superfolders). This has been fixed now. When using multichanneling the usage overview would not list some objects in other channel structures. Some fields for REST API requests were not documented, this has been fixed. When taking pages offline or deleting them, the notification about invalidated links would sometimes display the wrong path when using multichanneling. This has been fixed. The Sometimes, deleting an import did not work and caused an SGB. This has been fixed now. When saving pages containing links in editables with Aloha Editor, links to internal pages, that are incorrectly rendered as external links will now also be transformed to internal links, if the URL does not start with http:// but directly with /CNPortletapp. The internal handling of PreparedStatements used an unnecessary large amount of memory in long running transaction (like an import), which could lead to performance problems and even OutOfMemory errors. This has been fixed now. When configuring custom columns for the repository browser, they were always made sortable, even if “sortable” was set to false. This has been fixed now. Sometimes an error during a publish run did not cause a rollback of the current transaction (which could in turn cause subsequent publish runs to stall indefinitely). This has been fixed. The possible values for the “sortby” query parameter has been documented in the REST API documentation for methods that return sorted lists of elements. Pages containing tags that have values referencing a part of the construct which no longer exists could not be saved any more. This has been fixed now, such data inconsistencies will be cleaned automatically while saving. When using login via SSO, sometimes user session were completely reset between logins. Custom settings like the current content language, the paging or open folders in the tree were lost in such cases. This has been fixed now. When an editor entered more than 255 characters into the description field for pages, folders or files, this either caused an SGB or superfluous characters were silently removed (depending on the database configuration). This has been changed now, so that the user will get a descriptive error message. When a page is modified because the tagtype of a template tag (editable in pages) was changed, the editor and edate were changed, if the page was also missing some editable tags from the template. This has been fixed now. The default values of the variables “langvars“ and “pagevars“ in the PageAPI of the GCN Javascript API were wrongly documented as “false”. This has been corrected. Links could be created by pressing the insert link buttons, or by inserting a magic link tag from the insert tag menu. The later method was not intended, so the link tag is no longer shown in the insert menu. When the feature Fixed an internal server error (white page) when administrating users in the GCN user management. Fixed some issues with activated maintenance mode: Fixed the feature “move_perm_with_edit” not being respected anymore since 5.19.0, when moving a file. Also fixed an error message printing the wrong source folder, when the user has insufficient permissions to move an object in the source folder. Fixed a bug where Aloha Editor blocks (i.e. links) would be removed when saving the page, when a tag with the same name existed previously, but was removed by the editor. This only happened when the the page was not reloaded after saving. This can happen with Frontend editing and the Real editor mode. Fixed the approval of page publish requests not always working for pages in channels. The error message “Page not found” was displayed. The memory consumption for publishing pages that contain sorted overviews over pages when using publish cache has been reduced. The documentation of the feature Publish Cache now contains a note about when the Publish Cache needs to be cleared and how this can be done. When using the publish cache and a page was republished with modified content, the page variants of the page were also republished, but the publish cache of the page variants were not cleared. As a result, the page variants were republished with their old content. This has been fixed now. Creating a page could fail while making the proposed filename unique if too many other pages with similar filenames exist. This has been fixed now. Users with language specific edit permissions (given from roles) could see some actions in the menu for page lists, which they were not allowed to perform. Clicking on one of those menu items resulted in an error. This has been fixed now. When updating Gentics Content.Node to a newer version, the progress display didn‘t work correctly sometimes. When using the feature publish_cache and only changing an object property of a page (without changing or manually republishing the page itself), the page was republished with the old object property value. This has been fixed now. When dirting pages using the maintenance dialog, the publish cache of the dirted pages were not renewed. This could cause pages to be published with old content. This has been fixed now. The automatic tomcat update failed on RHEL 5 because this system does not support the parameter “-V” of the sort command. This has been fixed. When deleting a folder containing objects, it could happen that the following publish process failed with an “InconsistentDataException” while checking the dirted objects, which has been fixed now. When using the publish cache publishing pages with big page overviews could cause OutOfMemory errors. This has been fixed now. When publishing pages - using the publish cache - with tags where the Tagtype has been deleted, an error message was printed to the log file. This error has been removed. Fixed error when reading the XNL Configuration. This bug has been introduced in version 5.17.0. It is now possible to import objects from CMS versions >= 5.19.3 to CMS versions >= 5.18.44 although the format of global IDs is different. The REST API documentation incorrectly statet, that the nodeId for the call The Admin Info on the start screen of the CMS backend probably showed incorrect number of remaining objects during a publish process, which has been corrected now. When a node was deleted, the entries in the publish table for pages of that node were left behind. Such entries will now be removed at the start of every publish process. When using the feature publish_cache, the publish process used too much memory which probably caused OutOfMemory errors. This has been fixed now. When importing a new Node containing an object with an overview, where the root folder of the new Node was selected, a NullPointerException could occur, which has been fixed now. When using Internet Explorer, the page would scroll to the top of the currently active editable when closing the tagfill dialog. This has been fixed now. When publishing pages with tags where the Tagtype has been deleted, an error message was printed to the log file. This error has been removed. Fixed pages being rendered with the wrong DOCTYPE sometimes when comparing 2 page versions and the page does not define a HTML 4 Doctype (but HTML 5 for example). Some internal Locks have been made less restrictive to avoid unnecessary locking of threads. When editing links with Aloha Editor and entering data containing special URL characters (like ‘#‘) the resulting query sent to the server was incorrect. Especially when the character ‘#‘ was used, the resulting query was an unbounded recursive search for all pages, which could lead to performance problems on the server and timeout errors in the client. This has been fixed now. When applying this update, the packaged Tomcat will be updated to version 7.0.63 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. Added documentation in the faq-section for the correct start order of mysql, apache and tomcat When using Internet Explorer to insert tags into editables with a visible scrollbar, the page was scrolled to the top of the editable. This has been fixed now. When inserting tags in tables, the delete button was missing. Also tags with script elements, could be missing all their edit buttons. These issues have been fixed. When inserting inline tag elements, sometimes superfluous wrapper tags where inserted before and after the tag. This has been fixed. When using instant publishing and publish handlers, the publish handlers were not called for deleted objects are pages that were taken offline. This has been fixed now. When a folder structure is deleted, in some circumstances, templates that would neither be linked nor used any more would not be deleted but remained in the database. This has been fixed now. When a language variant of a page with restricted inheritance was created, the new language variant did not have the same inheritance restrictions set. This has been fixed now. The update of the Java libraries while Tomcat is still running could cause errors (though Tomcat would start again cleanly after the update). When the CMS was in maintenance mode users could still login via SSO. The corresponding check has been added to the SSO login, to ensure that only the user who activated maintenance mode can access the CMS backend. When using the feature publish_cache, the property ttype for pages would resolve to The log entries for changing the inheritance of objects did not show the correct action in the log view, which has been fixed now. The log entries for start and end of the publish process did not show the correct action in the log view, which has been fixed now. When editing a page with the Aloha editor, the cursor would disappear in some browsers after inserting an inline tag, which prevented further editing. This has been fixed. Manual Change On systems running PHP Version 5.3.9 or higher, there is a new configuration option max_input_vars which should be set to a higher number. This setting limits the number of input variables, that can be posted to the server. The default setting (1000) prevents e.g. successful linking of templates to folders, if the folder tree shows more than 500 folders. We therefore recommend to raise the value of max_input_vars to e.g. 10000 in the file gtx_gcn_custom.ini. You have to restart the apache webserver after that. The path to this file varies between distributions: Sometimes, handling dependencies caused errors due to stale database connections. This has been fixed now. In cases where the publish process is interrupted (cancelled) while waiting for a semaphore to write into a contentrepository, additional information about the thread which last acquired that semaphore will now be logged. When exporting objects with translatable names (like tagtypes or object property definitions), the export file could contain an inconsistency due to missing translations. This subsequently caused an “Internal Error” during import. This issue has been fixed. Saving of pages that contain lot‘s of new links may take some time. During this time, the editor has no indication that the new links are currently processed and prepared to be saved. The behaviour has been changed now, so that a progress information is shown during page save and preparing new links to be saved is done much more efficient. The columns for storing dirt analysis information in the backend database sometimes where too small and have been extended now. Fixed possible javascript error on the CMS start page. For parts of type “File (Upload)”, the button to upload a new file was missing and has been readded. Links to an anchor on the current page will be made absolute by the browser when they are pasted or moved within the same page. Those absolute URLs will now be fixed during saving. Sometimes a user who had all the required privileges could still get an error about insufficient permissions when trying to move a file. This has been fixed. When configuring a fixed pageSize for the repository browser, paging did not work as expected and has been fixed now. Saving values with a large number of characters could result in an error. This has been fixed. In rare cases a NullPointerException could occur when uploading a file. This happened if the language id in the session of the user was invalid. This has been fixed. When saving page properties with an empty filename, the filename was not automatically generated from the (possibly changed) page name. This has been fixed. A potential security issue, that was introduced with versions 5.18.31 and 5.19.25 has been fixed. When saving pages with Aloha Editor, that contain links with empty HTML tags in them (like a When assigning permissions to groups, sometimes certain checkboxes were not filled correctly in some browsers. This has been fixed. When a user with permissions restricted to channels tried to take a page offline over the REST API, the permission check was not done channel specific, which has been fixed now. Automatic inbox messages that are generated when When taking a page offline over the REST API, other pages will be checked for invalid links now. Changing an object property now creates an entry in the administration logs. When a page was copied in a multichannelling environment, the copy was automatically disinherited from the channels, where the original page was localized. This has been fixed now. The copy will now have the same inheritance settings as the original page (if possible) and will only be further restricted, if it is copied into a folder with further restrictions. The initial timespan of log entries to be shown in the “Logs” view has been reduced from one hour to five minutes. This reduces the number of initially shown entries, especially if the user has no paging activated. Dropped Support for Redhat Enterprise Linux (RHEL) Version 5.x because the default PHP Version (5.1) is no longer supported. See the updated compatibility list When using SiteMinder for SSO, the logged in user was always “anonymous” (without any permissions). This has been fixed now. When users where granted permission to view files/images through roles, these permissions were not considered during a recursive search for files/images (in the subfolders). This has been fixed now. For implementations using their own jQuery Version, saving the page with Aloha Editor failed with a javascript error, when the page contained at least one anchor tag. This has been fixed now. When users with publish permission restricted to channels tried to publish pages out of the publish queue, this sometimes failed due to an incorrect permission check. This has been fixed now. Copying of pages in channels did not work due to an incorrect permission check, if the user was restricted to that channel. This has been fixed now. When a page contained an anchor tag without href attribute, an error occurred while saving the page with Aloha Editor. This has been fixed now. Enhanced the error handling of PHP errors. Catchable PHP errors will be also logged to the Gentics Content.Node error log now. Fixed a syntax error in the gcn-fileupload plugin that caused a JavaScript error with Internet Explorer in IE7-Mode. When the publish process failed during handling of time management, the process was marked as “OK” in the scheduler. This has been fixed now. When editing a page with Aloha Editor and changing an internal link to point to an external target, this change sometimes was not persisted when saving. This has been fixed now. When creating tables or tags at the very beginning or end of an editable, an empty paragraph will also be added (which is automatically removed if not needed), so that the cursor can be set before or after the new tag or table. Before this fix, it was necessary to deactivate and activate the editable to get the empty paragraphs. When using an archive workflow to move deleted pages into an archive folder, and deleting a language variant of a page, the moved language variant was not completely detached from the other language variants, if the name of the moved page needed to be changed, because another page with that name already existed in the archive folder. Also the moved page was still locked after the operation. Both issues have been fixed now. When the process of changing the inheritance of folder structures failed with an unexpected error, it could happen that an inconsistent state was left behind. In such cases, the publish process could subsequently fail due to the data inconsistency. The error behaviour of changing the inheritance has been changed. In the case of an error, all changes will be undone and the previous (consistent) state will be restored. When a page is opened for editing with Aloha Editor, lot‘s of redundant AJAX calls to the REST API were made to initialize the Editor. The number of calls has been reduced now, which will minimize the overall loading time, especially for pages that contain many editables and tags. Image manipulation 2: When used with a custom context path, the image would disappear from the editor after resize or crop operations. This was due to a broken link, which has been fixed now. If a page was opened for editing and the editing operation was then cancelled, the page would lose its disinheriting information. This could lead to publishing problems due to inheriting inconsistencies. This has been fixed now. When creating a new content tag that is named automatically, a name would be selected for it, although there is already a template tag by the same name, that is NOT editable in page. This name would typically be something like your_custom_tag1. This may cause confusion or even prevent a page from being saved in the backend. The new behavior is to only use automatically generated tag names, that are not used by any templatetags associated with any of the pagevariants using the content to be edited. Collisions may still occur if localizations of the template use a different set of templatetag names and there are no corresponding page localizations. When applying this update, the packaged Tomcat will be updated to version 7.0.61 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.54) after updating. Added documentation for changing the page title of the CMS Backend It is now possible to view failed dirt events in the maintenance dialog. Failed dirt events can be removed from the dirtqueue or can be re-scheduled. The Gentics Content.Node Javascript API has been changed, so that TagAPI objects will no longer be cached. The _data of TagAPI objects always reference the tag data in their parent (e.g. a PageAPI object), so there is no need to cache the TagAPI object as well. This fixes problems caused by the PageAPI object being refreshed in the cache, while the TagAPI objects were not refreshed, which caused them to no longer reference the tag data of the PageAPI object. The result was that changes in the TagAPI object were no longer reflected in the PageAPI object and saving the page would unintentionally restore old tag values. When the backend apache uses the module modunique_id_ this can lead to unexpected behaviour like cms dialogues that cannot be openend, until the user‘s session is reset. This has been fixed now. When a page is modified because the tagtype of a template tag (editable in pages) was changed, this will no longer change the editor or edate of the page. Also if the page is republished in this process, the publisher and pdate will not change. When editing object properties of a template or folder, the actions to make the object properties editable in pages where missing. They have been added again. When changing the language of a page in a node that does not have the original page language activated, replacing of the language code in the filename did not work. The new language code was just appended to the original one. This has been changed now: When changing the language of a page, the language code in the filename will now be replaced with the new one, even if the language is not activated in the node. The attribute name data-gcn-constructname, that exists for editing pages with the aloha editor was renamed to data-gcn-i18n-constructname. It contains the internationalized tagtype name of a tag. Make the shrinktofit option for the jqGrid (the object list) in the repository browser configurable. This option can be used to make the repository browsers width bigger on smaller screens while keeping the benefits of the dynamic resizing of the column widths. Links to internal pages or files that were entered with their internal URL will now correctly be transformed to tags pointing to the internal objects, instead of saving the URLs. This fixes incorrect saving of links with their internal URLs. Some icons have been added to the “Page” menu. Fixed nested “intag“ object properties not being copied to subfolders when using the backend “Apply to subfolders“ or the Rest API “tagsToSubfolders” option. When creating nested object properties, the inner tag was only visible, if it was filled at least once, even if the tagtype had the option “auto-enabled” switched on. This has been fixed now. However, this will only affect new created nested object properties. Already existing object properties, that are not visible need to be filled once. When saving a page using the REST API, the status will always be set to 0 (being edited), regardless of the status flag in the posted page object. The names of custom columns of the repository browser can now be translated into the CMS language. gcnfileupload-plugin: The upload form is now reset before every use. gcnfileupload-plugin: Added translations for several hardcoded german UI-elements. Manual Change The implementation of the “Aloha Link” Tagtype needs to be updated. When linking to images (using the Aloha Link Plugin), the display of the link target in the toolbar was incorrect. The internal URL to the image was shown instead of the filename. The fix for this also requires an update of the implementation of the “Aloha Link“ Tagtype (keyword: “gtxalohapagelink”), according to the code in the Aloha Page Link Tag Description. A vulnerability of the GenticsImageStore in the CMS backend has been fixed. The creation of unique filenames during fileupload sometimes failed to distinguish filenames that only were different in case. This has been fixed now. When more than one handler subscribed the channel “tag.rendered”, the behaviour was unexpected: # If all handlers passed a modiied html to the callback only one of the changes was accepted # When saving a page, that contained at least two new links, not all of the links were correctly transformed to tags. The page icon used to display the language in the assistant frame was different for page preview and page properties. Now, for all operations the same icon is used to display the language in the assistant. The permission checks on the publish queue did not consider channel restrictions correctly. Users could see pages in the queue for all channels (but could not view the pages or approve publishing). The permission check in the queue has been fixed now. When users with permissions restricted to channels changed the binary content of channel local files, they received an error message (missing permission), although the file upload worked. This has been fixed now. Content.Repositories using deprecated attribute types will now be marked in the list of Content.Repositories. Also the attributes using deprecated types will be marked in the tagmap editor. Additionally, the Gentics Content.Node Guides now contain a migration guide for changing attribute types in Content.Repositories with minimal downtime of the frontend implementation. When changing the inheritance takes longer than normal (default is 5 seconds), the user will be informed and the process will be continued in the background. When editing a page with aloha editor using an older version of Internet Explorer (like IE9), clicking on menu items with unsaved changes in editables would warn the user twice about unsaved changes. When clicking on a menu item of the “page“ top menu, the page was saved, even if the user approved to leave the page with unsaved changes (twice). The behaviour has been changed now: when clicking on a “page” menu item, the page will be saved before the action is triggered. When clicking on another menu item (navigating away from the edited page), the user will get one notification about leaving the page with unsaved changes. Files that have no mimetype set (e.g. due to an error during the upload), will now be visible in the backend and be marked as “broken”. When closing a tagfill dialog in IE >= 9 no cursor was shown when clicking into another editable. This has been fixed. When using SSO with CAS or JOSSO, the user‘s sessions would be reset on every login. This has been fixed now. The entry “Save” in the related links (in the assistant frame) of the page preview has been removed, because it suggested, that the page had not been saved properly. Users with permissions restricted to channels were not allowed to create local folders in their channels. This has been fixed now. When changing the inheritance of folder structures takes longer (because many objects and/or many channels are affected), this could interfere with a publish process running at the same time. It could happen that the publish process would fail due to a database lock wait timeout. This has been fixed. Copying a page into a channel local folder was not possible and has been fixed. The pageusage count for pages used in pagetags of other pages was always 0 due to an incorrect SQL statement. Additionally, the error “Error while getting usageinfo for pages” was logged in the server‘s log. This has been fixed now. When parts of a construct have to be replaced (i.e. some parts have to be removed and other have to be added) while importing, this could lead to incorrectly filled default values for such constructs. This has been fixed now. When the tag definition of a template was changed and the change was synchronized with the pages, this could lead to database locks if users tried to lock the same pages. This has been fixed now, users trying to lock pages currently changed by the synchronization will get the page in readonly mode. Users with the permission to create pages restricted to channels, could not create pages in those channels, because the permission check was done incorrectly. This has been fixed now. When publishing a node and its channels into the filesystem, and when localizing pages, the former inherited pages were sometimes not correctly removed from the filesystem of the channel. This has been fixed now. Fixed wrong proxy prefix for Gentics-Imagestore-URLs in frontend editing. When fetching an object via the REST API in edit mode, tags that were inactive, but should become active when edited were marked as being “inactive“. When the fetched object was saved back (without any changes), the tags would be set to “inactive“. This has been changed, so that tags in that state will now be marked as being “active”, if the object is fetched in edit mode. In multichannelling environments, it was not possible to create a file in a folder that was inherited in a channel, if the folder was localized in another channel. Also copying of pages in such folders failed. Both issues have been fixed now. In multichannelling environments, it was not possible to create a new page in a localized folder in a channel. This has been fixed now. Previously, when using the language menu while a page is opened, the CMS would under certain circumstances display a page of the wrong language or even an error message. Now, the page is always either displayed in the chosen language, or the language doesn‘t change if the selected language version of the current page does not exist and the user is not allowed to create it. Previously, when clicking pages in the history, the CMS would under certain circumstances not open the intended page, display an error message or in rare cases create a translation. Now, exactly the specified page will be opened, as listed in the history (same language version, same channel). When a page was saved with only changes in the content, the status of the page was not changed to “being edited”. This has been fixed now. When users were restricted to channels, they could not create local folders in their channels due to an incorrect permission check. This has been fixed now. When an editor without publish permission tried to publish a page, all users of parent groups with publish permission were notified, even if the users were restricted to channels and were not allowed to see and publish the page in question. This has been fixed now: The node restriction is now considered when notifying users about pages to be published. Fixed an Internal Error while importing a modified tagtype, if the type of a part in the tagtype had been modified. When editing a page, the tool-tip of a tag now shows the tag keyword and the tagtype name instead of only the tag keyword. Fixed NullPointerException when comparing page versions in a master node with multichanneling. If the user changes the page filename and the new filename has no file extension, the changed filename does not have the markup language extension of the page template after saving the changes. This bug was introduced with this feature release (5.19). This has been fixed, to match the behaviour of previous releases. Sometimes, CSS settings of aloha editor plugins did not overwrite the core aloha editor CSS settings (due to a loading order problem), which could cause indeterministic layout problems. This has been fixed now, the core aloha editor CSS settings will now always be loaded before the plugin CSS settings, in order to allow the plugin CSS settings to overwrite the core settings. When opening a page in preview mode of aloha editor, the history entry created in the assistant frame showed the normal page icon, but would open the page in edit mode. This has been fixed now: only opening a page in edit mode will create a history entry showing the edit icon, that will open the page in edit mode again. Fix property “fullPath” of repository items for correct display in sidebar. When using a workflow to move deleted objects into an “Archive“ node, moving did not work when the user did not have permission to move the object into the “Archive”. This has been fixed now. When the moving is done from a workflow, no permission checks will be done for this operation. A possible NullPointerException during the import has been fixed. When a bundle was imported, the globalid of the bundle was always considered to be an empty string. For this reason, all export files were considered to belong to the same bundle during the import. This has been fixed now. Additionally, an SGB in the display of the import history details has been fixed. CAS: Fixed CAS-services not being accesible via HTTPS by adding a new $CAS_SSO[‘curlOptions‘] option that allows the configuration of CURL SSL. Read the “CAS – Central Authentication Service” page in the documentation for more information. When importing templates that contained tags, where the values had been changed, under special cirvumstances, the new values were not imported correctly. This has been fixed now. Errors that happen while rendering velocity tags will now contain more descriptive information in the server log. The name and ID of the page and tag will be logged now. The documentation of the feature Copy Tags has been enhanced to include configuration settings, that are necessary for the feature to work. The globalprefix stored in the database would not be updated when the license file was changed. This was a regression from 5.19.3. When using the global tagtype migration, an error message was always shown. This has been fixed now. The permissions of object properties are now also respected by the GCN Rest API when loading or saving objects. Permissions: When a group had permissions on an object, and all permission were removed, the permission cache was not refreshed and the group still had the previous permissions. This only happened when all permissions to an object were removed. When editing a page with Aloha Editor and an editable only contained a table, it was not possible to add content before or after the table. This has been fixed now: When the editable is activated, paragraphs will be created as landing areas for the cursor. When editing a page with Aloha Editor, the following editing actions would lead to unexpected behaviour: Following these steps, the tagfill dialog would now be empty (not showing the data entered before). This problem has been fixed now, so that editing pages in the way described above will work as expected. The migration job for globalids to uuids has been made more failsafe. Before the old tables are removed, a final check will be done, whether all data has been migrated completely. Additionally, the migration process will now be done in batches to reduce the memory consumption in the database for every single update statement. It is now possible to change the synchronization mechanism for objects, that need to be removed from a content repository also for non-multichannelling aware contentrepository from the default differential synchronization to a full synchronization. Using the full synchronization is slower than the differential approach but is less error prone. Changed Contentrepository DB connection pool to be more resilient in cases of reset DB Connections. Fixed output of error log message caused by debug output when rendering tags for publishing. The algorithm to check whether a new page version must be created and to create the page version used many sql statements and therefore was inefficient. This algorithm has been changed now to be more efficient, especially when no page version must be created. This will affect actions like: The process of saving a page has been optimized to avoid unnecessary checks, if only content, but no metadata was changed. Fixed newly introduced error with bugfix SUP-434 in the previous hotfix. The overview wizard could start with page 1 even if the user already made all the selections on page 1. Fixed object properties not being deleted, when passing their name in the “delete” list of the PageResource.save Rest API method. When copying pages took longer than the configured timeout (due to high load on the server, number of copied pages or overall system performance), the user got an SGB, which suggested that copying failed, which was not the case. This has been fixed now: When copying pages takes longer than 5 seconds, the user will get a message, that the process will be continued in the background. Once copying is done, the user will receive an instant message. Additionally, when copying using the REST API, it is now possible to specify the maximum “foreground” time in milliseconds. The default value is 0, which will block the call until copying is done (which is the old behaviour). Overview tags in pages: When editing new overview tags in pages the wizard started wrongly with page 2 when no selection was made for the object type or the selection type in page 1. This has been fixed. The wizard will now start correctly with page one if any selection is possible and hasn‘t been made. When defining the tags in a template, it is now possible to save an updated list of tags without synchronizing the pages (by clicking the ‘Apply‘ button) or to save and synchronize the pages (by clicking the new ‘Apply and synchronize pages‘ button). Additionally, if errors occur (e.g. because some pages are currently locked by other users), the whole synchronization process does not fail (and has to be repeated), but all pages, that can be synchronized will be synchronized. If the action is triggered again (by clicking ‘Apply and synchronize pages‘ without actually changing the tag definitions, the remaining pages will be synchronized. Additionally, there is now an additional view (“Tagstate” via the template‘s top menu) that will show, how many pages are in sync or out of sync with the template regarding the editable tag definitions. REST-API: When copying a contenttag, using page/newtag, the operation would fail for some content tags. When editing a page using Aloha Editor with Internet Explorer, and adding new links to the page, the click on “Save” in the assistant frame showed a message, informing the user that he was about to leave the page with unsaved changes. This has been fixed now. Additionally, when saving a page that contained new links, some additional AJAX calls to the backend were done (in the background), which caused saving to be slower than necessary. Those AJAX calls have been reduced to the necessary minimum. Bug in GenticsImageStore Cache: When replacing a resized image in a page that is embedded with a GIS URL, the original resized image was still visible. This has been fixed. Some problems with copying or importing templates in the backend have been fixed: This update will also correct incorrectly bound templates in the database. When saving a page that contained a tag using one of the list parts (List, List (unordered), List (ordered)) the entries of the list part were merged into a single entry. The same happened, when migrating such a page with the tagtype migration, if at least one post processor was used. This has been fixed now. When custom columns were configured for the gcn-linkbrowser plugin, the display of thumbnails in the repository browser did not work any more. This has been fixed. It is now possible to grant/revoke permission for viewing and setting the inheritance of objects in specific nodes or channels. Initially, the permission flag will be set to all groups, that have permission to view nodes. For images having the mimetype “image/x-png” no thumbnails were generated in the backend, which has been fixed now. Connections from the database connection pool are now tested before being used. Comparing Page Versions did not work correctly with Pages in localized Folders. This has been fixed. Copying of nodes was broken due to some classes, that were removed but still referenced in an internal configuration. This has been fixed now. Copying a tagmap entry between contentrepositories would fail unconditionally. Fixed a NullpointerException when importing a page that could occur under rare circumstances. Multiple bugs fixed in page publishing: Fixed accidentally cutting off a filename extension when uploading a new file. If the user changes the filename when uploading a new file in the CMS and the new filename has no filename extension, then the original filename extension of the input file is attached to the new filename. In some cases an error could occur when accessing the CMS directly after an update has been applied. The error occurred because some mandatory tasks for i18n support were not completed. When a tagtype contains an velocity tagpart that is editable it could lead to side effects. Improved the documentation, so that making a velocity tagpart editable is now discouraged, as it is also not supported. The failure behaviour and logging of the publish process has been improved, in cases where committing the content repository transactions at the end of the publish process fails. When the localized copy of a page was taken offline, instant publishing would replace the page with the inherited page, instead of completely removing it from the content repository. Only the next regular publish run would correct this and remove the page from the content repository. This has been fixed now, so that instant publishing will correctly remove the page. Sometimes, the tree shown to select the target folder for copying pages was rendered incompletely. This has been fixed now. Improved logging output in context of an inconsistency in multichanneling when a localized object does not have a master object. Implemented a workaround for the Internet Explorer 10 and 11 frame rendering issues with different document modes. GCN will force a redraw of content frames from now on in order to prevent issues with empty pages. Also fixed the upper page frame in the “translate to” page sometimes being invisible or too small. When a contentrepository was imported, the foreignlink attribute rule of an already existing tagmap entry would not be overwritten, if it was changed. This has been fixed now. Creating a page variant in multichannelling environments with localized language versions would sometimes fail or introduce consistency problems to the newly created page variant. Fixed documentation of AuthenticationResource to describe the proper parameters for the validate method. When multiple requests to translate a given page into a specific language were sent at the same time (or in a way that a new request was sent before the previous request returned), it was possible that multiple language variants in the requested language were created for the same page. Only one of the language variants was visible in the backend, but possibly both were published. This has been fixed now. Translating pages will now be synchronized (per page), so that multiple parallel requests will only create a single language variant, which will be returned by all of those requests. Fixed possible NPE when checking data in contentrepositories Warning: potential downtime! Deleting one or more files caused an error if a workflow is activated that moves deleted files to another folder. This has been fixed. When moving folder structures within master nodes of multichannelling environments, all channel local objects in that structure were pushed to the master node as well. This has been changed now. Objects within moved folder structures will now only be moved between channels, if this is necessary to maintain channel integrity. Moving files/images across channel trees would always return an error message. REST-API: Removed unused “folder” field from FolderCreateRequest. This prevents a JsonMappingException in the Java REST client. The generation and internal storage of global IDs in the backend database has been changed: This change will be done during the system startup after this update and might take some time (depending on the size of the database and the overall system performance). However, there are some drawbacks: Fixed potential inheritance restriction consistency problem when moving pages between channels. Recursively setting permissions or setting object properties might take longer and run into a timeout. In such cases, it was not perfectly clear to the user, what happened and if the requested action was successfully performed. The processes have been changed now, so that if setting the permissions or the object properties recursively takes longer than some seconds, it will be sent to the background. The user will get a message that the process is continued in the background and will get an instant message when the process is completed. SVG images could not be exchanged in the image properties page. This has been fixed. Fixed possible NPE when saving pages containing empty overviews Running the purgeversions could possibly remove a page version, even if the content was still used by another page variant, if the page variants were not in sync. This could lead to pages being published completely empty. This has been fixed now. If any pages having page variants lack their published page version and are therefore published completely empty, they must be published again to correct the page version. When an object is not changed during an import, because the local copy is identical to the imported version, the import details list will now show ‘unchanged‘ instead of ‘ignored‘ as import action. Additionally, the import details list will now also show conflicts, that existed during the import and the individual conflict setting for the imported objects. Optional Manual Change Java 8 Runtime Support Java 8 JRE support for Gentics Content.Node 5.17.x and newer was added. You can update the used Java version to Server JRE 8u25 64 bit by downloading the ‘Server JRE 8‘ package and extracting it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the Apache Tomcat server once you finished this step using the /Node/bin/nodectl script. Corrected paths for cleaning up unneccesary directories when performing the RHEL GCN package migration Fixed accidentally cutting off a filename extension. If a filename is changed in the CMS in the file properties and the new filename has no filename extension, then the previous filename extension (if any) is attached to the new filename. Changing a datasource with an import failed to dirt dependent objects. This has been fixed now. If the import changes entries of a datasource, dependent objects will be dirted. The memory consumption of the timetrigger script (used for time based workflows) has been reduced. Fixed curl printing debug output to error.log when the PHP curl extension is enabled. The assignment of languages to nodes was imported with the language, but not with the node: The behaviour has been changed now, so that the language assignment is changed, when the node is imported. Aloha Editor Change Summary The import2 and export2 features are now enabled by default. The older import/export implementation is no longer supported and can‘t be used any longer. Manual Change The old Live Editor has been removed and can‘t be used anymore for editing pages. We recommend migrating your projects to Aloha Editor, otherwise inline-editing will not be possible anymore. Details about the editor migration can be found in the guides. Remove the following setting in your node.main.conf: $FEATURE[“superedit_page”] = true; Image support enhancement: In older versions, only files that are supported by the Gentics Image Store were handled as images and put into the list of images in folders. This had the downside that their mimetype was set to “application/octet-stream“. This caused problems with some image types likes .svg because the browser couldn‘t display the image because of the wrong mimetype. Now all images that have a mimetype starting with “image/” will also be listed as images by GCN. Additional a notice will be displayed to the users when they try to select an image in the repository browser (image tags) that is maybe not supported by all browsers. When updating to this version, files that have already been uploaded in older versions will NOT be changed. It is now possible to configure the default value for the IE Standards mode for all pages in the CMS. The X-UA-Compatible Header, that is added to every page per default, can now be set to a different value than “IE=7“. For configuration see the description of the feature “X-UA-Compatible Header Content” in the guides. Added a new default blue Gentics stream for the login mask and the top header background. The feature “multichannelling” has been enhanced, so that the inheritance of objects can now be configured. Please consult the Gentics Infoportal for further details. The Migration Tool now allows global tag type migrations that affect all objects of the selected types. See the Gentics Content.Node Guides for details. When migrating tags for a single page and selecting the option Apply this migration to ALL pages using this page's template. there is now a new option Apply this migration to ALL nodes. If the new option is selected, all pages of all nodes will be migrated, not only the pages in the same node as the original page. The REST API has been extended: The new command line tool GlobalIdSync allows synchronization of global IDs of tagtypes, datasources and object property definitions between systems in order to be able to import those objects from one system to the other without creating unwanted duplicates. Fixed the WebDAV fileuploader saving files with the wrong mimetype. Example: “image/png; charset=binary“ instead of “image/png”. The mimetypes of already uploaded files will be corrected in the database when updating. The default values of the variables “langvars“ and “pagevars“ in the PageAPI of the GCN Javascript API were wrongly documented as “false”. This has been corrected. Links could be created by pressing the insert link buttons, or by inserting a magic link tag from the insert tag menu. The later method was not intended, so the link tag is no longer shown in the insert menu. When the feature Fixed an internal server error (white page) when administrating users in the GCN user management. Fixed some issues with activated maintenance mode: Fixed a bug where Aloha Editor blocks (i.e. links) would be removed when saving the page, when a tag with the same name existed previously, but was removed by the editor. This only happened when the the page was not reloaded after saving. This can happen with Frontend editing and the Real editor mode. Fixed the approval of page publish requests not always working for pages in channels. The error message “Page not found” was displayed. The memory consumption for publishing pages that contain sorted overviews over pages when using publish cache has been reduced. The documentation of the feature Publish Cache now contains a note about when the Publish Cache needs to be cleared and how this can be done. When using the publish cache and a page was republished with modified content, the page variants of the page were also republished, but the publish cache of the page variants were not cleared. As a result, the page variants were republished with their old content. This has been fixed now. Users with language specific edit permissions (given from roles) could see some actions in the menu for page lists, which they were not allowed to perform. Clicking on one of those menu items resulted in an error. This has been fixed now. When updating Gentics Content.Node to a newer version, the progress display didn‘t work correctly sometimes. When using the feature publish_cache and only changing an object property of a page (without changing or manually republishing the page itself), the page was republished with the old object property value. This has been fixed now. When dirting pages using the maintenance dialog, the publish cache of the dirted pages were not renewed. This could cause pages to be published with old content. This has been fixed now. The automatic tomcat update failed on RHEL 5 because this system does not support the parameter “-V” of the sort command. This has been fixed. When deleting a folder containing objects, it could happen that the following publish process failed with an “InconsistentDataException” while checking the dirted objects, which has been fixed now. When using the publish cache publishing pages with big page overviews could cause OutOfMemory errors. This has been fixed now. When publishing pages - using the publish cache - with tags where the Tagtype has been deleted, an error message was printed to the log file. This error has been removed. Fixed error when reading the XNL Configuration. This bug has been introduced in version 5.17.0. It is now possible to import objects from CMS versions >= 5.19.3 to CMS versions >= 5.18.44 although the format of global IDs is different. The REST API documentation incorrectly statet, that the nodeId for the call The Admin Info on the start screen of the CMS backend probably showed incorrect number of remaining objects during a publish process, which has been corrected now. When a node was deleted, the entries in the publish table for pages of that node were left behind. Such entries will now be removed at the start of every publish process. When using the feature publish_cache, the publish process used too much memory which probably caused OutOfMemory errors. This has been fixed now. When importing a new Node containing an object with an overview, where the root folder of the new Node was selected, a NullPointerException could occur, which has been fixed now. When using Internet Explorer, the page would scroll to the top of the currently active editable when closing the tagfill dialog. This has been fixed now. When publishing pages with tags where the Tagtype has been deleted, an error message was printed to the log file. This error has been removed. Fixed pages being rendered with the wrong DOCTYPE sometimes when comparing 2 page versions and the page does not define a HTML 4 Doctype (but HTML 5 for example). When editing links with Aloha Editor and entering data containing special URL characters (like ‘#‘) the resulting query sent to the server was incorrect. Especially when the character ‘#‘ was used, the resulting query was an unbounded recursive search for all pages, which could lead to performance problems on the server and timeout errors in the client. This has been fixed now. When applying this update, the packaged Tomcat will be updated to version 7.0.63 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.61) after updating. Added documentation in the faq-section for the correct start order of mysql, apache and tomcat When using Internet Explorer to insert tags into editables with a visible scrollbar, the page was scrolled to the top of the editable. This has been fixed now. When inserting tags in tables, the delete button was missing. Also tags with script elements, could be missing all their edit buttons. These issues have been fixed. When inserting inline tag elements, sometimes superfluous wrapper tags where inserted before and after the tag. This has been fixed. When using instant publishing and publish handlers, the publish handlers were not called for deleted objects are pages that were taken offline. This has been fixed now. When a folder structure is deleted, in some circumstances, templates that would neither be linked nor used any more would not be deleted but remained in the database. This has been fixed now. The update of the Java libraries while Tomcat is still running could cause errors (though Tomcat would start again cleanly after the update). When the CMS was in maintenance mode users could still login via SSO. The corresponding check has been added to the SSO login, to ensure that only the user who activated maintenance mode can access the CMS backend. When using the feature publish_cache, the property ttype for pages would resolve to The log entries for start and end of the publish process did not show the correct action in the log view, which has been fixed now. When editing a page with the Aloha editor, the cursor would disappear in some browsers after inserting an inline tag, which prevented further editing. This has been fixed. Manual Change On systems running PHP Version 5.3.9 or higher, there is a new configuration option max_input_vars which should be set to a higher number. This setting limits the number of input variables, that can be posted to the server. The default setting (1000) prevents e.g. successful linking of templates to folders, if the folder tree shows more than 500 folders. We therefore recommend to raise the value of max_input_vars to e.g. 10000 in the file gtx_gcn_custom.ini. You have to restart the apache webserver after that. The path to this file varies between distributions: Sometimes, handling dependencies caused errors due to stale database connections. This has been fixed now. In cases where the publish process is interrupted (cancelled) while waiting for a semaphore to write into a contentrepository, additional information about the thread which last acquired that semaphore will now be logged. When exporting objects with translatable names (like tagtypes or object property definitions), the export file could contain an inconsistency due to missing translations. This subsequently caused an “Internal Error” during import. This issue has been fixed. Saving of pages that contain lot‘s of new links may take some time. During this time, the editor has no indication that the new links are currently processed and prepared to be saved. The behaviour has been changed now, so that a progress information is shown during page save and preparing new links to be saved is done much more efficient. The columns for storing dirt analysis information in the backend database sometimes where too small and have been extended now. Fixed possible javascript error on the CMS start page. For parts of type “File (Upload)”, the button to upload a new file was missing and has been readded. Links to an anchor on the current page will be made absolute by the browser when they are pasted or moved within the same page. Those absolute URLs will now be fixed during saving. When configuring a fixed pageSize for the repository browser, paging did not work as expected and has been fixed now. Saving values with a large number of characters could result in an error. This has been fixed. In rare cases a NullPointerException could occur when uploading a file. This happened if the language id in the session of the user was invalid. This has been fixed. A potential security issue, that was introduced with versions 5.18.31 and 5.19.25 has been fixed. When saving pages with Aloha Editor, that contain links with empty HTML tags in them (like a When assigning permissions to groups, sometimes certain checkboxes were not filled correctly in some browsers. This has been fixed. When a user with permissions restricted to channels tried to take a page offline over the REST API, the permission check was not done channel specific, which has been fixed now. Automatic inbox messages that are generated when When taking a page offline over the REST API, other pages will be checked for invalid links now. Changing an object property now creates an entry in the administration logs. The initial timespan of log entries to be shown in the “Logs” view has been reduced from one hour to five minutes. This reduces the number of initially shown entries, especially if the user has no paging activated. Dropped Support for Redhat Enterprise Linux (RHEL) Version 5.x because the default PHP Version (5.1) is no longer supported. See the updated compatibility list When using SiteMinder for SSO, the logged in user was always “anonymous” (without any permissions). This has been fixed now. When users where granted permission to view files/images through roles, these permissions were not considered during a recursive search for files/images (in the subfolders). This has been fixed now. For implementations using their own jQuery Version, saving the page with Aloha Editor failed with a javascript error, when the page contained at least one anchor tag. This has been fixed now. When users with publish permission restricted to channels tried to publish pages out of the publish queue, this sometimes failed due to an incorrect permission check. This has been fixed now. Copying of pages in channels did not work due to an incorrect permission check, if the user was restricted to that channel. This has been fixed now. When a page contained an anchor tag without href attribute, an error occurred while saving the page with Aloha Editor. This has been fixed now. Enhanced the error handling of PHP errors. Catchable PHP errors will be also logged to the Gentics Content.Node error log now. Fixed a syntax error in the gcn-fileupload plugin that caused a JavaScript error with Internet Explorer in IE7-Mode. When the publish process failed during handling of time management, the process was marked as “OK” in the scheduler. This has been fixed now. When editing a page with Aloha Editor and changing an internal link to point to an external target, this change sometimes was not persisted when saving. This has been fixed now. When creating tables or tags at the very beginning or end of an editable, an empty paragraph will also be added (which is automatically removed if not needed), so that the cursor can be set before or after the new tag or table. Before this fix, it was necessary to deactivate and activate the editable to get the empty paragraphs. When a page is opened for editing with Aloha Editor, lot‘s of redundant AJAX calls to the REST API were made to initialize the Editor. The number of calls has been reduced now, which will minimize the overall loading time, especially for pages that contain many editables and tags. Image manipulation 2: When used with a custom context path, the image would disappear from the editor after resize or crop operations. This was due to a broken link, which has been fixed now. If a page was opened for editing and the editing operation was then cancelled, the page would lose its disinheriting information. This could lead to publishing problems due to inheriting inconsistencies. This has been fixed now. When creating a new content tag that is named automatically, a name would be selected for it, although there is already a template tag by the same name, that is NOT editable in page. This name would typically be something like your_custom_tag1. This may cause confusion or even prevent a page from being saved in the backend. The new behavior is to only use automatically generated tag names, that are not used by any templatetags associated with any of the pagevariants using the content to be edited. Collisions may still occur if localizations of the template use a different set of templatetag names and there are no corresponding page localizations. When applying this update, the packaged Tomcat will be updated to version 7.0.61 which contains important security and bug fixes. You can delete the old Tomcat directory (/Node/apache-tomcat-7.0.54) after updating. Added documentation for changing the page title of the CMS Backend It is now possible to view failed dirt events in the maintenance dialog. Failed dirt events can be removed from the dirtqueue or can be re-scheduled. The Gentics Content.Node Javascript API has been changed, so that TagAPI objects will no longer be cached. The _data of TagAPI objects always reference the tag data in their parent (e.g. a PageAPI object), so there is no need to cache the TagAPI object as well. This fixes problems caused by the PageAPI object being refreshed in the cache, while the TagAPI objects were not refreshed, which caused them to no longer reference the tag data of the PageAPI object. The result was that changes in the TagAPI object were no longer reflected in the PageAPI object and saving the page would unintentionally restore old tag values. When the backend apache uses the module modunique_id_ this can lead to unexpected behaviour like cms dialogues that cannot be openend, until the user‘s session is reset. This has been fixed now. When a page is modified because the tagtype of a template tag (editable in pages) was changed, this will no longer change the editor or edate of the page. Also if the page is republished in this process, the publisher and pdate will not change. When editing object properties of a template or folder, the actions to make the object properties editable in pages where missing. They have been added again. When changing the language of a page in a node that does not have the original page language activated, replacing of the language code in the filename did not work. The new language code was just appended to the original one. This has been changed now: When changing the language of a page, the language code in the filename will now be replaced with the new one, even if the language is not activated in the node. The attribute name data-gcn-constructname, that exists for editing pages with the aloha editor was renamed to data-gcn-i18n-constructname. It contains the internationalized tagtype name of a tag. Make the shrinktofit option for the jqGrid (the object list) in the repository browser configurable. This option can be used to make the repository browsers width bigger on smaller screens while keeping the benefits of the dynamic resizing of the column widths. Links to internal pages or files that were entered with their internal URL will now correctly be transformed to tags pointing to the internal objects, instead of saving the URLs. This fixes incorrect saving of links with their internal URLs. When saving a page using the REST API, the status will always be set to 0 (being edited), regardless of the status flag in the posted page object. Some icons have been added to the “Page” menu. gcnfileupload-plugin: The upload form is now reset before every use. Fixed nested “intag“ object properties not being copied to subfolders when using the backend “Apply to subfolders“ or the Rest API “tagsToSubfolders” option. gcnfileupload-plugin: Added translations for several hardcoded german UI-elements. When creating nested object properties, the inner tag was only visible, if it was filled at least once, even if the tagtype had the option “auto-enabled” switched on. This has been fixed now. However, this will only affect new created nested object properties. Already existing object properties, that are not visible need to be filled once. Manual Change The implementation of the “Aloha Link” Tagtype needs to be updated. When linking to images (using the Aloha Link Plugin), the display of the link target in the toolbar was incorrect. The internal URL to the image was shown instead of the filename. The fix for this also requires an update of the implementation of the “Aloha Link“ Tagtype (keyword: “gtxalohapagelink”), according to the code in the Aloha Page Link Tag Description. A vulnerability of the GenticsImageStore in the CMS backend has been fixed. The creation of unique filenames during fileupload sometimes failed to distinguish filenames that only were different in case. This has been fixed now. When more than one handler subscribed the channel “tag.rendered”, the behaviour was unexpected: # If all handlers passed a modiied html to the callback only one of the changes was accepted # When saving a page, that contained at least two new links, not all of the links were correctly transformed to tags. The page icon used to display the language in the assistant frame was different for page preview and page properties. Now, for all operations the same icon is used to display the language in the assistant. The permission checks on the publish queue did not consider channel restrictions correctly. Users could see pages in the queue for all channels (but could not view the pages or approve publishing). The permission check in the queue has been fixed now. When users with permissions restricted to channels changed the binary content of channel local files, they received an error message (missing permission), although the file upload worked. This has been fixed now. Content.Repositories using deprecated attribute types will now be marked in the list of Content.Repositories. Also the attributes using deprecated types will be marked in the tagmap editor. Additionally, the Gentics Content.Node Guides now contain a migration guide for changing attribute types in Content.Repositories with minimal downtime of the frontend implementation. When editing a page with aloha editor using an older version of Internet Explorer (like IE9), clicking on menu items with unsaved changes in editables would warn the user twice about unsaved changes. When clicking on a menu item of the “page“ top menu, the page was saved, even if the user approved to leave the page with unsaved changes (twice). The behaviour has been changed now: when clicking on a “page” menu item, the page will be saved before the action is triggered. When clicking on another menu item (navigating away from the edited page), the user will get one notification about leaving the page with unsaved changes. Files that have no mimetype set (e.g. due to an error during the upload), will now be visible in the backend and be marked as “broken”. When closing a tagfill dialog in IE >= 9 no cursor was shown when clicking into another editable. This has been fixed. When using SSO with CAS or JOSSO, the user‘s sessions would be reset on every login. This has been fixed now. The entry “Save” in the related links (in the assistant frame) of the page preview has been removed, because it suggested, that the page had not been saved properly. Users with permissions restricted to channels were not allowed to create local folders in their channels. This has been fixed now. Copying a page into a channel local folder was not possible and has been fixed. When parts of a construct have to be replaced (i.e. some parts have to be removed and other have to be added) while importing, this could lead to incorrectly filled default values for such constructs. This has been fixed now. When the tag definition of a template was changed and the change was synchronized with the pages, this could lead to database locks if users tried to lock the same pages. This has been fixed now, users trying to lock pages currently changed by the synchronization will get the page in readonly mode. When publishing a node and its channels into the filesystem, and when localizing pages, the former inherited pages were sometimes not correctly removed from the filesystem of the channel. This has been fixed now. Fixed wrong proxy prefix for Gentics-Imagestore-URLs in frontend editing. When fetching an object via the REST API in edit mode, tags that were inactive, but should become active when edited were marked as being “inactive“. When the fetched object was saved back (without any changes), the tags would be set to “inactive“. This has been changed, so that tags in that state will now be marked as being “active”, if the object is fetched in edit mode. Previously, when using the language menu while a page is opened, the CMS would under certain circumstances display a page of the wrong language or even an error message. Now, the page is always either displayed in the chosen language, or the language doesn‘t change if the selected language version of the current page does not exist and the user is not allowed to create it. Previously, when clicking pages in the history, the CMS would under certain circumstances not open the intended page, display an error message or in rare cases create a translation. Now, exactly the specified page will be opened, as listed in the history (same language version, same channel). When a page was saved with only changes in the content, the status of the page was not changed to “being edited”. This has been fixed now. When an editor without publish permission tried to publish a page, all users of parent groups with publish permission were notified, even if the users were restricted to channels and were not allowed to see and publish the page in question. This has been fixed now: The node restriction is now considered when notifying users about pages to be published. Fixed an Internal Error while importing a modified tagtype, if the type of a part in the tagtype had been modified. When editing a page, the tool-tip of a tag now shows the tag keyword and the tagtype name instead of only the tag keyword. Fixed NullPointerException when comparing page versions in a master node with multichanneling. Sometimes, CSS settings of aloha editor plugins did not overwrite the core aloha editor CSS settings (due to a loading order problem), which could cause indeterministic layout problems. This has been fixed now, the core aloha editor CSS settings will now always be loaded before the plugin CSS settings, in order to allow the plugin CSS settings to overwrite the core settings. When opening a page in preview mode of aloha editor, the history entry created in the assistant frame showed the normal page icon, but would open the page in edit mode. This has been fixed now: only opening a page in edit mode will create a history entry showing the edit icon, that will open the page in edit mode again. A possible NullPointerException during the import has been fixed. CAS: Fixed CAS-services not being accesible via HTTPS by adding a new $CAS_SSO[‘curlOptions‘] option that allows the configuration of CURL SSL. Read the “CAS – Central Authentication Service” page in the documentation for more information. When importing templates that contained tags, where the values had been changed, under special cirvumstances, the new values were not imported correctly. This has been fixed now. Errors that happen while rendering velocity tags will now contain more descriptive information in the server log. The name and ID of the page and tag will be logged now. The documentation of the feature Copy Tags has been enhanced to include configuration settings, that are necessary for the feature to work. The permissions of object properties are now also respected by the GCN Rest API when loading or saving objects. Permissions: When a group had permissions on an object, and all permission were removed, the permission cache was not refreshed and the group still had the previous permissions. This only happened when all permissions to an object were removed. When editing a page with Aloha Editor and an editable only contained a table, it was not possible to add content before or after the table. This has been fixed now: When the editable is activated, paragraphs will be created as landing areas for the cursor. When editing a page with Aloha Editor, the following editing actions would lead to unexpected behaviour: Following these steps, the tagfill dialog would now be empty (not showing the data entered before). This problem has been fixed now, so that editing pages in the way described above will work as expected. It is now possible to change the synchronization mechanism for objects, that need to be removed from a content repository also for non-multichannelling aware contentrepository from the default differential synchronization to a full synchronization. Using the full synchronization is slower than the differential approach but is less error prone. Changed Contentrepository DB connection pool to be more resilient in cases of reset DB Connections. Fixed output of error log message caused by debug output when rendering tags for publishing. The algorithm to check whether a new page version must be created and to create the page version used many sql statements and therefore was inefficient. This algorithm has been changed now to be more efficient, especially when no page version must be created. This will affect actions like: The process of saving a page has been optimized to avoid unnecessary checks, if only content, but no metadata was changed. Fixed newly introduced error with bugfix SUP-434 in the previous hotfix. The overview wizard could start with page 1 even if the user already made all the selections on page 1. Fixed object properties not being deleted, when passing their name in the “delete” list of the PageResource.save Rest API method. When copying pages took longer than the configured timeout (due to high load on the server, number of copied pages or overall system performance), the user got an SGB, which suggested that copying failed, which was not the case. This has been fixed now: When copying pages takes longer than 5 seconds, the user will get a message, that the process will be continued in the background. Once copying is done, the user will receive an instant message. Additionally, when copying using the REST API, it is now possible to specify the maximum “foreground” time in milliseconds. The default value is 0, which will block the call until copying is done (which is the old behaviour). Overview tags in pages: When editing new overview tags in pages the wizard started wrongly with page 2 when no selection was made for the object type or the selection type in page 1. This has been fixed. The wizard will now start correctly with page one if any selection is possible and hasn‘t been made. When defining the tags in a template, it is now possible to save an updated list of tags without synchronizing the pages (by clicking the ‘Apply‘ button) or to save and synchronize the pages (by clicking the new ‘Apply and synchronize pages‘ button). Additionally, if errors occur (e.g. because some pages are currently locked by other users), the whole synchronization process does not fail (and has to be repeated), but all pages, that can be synchronized will be synchronized. If the action is triggered again (by clicking ‘Apply and synchronize pages‘ without actually changing the tag definitions, the remaining pages will be synchronized. Additionally, there is now an additional view (“Tagstate” via the template‘s top menu) that will show, how many pages are in sync or out of sync with the template regarding the editable tag definitions. REST-API: When copying a contenttag, using page/newtag, the operation would fail for some content tags. When editing a page using Aloha Editor with Internet Explorer, and adding new links to the page, the click on “Save” in the assistant frame showed a message, informing the user that he was about to leave the page with unsaved changes. This has been fixed now. Additionally, when saving a page that contained new links, some additional AJAX calls to the backend were done (in the background), which caused saving to be slower than necessary. Those AJAX calls have been reduced to the necessary minimum. Bug in GenticsImageStore Cache: When replacing a resized image in a page that is embedded with a GIS URL, the original resized image was still visible. This has been fixed. Some problems with copying or importing templates in the backend have been fixed: This update will also correct incorrectly bound templates in the database. When saving a page that contained a tag using one of the list parts (List, List (unordered), List (ordered)) the entries of the list part were merged into a single entry. The same happened, when migrating such a page with the tagtype migration, if at least one post processor was used. This has been fixed now. When custom columns were configured for the gcn-linkbrowser plugin, the display of thumbnails in the repository browser did not work any more. This has been fixed. Connections from the database connection pool are now tested before being used. Comparing Page Versions did not work correctly with Pages in localized Folders. This has been fixed. Copying a tagmap entry between contentrepositories would fail unconditionally. Fixed a NullpointerException when importing a page that could occur under rare circumstances. Multiple bugs fixed in page publishing: Fixed accidentally cutting off a filename extension when uploading a new file. If the user changes the filename when uploading a new file in the CMS and the new filename has no filename extension, then the original filename extension of the input file is attached to the new filename. In some cases an error could occur when accessing the CMS directly after an update has been applied. The error occurred because some mandatory tasks for i18n support were not completed. When a tagtype contains an velocity tagpart that is editable it could lead to side effects. Improved the documentation, so that making a velocity tagpart editable is now discouraged, as it is also not supported. The failure behaviour and logging of the publish process has been improved, in cases where committing the content repository transactions at the end of the publish process fails. When the localized copy of a page was taken offline, instant publishing would replace the page with the inherited page, instead of completely removing it from the content repository. Only the next regular publish run would correct this and remove the page from the content repository. This has been fixed now, so that instant publishing will correctly remove the page. Sometimes, the tree shown to select the target folder for copying pages was rendered incompletely. This has been fixed now. Implemented a workaround for the Internet Explorer 10 and 11 frame rendering issues with different document modes. GCN will force a redraw of content frames from now on in order to prevent issues with empty pages. Also fixed the upper page frame in the “translate to” page sometimes being invisible or too small. When a contentrepository was imported, the foreignlink attribute rule of an already existing tagmap entry would not be overwritten, if it was changed. This has been fixed now. Fixed documentation of AuthenticationResource to describe the proper parameters for the validate method. When multiple requests to translate a given page into a specific language were sent at the same time (or in a way that a new request was sent before the previous request returned), it was possible that multiple language variants in the requested language were created for the same page. Only one of the language variants was visible in the backend, but possibly both were published. This has been fixed now. Translating pages will now be synchronized (per page), so that multiple parallel requests will only create a single language variant, which will be returned by all of those requests. Fixed possible NPE when checking data in contentrepositories When moving folder structures within master nodes of multichannelling environments, all channel local objects in that structure were pushed to the master node as well. This has been changed now. Objects within moved folder structures will now only be moved between channels, if this is necessary to maintain channel integrity. Recursively setting permissions or setting object properties might take longer and run into a timeout. In such cases, it was not perfectly clear to the user, what happened and if the requested action was successfully performed. The processes have been changed now, so that if setting the permissions or the object properties recursively takes longer than some seconds, it will be sent to the background. The user will get a message that the process is continued in the background and will get an instant message when the process is completed. Fixed possible NPE when saving pages containing empty overviews Running the purgeversions could possibly remove a page version, even if the content was still used by another page variant, if the page variants were not in sync. This could lead to pages being published completely empty. This has been fixed now. If any pages having page variants lack their published page version and are therefore published completely empty, they must be published again to correct the page version. When an object is not changed during an import, because the local copy is identical to the imported version, the import details list will now show ‘unchanged‘ instead of ‘ignored‘ as import action. Additionally, the import details list will now also show conflicts, that existed during the import and the individual conflict setting for the imported objects. Optional Manual Change Java 8 Runtime Support Java 8 JRE support for Gentics Content.Node 5.17.x and newer was added. You can update the used Java version to Server JRE 8u25 64 bit by downloading the ‘Server JRE 8‘ package and extracting it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the Apache Tomcat server once you finished this step using the /Node/bin/nodectl script. Corrected paths for cleaning up unneccesary directories when performing the RHEL GCN package migration Fixed accidentally cutting off a filename extension. If a filename is changed in the CMS in the file properties and the new filename has no filename extension, then the previous filename extension (if any) is attached to the new filename. Changing a datasource with an import failed to dirt dependent objects. This has been fixed now. If the import changes entries of a datasource, dependent objects will be dirted. The memory consumption of the timetrigger script (used for time based workflows) has been reduced. Fixed curl printing debug output to error.log when the PHP curl extension is enabled. The assignment of languages to nodes was imported with the language, but not with the node: The behaviour has been changed now, so that the language assignment is changed, when the node is imported. When creating a folder, the role permissions were not inherited from the parent folder. This has been fixed. When editing a page with Aloha Editor in Internet Explorer (up to version 10 or in IE7 Mode), saving the page by clicking “Save” in the main menu, the user got a warning about leaving the page with unsaved changes. This has been fixed now, saving the page from the main menu will now work without the additional warning. The version of the library commons-dbcp has been updated from 1.2.1 to 1.2.2 which includes a fix for https://issues.apache.org/jira/browse/DBCP-64. This bug caused database connections to content repositories, that were fetched from the pool and died (e.g. because the server was not reachable any more) not being returned into the pool. This subsequently caused the pool to exhaust and the publish process to fail, until the tomcat was restarted. Fixed a bug in the import system with folders that got moved to another node. When a folder that is in the import file, already exists on the target system, but has been moved to another node on the source system, the node information for some folders would be inconsistent in the database in some cases. This caused some folders to not show up anymore in the tree because their parent folder couldn‘t be opened anymore. This has been fixed now. Copying pages in multichannelling environments did not work as expected: Those issues have been fixed now. Login: When someone tried to log in with an empty password, GCN displayed an “Internal error“ message instead of “Bad credentials”. Replaced logos in Gentics Content.Node to fit to the new Gentics CD. Rest API: Fixed MySQL deadlock problem that can happen when calling methods in PermResource that change object permissions parallelly (eg.: in threads). When a custom context path is configured like documented in the Guides, the thumbnails of images in the minibrowser were not rendered, because the URLs were wrong. This has been fixed now. Page tags: Removed message in the tooltip stating that the tag is not editable in the page, even though it is editable. Apache/Tomcat AJP connector: mod_jk has been replaced by mod_proxy_ajp in the GCN package. A rendering issue in IE 10 can cause blank pages to be rendered when using framesets. Adjusted the browser compatibility list and the “disableIE7StandardsMode” feature description. 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. 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. A rare error in the feature resumablepublish_process_, which could cause the publish process to fail, has been fixed. 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. 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. 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. 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. Sanitize filename feature: Fixed the hint message being shown, even if the feature is properly configured. Fixed handling of filenames containing dots. Fixed sanitizing of the filename extension. Some bugs in the sanitize name feature have been fixed: SSL Security Advisory When creating folders over the REST API, the inheritable object tags from the mother folder were not automatically set for the new created folder. This has been fixed now. Creating new folders in the backend sometimes produced an SGB due to duplicate object tags. The folder was created in the DB, but caches were not properly cleared, which caused some problems afterwards. This has been fixed now, duplicate object tags will be ignored now. When creating pages from within the todo tool, the language was not correctly set, if the Node, the user had visited last, did not have that language activated. This has been fixed now, the language will now be checked against the languages of the Node, where the page is created. Saving the tag definitions of a template possibly takes some time, because it could affect many pages. This could lead to a timeout in the request, which resulted in an SGB, although the process of saving the tag definition was successful. This has been changed now, so that if saving the tag definitions takes longer, the process will be taken to the background and the user will get a notification, when saving is complete. When an editor without permission to publish a page tried to publish a page that was missing some mandatory tags, the page would be put into the queue nevertheless. This is incorrect, the check for missing mandatory tags has to be done before putting the page into the queue. The behaviour has been changed now, so that it is not possible to put a page into the queue, if it is missing mandatory tags. Some issues of export and import of channel structures have been fixed. Fixed a SGB error that occured in some cases, when trying to upload a new file in the tag fill dialog. Editing pages with Aloha Editor: When using the method addDeleteButton() to add delete buttons to blocks, that contain nested blocks, the delete button was also attached to the nested blocks. This has been fixed now. Image Manipulation: The error “include imagemanipulation2 not found.” which showed up in the error log but had no functional consequence was fixed. When publishing into a non MCCR content repository and not using multithreaded publishing, the motherid of an object sometimes would not be updated after the object had been moved to another folder. This has been fixed now. When an editor using Aloha Editor on Internet Explorer tried to leave the edited page (e.g. by clicking into the tree) with unsaved changes, a confirm message was shown, whether the changes should be saved before leaving the page. However, saving never worked, regardless of whether “OK“ or “Cancel” was clicked. Since it is not possible to save the page in an asynchronous call when leaving the page (the browser just would not issue the asynchronous save request), the behaviour when just leaving the page with unsaved changes has now been unified for all browsers: The user will get a notification message, explaining that unsaved changes would be lost when leaving the page. When a page is modified and republished during a publish process that published this page, it could happen that not all dependencies of the republished page were correctly dirted. This has been fixed now. In the previous bugfix RT58305, a background job that deletes broken content tags was added. However when a broken tag was found it caused the Tomcat to wrongly block the startup due to a not logged error. The error handling of background jobs has also been improved. When content repositories, that have instant publishing enabled are not available, this might affect the whole system. With some new configuration options, it is possible to have instant publishing temporarily disabled in case of availability problems. See Instant Publishing in the Guides for details. The tree used to select the target folders when copying pages internally used too many requests to the REST API. This has been fixed now, which will reduce the render times for the tree. In some situations, dirting of folders upon changed object properties might not work, because a new object tag object had been created since the folder was last published. Storing of dependencies has been improved to be insensitive against such situations. It is important to note, that this change will only affect objects, that are republished after this update. Some errors, that occurred while rendering the tree will be logged now. When generating a filename from the page name, the result was empty, if the name contained only whitespace characters. Also, a filename that begins with a dot could cause problems. This has been fixed, so that in both cases the filename will begin with “1” instead. The import of pages will now give more explicit error messages (in the server log) when the process fails due to data inconsistencies. Enhanced the documentation of how to migrate GCN to the new package with system distribution Apache. When using the Repository Browser in IE7 (or in a more recent version of Internet Explorer in IE7 mode), resizing the window and/or the Repository Browser could completely crash the browser. This has been fixed now. When editing template properties, the file upload field always reported an error (“A file needs to be selected”) although selecting a file is not necessary. The changes made for the template were saved anyway. This has been fixed now. When editing with Aloha Editor and an editable is activated that has a block element (like a table or tag) as first and/or last element, an empty paragraph needs to be inserted at the very start and/or end of the editable in order to provide a landing place for the cursor. When using Internet Explorer in IE7 mode, this did not work properly. Sometimes no paragraph was added, sometimes it contained a superfluous break element and thus had two lines. This has been fixed now. When rendering other tags with the velocity directory #gtx_edit() never rendered the tags in edit mode. This has been fixed now, the directory #gtx_edit() now also works for other tags. When publishing a page out of the Real Edit Mode using Aloha Editor failed (e.g. due to missing mandatory fields), no message was shown to the editor. This has been fixed now: a message will be shown to the editor and the page will stay in edit mode. REST API: Deleting a page would not work if it has missing contenttags or contenttags with missing values. The delete call would also report success on the delete operation in this case. When setting an object property for a localized folder in a channel and applying the change to all subfolders, the change also affected subfolders in the master channel. This has been fixed. Now, if an object-property-change is applied to all subfolders of a localized folder, then only localized subfolders in the same channel will be affected by the change. When setting the page language to a different language the language of the localized versions of the page was not updated. This has been fixed. Optional Manual Change Implementation of the tagtype for the FileLink plugin maybe has to be updated The Setup Guide of the Gentics Content.Node FileLink plugin did not explicitly state, that the part Sorting the items listed in the repository browser by name did not work and has been fixed now. Fixed that the user login didn‘t work on systems with 3rd party tools like siteminder or anything that adds additional cookies to the response headers of the Rest API. In rare cases the publish process could fail with an error like “ERROR: com.gentics.api.lib.exception.NodeException: Action WRITE_CR was initiated for object 10002.4711.99 twice” due to conflicting entries in the publish queue. This has been fixed now. Workflows: An issue was fixed which prevented trash workflows for folders from being executed correctly. Previously a trash workflow would not be able to move folders into a trash folder. Deleting of folders was not possible when the workflow was enabled. The error first occurred in GCN 5.17.11 and 5.18.0. When changing the tagtype of a template tag, that is editable in pages, not all caches where cleared correctly after the tags in the pages were changed. This could cause subsequent errors. E.g. when editing a page afterwards, it could happen, that the page was stored with the original tagtype. This has been fixed now. Construct Editing: Modifying any construct property including description, keyname, parts caused all pages to be republished that utilized tags that were created using the construct. Only modifications to parts will now cause republishing of pages. Modifying all other properties including keyname and description will no longer cause publishing of pages. When migrating existing projects to Aloha Editor, live editable tagtypes that use a part like CAS & JOSSO authentication: Fixed that the login didn‘t work and the users were stuck in an endless redirection loop. Some additional log entries were added to better log, when a template is modified. Also locking and unlocking pages will now be logged separately with new log actions “Lock“ and “Unlock”. Manual Change Aloha Link tagtype: A previous manual update of the tagtype “Aloha Link” caused a misbehaviour when adding a link. Breaks were inserted before and after links when saving a page. To perform the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. When disabling the IE7 Standards Mode, and editing pages using the old Live Editor, some incorrect CSS setting caused rendering problems for editable areas. The borders around editables containing multiple lines of content were not rendered correctly and the tag icon changed it‘s position when activating the editable. This has been fixed now. When editing a page using aloha editor in “real editor“ mode, saving the page (using the “Save“ button in the ribbon), saved the page, but did not create a new version. When clicking the “Cancel“ button in the ribbon afterwards, the last saved version of the page is restored, which is unexpected behaviour. This has been fixed now, when using the “Save“ button in the ribbon to save the page, a new version will now be created and clicking “Cancel” afterwards will no longer undo the changes, which were saved before. The update process has been changed to change the group of the PHP files to node_public, if the user node is member of that group. This fixes permission problems on systems that still use the second HTTP server for XNL modules. Translation permissions: A message will now be displayed when the translator has not enough permissions to translate a page in a different language. Previously the action was just silently aborted. Page Translate: In some cases a page property dialog with empty fields and no confirm button was shown when a user tried to translate a page. Additional permission checks were added in order to prevent this bug. The error messages now also contain information about the missing permissions. The gallery view was affected by the paging setting, but did not show the paging controls. Also the placement of the images in the gallery was wrong. This has been fixed now, the gallery will now show all images and will not use paging. When changing the name of a folder, without changing the publish directory, no check for duplicate publish paths will be done. Therefore, changing only the name is still possible, even if duplicate publish paths already exist. Page list: In some cases the top menu search menu was not being displayed. Additional role permission checks have been added in order to correctly determine the visibility of this menu entry. When pages, images or files cannot be moved due to naming conflicts, the error messages will now explicitly contain the names of the conflicting objects and their folders. Additionally, if the conflict arises in a channel (but not in the master node), the channel name will be contained in the error messages. Error messages will now be shown in a browser alert message, so they cannot be easily missed. Manual Change Apache webserver with new PHP version (package migration) & Apache Tomcat 7 update Important: If your current version is GCN 5.15.* or older, do NOT update to GCN 5.18.* directly. In this case update to GCN 5.17.* first, then do the package migration as explained in 1.) and then update to 5.18.*. Otherwise the update will not work. 1.) The Gentics Content.Node package now no longer supports the legacy packaged Apache webserver that was included in the /Node folder. Please migrate your Content.Node package before updating your system according to the migration guide. PHP 5.3 or higher is now mandatory to run Gentics Content.Node. 2.) Due to the Apache Tomcat 7 update it is mandatory to update some configuration files in /Node/etc/tomcat/ These configuration files may contain custom settings and should be inspected before updating. Please follow the configuration update steps before you continue with the Update. If not executed, your installation will not be able to startup. In that case you can just update your configuration files and restart the Apache Tomcat via nodectl. The password hashing of GCN users has been changed to use bcrypt for hashing. When applying this update, all stored passwords will be re-hashed with bcrypt immediately. As the old hashing algorithm is considered as weak by encryption experts, it‘s recommended to apply this update. The repository browser has been improved with the possibility to allow configuring of paging and columns and better visualization of translated pages. IPv6 support was added to Gentics Content.Node. No additional GCN configuration is needed to enable this capability. The Apache Tomcat version was updated to version 7.0.54. REST API: It is now possible to set the page name and filename within the PageCreateRequest. The page copy functionality was updated. It is now also possible to use the REST API to copy pages. Rest API /image/resize: Added new option “copyFile” to the request object which allows copying of the image during the resize call. Image manipulation: Multiple enhancements Previously when the system wasn‘t used for a very long time, the scheduler would create a lot of new sessions in the database. On the first login the session cleanup took very long and let the user wait. This has been fixed now. Feature “publish_folder_startpage”: Fixed a bug where the language variants of start pages wouldn‘t be published. When a page is published using instant publishing, the language variants of the start page will also be published now. When saving pages with Aloha Editor, that contain links with empty HTML tags in them (like a When assigning permissions to groups, sometimes certain checkboxes were not filled correctly in some browsers. This has been fixed. When a user with permissions restricted to channels tried to take a page offline over the REST API, the permission check was not done channel specific, which has been fixed now. Automatic inbox messages that are generated when When taking a page offline over the REST API, other pages will be checked for invalid links now. Changing an object property now creates an entry in the administration logs. The initial timespan of log entries to be shown in the “Logs” view has been reduced from one hour to five minutes. This reduces the number of initially shown entries, especially if the user has no paging activated. When users where granted permission to view files/images through roles, these permissions were not considered during a recursive search for files/images (in the subfolders). This has been fixed now. For implementations using their own jQuery Version, saving the page with Aloha Editor failed with a javascript error, when the page contained at least one anchor tag. This has been fixed now. When users with publish permission restricted to channels tried to publish pages out of the publish queue, this sometimes failed due to an incorrect permission check. This has been fixed now. When a page contained an anchor tag without href attribute, an error occurred while saving the page with Aloha Editor. This has been fixed now. Enhanced the error handling of PHP errors. Catchable PHP errors will be also logged to the Gentics Content.Node error log now. Fixed a syntax error in the gcn-fileupload plugin that caused a JavaScript error with Internet Explorer in IE7-Mode. When the publish process failed during handling of time management, the process was marked as “OK” in the scheduler. This has been fixed now. When editing a page with Aloha Editor and changing an internal link to point to an external target, this change sometimes was not persisted when saving. This has been fixed now. When creating tables or tags at the very beginning or end of an editable, an empty paragraph will also be added (which is automatically removed if not needed), so that the cursor can be set before or after the new tag or table. Before this fix, it was necessary to deactivate and activate the editable to get the empty paragraphs. When a page is opened for editing with Aloha Editor, lot‘s of redundant AJAX calls to the REST API were made to initialize the Editor. The number of calls has been reduced now, which will minimize the overall loading time, especially for pages that contain many editables and tags. Image manipulation 2: When used with a custom context path, the image would disappear from the editor after resize or crop operations. This was due to a broken link, which has been fixed now. If a page was opened for editing and the editing operation was then cancelled, the page would lose its disinheriting information. This could lead to publishing problems due to inheriting inconsistencies. This has been fixed now. When creating a new content tag that is named automatically, a name would be selected for it, although there is already a template tag by the same name, that is NOT editable in page. This name would typically be something like your_custom_tag1. This may cause confusion or even prevent a page from being saved in the backend. The new behavior is to only use automatically generated tag names, that are not used by any templatetags associated with any of the pagevariants using the content to be edited. Collisions may still occur if localizations of the template use a different set of templatetag names and there are no corresponding page localizations. Added documentation for changing the page title of the CMS Backend It is now possible to view failed dirt events in the maintenance dialog. Failed dirt events can be removed from the dirtqueue or can be re-scheduled. The Gentics Content.Node Javascript API has been changed, so that TagAPI objects will no longer be cached. The _data of TagAPI objects always reference the tag data in their parent (e.g. a PageAPI object), so there is no need to cache the TagAPI object as well. This fixes problems caused by the PageAPI object being refreshed in the cache, while the TagAPI objects were not refreshed, which caused them to no longer reference the tag data of the PageAPI object. The result was that changes in the TagAPI object were no longer reflected in the PageAPI object and saving the page would unintentionally restore old tag values. When the backend apache uses the module modunique_id_ this can lead to unexpected behaviour like cms dialogues that cannot be openend, until the user‘s session is reset. This has been fixed now. When a page is modified because the tagtype of a template tag (editable in pages) was changed, this will no longer change the editor or edate of the page. Also if the page is republished in this process, the publisher and pdate will not change. When editing object properties of a template or folder, the actions to make the object properties editable in pages where missing. They have been added again. When changing the language of a page in a node that does not have the original page language activated, replacing of the language code in the filename did not work. The new language code was just appended to the original one. This has been changed now: When changing the language of a page, the language code in the filename will now be replaced with the new one, even if the language is not activated in the node. The attribute name data-gcn-constructname, that exists for editing pages with the aloha editor was renamed to data-gcn-i18n-constructname. It contains the internationalized tagtype name of a tag. Make the shrinktofit option for the jqGrid (the object list) in the repository browser configurable. This option can be used to make the repository browsers width bigger on smaller screens while keeping the benefits of the dynamic resizing of the column widths. Links to internal pages or files that were entered with their internal URL will now correctly be transformed to tags pointing to the internal objects, instead of saving the URLs. This fixes incorrect saving of links with their internal URLs. When saving a page using the REST API, the status will always be set to 0 (being edited), regardless of the status flag in the posted page object. Some icons have been added to the “Page” menu. gcnfileupload-plugin: The upload form is now reset before every use. Fixed nested “intag“ object properties not being copied to subfolders when using the backend “Apply to subfolders“ or the Rest API “tagsToSubfolders” option. gcnfileupload-plugin: Added translations for several hardcoded german UI-elements. When creating nested object properties, the inner tag was only visible, if it was filled at least once, even if the tagtype had the option “auto-enabled” switched on. This has been fixed now. However, this will only affect new created nested object properties. Already existing object properties, that are not visible need to be filled once. Manual Change The implementation of the “Aloha Link” Tagtype needs to be updated. When linking to images (using the Aloha Link Plugin), the display of the link target in the toolbar was incorrect. The internal URL to the image was shown instead of the filename. The fix for this also requires an update of the implementation of the “Aloha Link“ Tagtype (keyword: “gtxalohapagelink”), according to the code in the Aloha Page Link Tag Description. A vulnerability of the GenticsImageStore in the CMS backend has been fixed. The creation of unique filenames during fileupload sometimes failed to distinguish filenames that only were different in case. This has been fixed now. When more than one handler subscribed the channel “tag.rendered”, the behaviour was unexpected: # If all handlers passed a modiied html to the callback only one of the changes was accepted # When saving a page, that contained at least two new links, not all of the links were correctly transformed to tags. The page icon used to display the language in the assistant frame was different for page preview and page properties. Now, for all operations the same icon is used to display the language in the assistant. The permission checks on the publish queue did not consider channel restrictions correctly. Users could see pages in the queue for all channels (but could not view the pages or approve publishing). The permission check in the queue has been fixed now. When users with permissions restricted to channels changed the binary content of channel local files, they received an error message (missing permission), although the file upload worked. This has been fixed now. Content.Repositories using deprecated attribute types will now be marked in the list of Content.Repositories. Also the attributes using deprecated types will be marked in the tagmap editor. Additionally, the Gentics Content.Node Guides now contain a migration guide for changing attribute types in Content.Repositories with minimal downtime of the frontend implementation. When editing a page with aloha editor using an older version of Internet Explorer (like IE9), clicking on menu items with unsaved changes in editables would warn the user twice about unsaved changes. When clicking on a menu item of the “page“ top menu, the page was saved, even if the user approved to leave the page with unsaved changes (twice). The behaviour has been changed now: when clicking on a “page” menu item, the page will be saved before the action is triggered. When clicking on another menu item (navigating away from the edited page), the user will get one notification about leaving the page with unsaved changes. Files that have no mimetype set (e.g. due to an error during the upload), will now be visible in the backend and be marked as “broken”. When closing a tagfill dialog in IE >= 9 no cursor was shown when clicking into another editable. This has been fixed. The entry “Save” in the related links (in the assistant frame) of the page preview has been removed, because it suggested, that the page had not been saved properly. When parts of a construct have to be replaced (i.e. some parts have to be removed and other have to be added) while importing, this could lead to incorrectly filled default values for such constructs. This has been fixed now. When the tag definition of a template was changed and the change was synchronized with the pages, this could lead to database locks if users tried to lock the same pages. This has been fixed now, users trying to lock pages currently changed by the synchronization will get the page in readonly mode. When publishing a node and its channels into the filesystem, and when localizing pages, the former inherited pages were sometimes not correctly removed from the filesystem of the channel. This has been fixed now. Fixed wrong proxy prefix for Gentics-Imagestore-URLs in frontend editing. When fetching an object via the REST API in edit mode, tags that were inactive, but should become active when edited were marked as being “inactive“. When the fetched object was saved back (without any changes), the tags would be set to “inactive“. This has been changed, so that tags in that state will now be marked as being “active”, if the object is fetched in edit mode. Previously, when using the language menu while a page is opened, the CMS would under certain circumstances display a page of the wrong language or even an error message. Now, the page is always either displayed in the chosen language, or the language doesn‘t change if the selected language version of the current page does not exist and the user is not allowed to create it. Previously, when clicking pages in the history, the CMS would under certain circumstances not open the intended page, display an error message or in rare cases create a translation. Now, exactly the specified page will be opened, as listed in the history (same language version, same channel). When a page was saved with only changes in the content, the status of the page was not changed to “being edited”. This has been fixed now. When an editor without publish permission tried to publish a page, all users of parent groups with publish permission were notified, even if the users were restricted to channels and were not allowed to see and publish the page in question. This has been fixed now: The node restriction is now considered when notifying users about pages to be published. Fixed an Internal Error while importing a modified tagtype, if the type of a part in the tagtype had been modified. When editing a page, the tool-tip of a tag now shows the tag keyword and the tagtype name instead of only the tag keyword. Fixed NullPointerException when comparing page versions in a master node with multichanneling. Sometimes, CSS settings of aloha editor plugins did not overwrite the core aloha editor CSS settings (due to a loading order problem), which could cause indeterministic layout problems. This has been fixed now, the core aloha editor CSS settings will now always be loaded before the plugin CSS settings, in order to allow the plugin CSS settings to overwrite the core settings. When opening a page in preview mode of aloha editor, the history entry created in the assistant frame showed the normal page icon, but would open the page in edit mode. This has been fixed now: only opening a page in edit mode will create a history entry showing the edit icon, that will open the page in edit mode again. A possible NullPointerException during the import has been fixed. When importing templates that contained tags, where the values had been changed, under special cirvumstances, the new values were not imported correctly. This has been fixed now. Errors that happen while rendering velocity tags will now contain more descriptive information in the server log. The name and ID of the page and tag will be logged now. The documentation of the feature Copy Tags has been enhanced to include configuration settings, that are necessary for the feature to work. CAS: Fixed CAS-services not being accesible via HTTPS by adding a new $CAS_SSO[‘curlOptions‘] option that allows the configuration of CURL SSL. Read the “CAS – Central Authentication Service” page in the documentation for more information. The permissions of object properties are now also respected by the GCN Rest API when loading or saving objects. Permissions: When a group had permissions on an object, and all permission were removed, the permission cache was not refreshed and the group still had the previous permissions. This only happened when all permissions to an object were removed. When editing a page with Aloha Editor and an editable only contained a table, it was not possible to add content before or after the table. This has been fixed now: When the editable is activated, paragraphs will be created as landing areas for the cursor. When editing a page with Aloha Editor, the following editing actions would lead to unexpected behaviour: Following these steps, the tagfill dialog would now be empty (not showing the data entered before). This problem has been fixed now, so that editing pages in the way described above will work as expected. It is now possible to change the synchronization mechanism for objects, that need to be removed from a content repository also for non-multichannelling aware contentrepository from the default differential synchronization to a full synchronization. Using the full synchronization is slower than the differential approach but is less error prone. Changed Contentrepository DB connection pool to be more resilient in cases of reset DB Connections. Fixed output of error log message caused by debug output when rendering tags for publishing. The algorithm to check whether a new page version must be created and to create the page version used many sql statements and therefore was inefficient. This algorithm has been changed now to be more efficient, especially when no page version must be created. This will affect actions like: The process of saving a page has been optimized to avoid unnecessary checks, if only content, but no metadata was changed. Fixed newly introduced error with bugfix SUP-434 in the previous hotfix. The overview wizard could start with page 1 even if the user already made all the selections on page 1. Fixed object properties not being deleted, when passing their name in the “delete” list of the PageResource.save Rest API method. Overview tags in pages: When editing new overview tags in pages the wizard started wrongly with page 2 when no selection was made for the object type or the selection type in page 1. This has been fixed. The wizard will now start correctly with page one if any selection is possible and hasn‘t been made. When defining the tags in a template, it is now possible to save an updated list of tags without synchronizing the pages (by clicking the ‘Apply‘ button) or to save and synchronize the pages (by clicking the new ‘Apply and synchronize pages‘ button). Additionally, if errors occur (e.g. because some pages are currently locked by other users), the whole synchronization process does not fail (and has to be repeated), but all pages, that can be synchronized will be synchronized. If the action is triggered again (by clicking ‘Apply and synchronize pages‘ without actually changing the tag definitions, the remaining pages will be synchronized. Additionally, there is now an additional view (“Tagstate” via the template‘s top menu) that will show, how many pages are in sync or out of sync with the template regarding the editable tag definitions. REST-API: When copying a contenttag, using page/newtag, the operation would fail for some content tags. When editing a page using Aloha Editor with Internet Explorer, and adding new links to the page, the click on “Save” in the assistant frame showed a message, informing the user that he was about to leave the page with unsaved changes. This has been fixed now. Additionally, when saving a page that contained new links, some additional AJAX calls to the backend were done (in the background), which caused saving to be slower than necessary. Those AJAX calls have been reduced to the necessary minimum. Bug in GenticsImageStore Cache: When replacing a resized image in a page that is embedded with a GIS URL, the original resized image was still visible. This has been fixed. Some problems with copying or importing templates in the backend have been fixed: This update will also correct incorrectly bound templates in the database. When saving a page that contained a tag using one of the list parts (List, List (unordered), List (ordered)) the entries of the list part were merged into a single entry. The same happened, when migrating such a page with the tagtype migration, if at least one post processor was used. This has been fixed now. Connections from the database connection pool are now tested before being used. Comparing Page Versions did not work correctly with Pages in localized Folders. This has been fixed. Copying a tagmap entry between contentrepositories would fail unconditionally. Fixed a NullpointerException when importing a page that could occur under rare circumstances. Multiple bugs fixed in page publishing: Fixed accidentally cutting off a filename extension when uploading a new file. If the user changes the filename when uploading a new file in the CMS and the new filename has no filename extension, then the original filename extension of the input file is attached to the new filename. In some cases an error could occur when accessing the CMS directly after an update has been applied. The error occurred because some mandatory tasks for i18n support were not completed. When a tagtype contains an velocity tagpart that is editable it could lead to side effects. Improved the documentation, so that making a velocity tagpart editable is now discouraged, as it is also not supported. The failure behaviour and logging of the publish process has been improved, in cases where committing the content repository transactions at the end of the publish process fails. When the localized copy of a page was taken offline, instant publishing would replace the page with the inherited page, instead of completely removing it from the content repository. Only the next regular publish run would correct this and remove the page from the content repository. This has been fixed now, so that instant publishing will correctly remove the page. Sometimes, the tree shown to select the target folder for copying pages was rendered incompletely. This has been fixed now. Implemented a workaround for the Internet Explorer 10 and 11 frame rendering issues with different document modes. GCN will force a redraw of content frames from now on in order to prevent issues with empty pages. Also fixed the upper page frame in the “translate to” page sometimes being invisible or too small. When a contentrepository was imported, the foreignlink attribute rule of an already existing tagmap entry would not be overwritten, if it was changed. This has been fixed now. Fixed documentation of AuthenticationResource to describe the proper parameters for the validate method. When multiple requests to translate a given page into a specific language were sent at the same time (or in a way that a new request was sent before the previous request returned), it was possible that multiple language variants in the requested language were created for the same page. Only one of the language variants was visible in the backend, but possibly both were published. This has been fixed now. Translating pages will now be synchronized (per page), so that multiple parallel requests will only create a single language variant, which will be returned by all of those requests. Fixed possible NPE when checking data in contentrepositories When moving folder structures within master nodes of multichannelling environments, all channel local objects in that structure were pushed to the master node as well. This has been changed now. Objects within moved folder structures will now only be moved between channels, if this is necessary to maintain channel integrity. Recursively setting permissions or setting object properties might take longer and run into a timeout. In such cases, it was not perfectly clear to the user, what happened and if the requested action was successfully performed. The processes have been changed now, so that if setting the permissions or the object properties recursively takes longer than some seconds, it will be sent to the background. The user will get a message that the process is continued in the background and will get an instant message when the process is completed. Fixed possible NPE when saving pages containing empty overviews Running the purgeversions could possibly remove a page version, even if the content was still used by another page variant, if the page variants were not in sync. This could lead to pages being published completely empty. This has been fixed now. If any pages having page variants lack their published page version and are therefore published completely empty, they must be published again to correct the page version. When an object is not changed during an import, because the local copy is identical to the imported version, the import details list will now show ‘unchanged‘ instead of ‘ignored‘ as import action. Additionally, the import details list will now also show conflicts, that existed during the import and the individual conflict setting for the imported objects. Optional Manual Change Java 8 Runtime Support Java 8 JRE support for Gentics Content.Node 5.17.x and newer was added. You can update the used Java version to Server JRE 8u25 64 bit by downloading the ‘Server JRE 8‘ package and extracting it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the Apache Tomcat server once you finished this step using the /Node/bin/nodectl script. Corrected paths for cleaning up unneccesary directories when performing the RHEL GCN package migration Fixed accidentally cutting off a filename extension. If a filename is changed in the CMS in the file properties and the new filename has no filename extension, then the previous filename extension (if any) is attached to the new filename. Changing a datasource with an import failed to dirt dependent objects. This has been fixed now. If the import changes entries of a datasource, dependent objects will be dirted. The memory consumption of the timetrigger script (used for time based workflows) has been reduced. Fixed curl printing debug output to error.log when the PHP curl extension is enabled. The assignment of languages to nodes was imported with the language, but not with the node: The behaviour has been changed now, so that the language assignment is changed, when the node is imported. When creating a folder, the role permissions were not inherited from the parent folder. This has been fixed. When editing a page with Aloha Editor in Internet Explorer (up to version 10 or in IE7 Mode), saving the page by clicking “Save” in the main menu, the user got a warning about leaving the page with unsaved changes. This has been fixed now, saving the page from the main menu will now work without the additional warning. The version of the library commons-dbcp has been updated from 1.2.1 to 1.2.2 which includes a fix for https://issues.apache.org/jira/browse/DBCP-64. This bug caused database connections to content repositories, that were fetched from the pool and died (e.g. because the server was not reachable any more) not being returned into the pool. This subsequently caused the pool to exhaust and the publish process to fail, until the tomcat was restarted. Fixed a bug in the import system with folders that got moved to another node. When a folder that is in the import file, already exists on the target system, but has been moved to another node on the source system, the node information for some folders would be inconsistent in the database in some cases. This caused some folders to not show up anymore in the tree because their parent folder couldn‘t be opened anymore. This has been fixed now. Replaced logos in Gentics Content.Node to fit to the new Gentics CD. Rest API: Fixed MySQL deadlock problem that can happen when calling methods in PermResource that change object permissions parallelly (eg.: in threads). When a custom context path is configured like documented in the Guides, the thumbnails of images in the minibrowser were not rendered, because the URLs were wrong. This has been fixed now. Page tags: Removed message in the tooltip stating that the tag is not editable in the page, even though it is editable. Apache/Tomcat AJP connector: mod_jk has been replaced by mod_proxy_ajp in the GCN package. A rendering issue in IE 10 can cause blank pages to be rendered when using framesets. Adjusted the browser compatibility list and the “disableIE7StandardsMode” feature description. 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. 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. A rare error in the feature resumablepublish_process_, which could cause the publish process to fail, has been fixed. 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. 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. 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. 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. Sanitize filename feature: Fixed the hint message being shown, even if the feature is properly configured. Fixed handling of filenames containing dots. Fixed sanitizing of the filename extension. Some bugs in the sanitize name feature have been fixed: When creating folders over the REST API, the inheritable object tags from the mother folder were not automatically set for the new created folder. This has been fixed now. Creating new folders in the backend sometimes produced an SGB due to duplicate object tags. The folder was created in the DB, but caches were not properly cleared, which caused some problems afterwards. This has been fixed now, duplicate object tags will be ignored now. Some issues of export and import of channel structures have been fixed. Editing pages with Aloha Editor: When using the method addDeleteButton() to add delete buttons to blocks, that contain nested blocks, the delete button was also attached to the nested blocks. This has been fixed now. When publishing into a non MCCR content repository and not using multithreaded publishing, the motherid of an object sometimes would not be updated after the object had been moved to another folder. This has been fixed now. When content repositories, that have instant publishing enabled are not available, this might affect the whole system. With some new configuration options, it is possible to have instant publishing temporarily disabled in case of availability problems. See Instant Publishing in the Guides for details. The tree used to select the target folders when copying pages internally used too many requests to the REST API. This has been fixed now, which will reduce the render times for the tree. In some situations, dirting of folders upon changed object properties might not work, because a new object tag object had been created since the folder was last published. Storing of dependencies has been improved to be insensitive against such situations. It is important to note, that this change will only affect objects, that are republished after this update. Some errors, that occurred while rendering the tree will be logged now. Saving the tag definitions of a template possibly takes some time, because it could affect many pages. This could lead to a timeout in the request, which resulted in an SGB, although the process of saving the tag definition was successful. This has been changed now, so that if saving the tag definitions takes longer, the process will be taken to the background and the user will get a notification, when saving is complete. Fixed a SGB error that occured in some cases, when trying to upload a new file in the tag fill dialog. When a page is modified and republished during a publish process that published this page, it could happen that not all dependencies of the republished page were correctly dirted. This has been fixed now. In the previous bugfix RT58305, a background job that deletes broken content tags was added. However when a broken tag was found it caused the Tomcat to wrongly block the startup due to a not logged error. The error handling of background jobs has also been improved. When generating a filename from the page name, the result was empty, if the name contained only whitespace characters. Also, a filename that begins with a dot could cause problems. This has been fixed, so that in both cases the filename will begin with “1” instead. The import of pages will now give more explicit error messages (in the server log) when the process fails due to data inconsistencies. SSL Security Advisory When creating pages from within the todo tool, the language was not correctly set, if the Node, the user had visited last, did not have that language activated. This has been fixed now, the language will now be checked against the languages of the Node, where the page is created. When an editor without permission to publish a page tried to publish a page that was missing some mandatory tags, the page would be put into the queue nevertheless. This is incorrect, the check for missing mandatory tags has to be done before putting the page into the queue. The behaviour has been changed now, so that it is not possible to put a page into the queue, if it is missing mandatory tags. Image Manipulation: The error “include imagemanipulation2 not found.” which showed up in the error log but had no functional consequence was fixed. When an editor using Aloha Editor on Internet Explorer tried to leave the edited page (e.g. by clicking into the tree) with unsaved changes, a confirm message was shown, whether the changes should be saved before leaving the page. However, saving never worked, regardless of whether “OK“ or “Cancel” was clicked. Since it is not possible to save the page in an asynchronous call when leaving the page (the browser just would not issue the asynchronous save request), the behaviour when just leaving the page with unsaved changes has now been unified for all browsers: The user will get a notification message, explaining that unsaved changes would be lost when leaving the page. Enhanced the documentation of how to migrate GCN to the new package with system distribution Apache. When using the Repository Browser in IE7 (or in a more recent version of Internet Explorer in IE7 mode), resizing the window and/or the Repository Browser could completely crash the browser. This has been fixed now. When editing template properties, the file upload field always reported an error (“A file needs to be selected”) although selecting a file is not necessary. The changes made for the template were saved anyway. This has been fixed now. When editing with Aloha Editor and an editable is activated that has a block element (like a table or tag) as first and/or last element, an empty paragraph needs to be inserted at the very start and/or end of the editable in order to provide a landing place for the cursor. When using Internet Explorer in IE7 mode, this did not work properly. Sometimes no paragraph was added, sometimes it contained a superfluous break element and thus had two lines. This has been fixed now. When rendering other tags with the velocity directory #gtx_edit() never rendered the tags in edit mode. This has been fixed now, the directory #gtx_edit() now also works for other tags. When publishing a page out of the Real Edit Mode using Aloha Editor failed (e.g. due to missing mandatory fields), no message was shown to the editor. This has been fixed now: a message will be shown to the editor and the page will stay in edit mode. REST API: Deleting a page would not work if it has missing contenttags or contenttags with missing values. The delete call would also report success on the delete operation in this case. When setting an object property for a localized folder in a channel and applying the change to all subfolders, the change also affected subfolders in the master channel. This has been fixed. Now, if an object-property-change is applied to all subfolders of a localized folder, then only localized subfolders in the same channel will be affected by the change. When setting the page language to a different language the language of the localized versions of the page was not updated. This has been fixed. Optional Manual Change Implementation of the tagtype for the FileLink plugin maybe has to be updated The Setup Guide of the Gentics Content.Node FileLink plugin did not explicitly state, that the part Sorting the items listed in the repository browser by name did not work and has been fixed now. In rare cases the publish process could fail with an error like “ERROR: com.gentics.api.lib.exception.NodeException: Action WRITE_CR was initiated for object 10002.4711.99 twice” due to conflicting entries in the publish queue. This has been fixed now. Workflows: An issue was fixed which prevented trash workflows for folders from being executed correctly. Previously a trash workflow would not be able to move folders into a trash folder. Deleting of folders was not possible when the workflow was enabled. The error first occurred in GCN 5.17.11 and 5.18.0. When changing the tagtype of a template tag, that is editable in pages, not all caches where cleared correctly after the tags in the pages were changed. This could cause subsequent errors. E.g. when editing a page afterwards, it could happen, that the page was stored with the original tagtype. This has been fixed now. Construct Editing: Modifying any construct property including description, keyname, parts caused all pages to be republished that utilized tags that were created using the construct. Only modifications to parts will now cause republishing of pages. Modifying all other properties including keyname and description will no longer cause publishing of pages. When migrating existing projects to Aloha Editor, live editable tagtypes that use a part like Some additional log entries were added to better log, when a template is modified. Also locking and unlocking pages will now be logged separately with new log actions “Lock“ and “Unlock”. Manual Change Aloha Link tagtype: A previous manual update of the tagtype “Aloha Link” caused a misbehaviour when adding a link. Breaks were inserted before and after links when saving a page. To perform the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. When disabling the IE7 Standards Mode, and editing pages using the old Live Editor, some incorrect CSS setting caused rendering problems for editable areas. The borders around editables containing multiple lines of content were not rendered correctly and the tag icon changed it‘s position when activating the editable. This has been fixed now. When editing a page using aloha editor in “real editor“ mode, saving the page (using the “Save“ button in the ribbon), saved the page, but did not create a new version. When clicking the “Cancel“ button in the ribbon afterwards, the last saved version of the page is restored, which is unexpected behaviour. This has been fixed now, when using the “Save“ button in the ribbon to save the page, a new version will now be created and clicking “Cancel” afterwards will no longer undo the changes, which were saved before. The update process has been changed to change the group of the PHP files to node_public, if the user node is member of that group. This fixes permission problems on systems that still use the second HTTP server for XNL modules. Translation permissions: A message will now be displayed when the translator has not enough permissions to translate a page in a different language. Previously the action was just silently aborted. Page Translate: In some cases a page property dialog with empty fields and no confirm button was shown when a user tried to translate a page. Additional permission checks were added in order to prevent this bug. The error messages now also contain information about the missing permissions. The gallery view was affected by the paging setting, but did not show the paging controls. Also the placement of the images in the gallery was wrong. This has been fixed now, the gallery will now show all images and will not use paging. When changing the name of a folder, without changing the publish directory, no check for duplicate publish paths will be done. Therefore, changing only the name is still possible, even if duplicate publish paths already exist. Page list: In some cases the top menu search menu was not being displayed. Additional role permission checks have been added in order to correctly determine the visibility of this menu entry. When pages, images or files cannot be moved due to naming conflicts, the error messages will now explicitly contain the names of the conflicting objects and their folders. Additionally, if the conflict arises in a channel (but not in the master node), the channel name will be contained in the error messages. Error messages will now be shown in a browser alert message, so they cannot be easily missed. Feature “publish_folder_startpage”: Fixed a bug where the language variants of start pages wouldn‘t be published. When a page is published using instant publishing, the language variants of the start page will also be published now. The Aloha.Editor version number was finally bumped from 0.26.6 to 1.0.0. This update will therefore use version 1.0.0 of Aloha.Editor. Version 1.0.0 does only contain the version update from 0.26.6 to 1.0.0 – No other changes were added to it. Fixed that the “Quickjump” didn‘t work anymore on the start page of Gentics Content.Node. When using a PostProcessor in a tagtype migration for a template, the template was not migrated although the job finished with success. This has been fixed now. When uploading new files or changing files, the uniqueness check for the filename (with publish directory) was not done case insensitively. This could cause creation of files for which the publish path only differed in case. This subsequently could cause problems in the frontend. The uniqueness check has been fixed now to be case insensitive. When uploading a new image/file and then directly clicking the file, editing it‘s object properties did not work (produced an SGB). This has been fixed now. Unnecessary output of WARN messages like “WARN TagPartType not filled, but is still rendered. (TagPartType is null, data inconsistency – invalid link to tag {tagClass:class com.gentics.contentnode.object.ContentTag} {tagId:0} {valueId:47110815})” in the publish log will be omitted now. In rare cases, the application server for Gentics Content.Node would not start properly due to an unexpectedly terminated initialization job, which the startup routine failed to detect. This has been fixed now. If an initialization job terminates, an exception will be logged and the application server will start normally. Loading images (path /folder/getFiles/{folderId}) or items (path /folder/getItems/{folderId}) using the Java REST API client failed with some deserialization errors. This has been fixed now. The result for the calls to /folder/getFiles/{folderId} and /folder/getItems/{folderId} will contain an additional property (@class) for each file or item, that specifies the Class to be used for deserialization in the Java REST API client. When a published page was republished without any changes, a log entry like “Create Major Version (updated version 9.0 to 9.0)” was written which suggested that a new version should have been created. In fact, when republishing an already published page without any changes will not create a new version and such log entries are incorrect and will not be written any more. The Time Management during a publish process will now be done earlier (before the initialization of the publish process) in it‘s own transaction. This fixes problems, where pages, that are published with “publish at” are possibly not published with the correct contents. Translating pages in the backend or with the REST-API wouldn‘t work when group channel restrictions were in use. Fixed and unified page filename handling for creation and translation, which incorrectly replaced some valid characters. When starting a Tagtype Migration process, a new background Thread is created, which is never removed. This has been fixed now. A PHP error within the autoupdate changelog mechanism was fixed. Previously this error could cause the changelog mechanism to abort the update process. The background job for synchronizing published versions of page variants sometimes causes an Exception on tomcat startup. This has been fixed. When a page was localized in a channel, the properties “languageset“ and “pagevariants“ were triggered for all language or page variants of the page in the master node and for all channels. This probably caused too many pages dirted, which subsequently caused too large publish processes. This has been fixed now, dirting of “languageset“ and “pagevariants” will now be done channel specific were possible. Sometimes importing a Page with an Overview that already exists on the system does not update the overview settings. This has been fixed. When modifying the html of a tag in a callback to “tag.rendered” (using the Gentics Content.Node Javascript API), the modified html was ignored. This has been fixed now. When modifying the html of a tag, it is necessary to note, that at least the root tag of the original html must be left untouched. When editing an overview for the first time after a new login, the list of selected entries will disappear after clicking back and next in the overview wizard. This has been fixed. Moving folder structures between channels did not work as expected. Objects contained in the moved folder structure possibly were not moved between the channels. This could result in inconsistent data, where inherited objects were located in local folders. This has been fixed now. Additionally, some additional checks for possible naming conflicts will be done, when moving folder structures between nodes. When moving large folder structures takes longer than some seconds, the move operation will now be continued in the background. The user will get a notification (via instant message), when the folder structure has been moved. Guides: Enhanced the FAQ page on how to enable the profiler. Channel sync: Fix javascript error occuring when pressing the buttons “Push to master“ or “Remove localization“. Error message: ”Uncaught TypeError: Cannot read property ‘focus‘ of undefined Fixed users being able to take inherited pages offline, even when they don‘t have access to the master node. When restoring a page version, tags where the tagtype has been deleted in the meanwhile also got restored. When trying to load this page afterwards the user would get an error message. The problem has been fixed by not restoring such tags anymore. When translating a page, the generated filename was not consistent with the generated filename of the original page. Updated overview tag part description. With Firefox the menu list in the template preview is displayed always with two columns instead of one. This has been fixed. An issue within the REST API was fixed which could lead to stalling mysql server connections. Ultimately this issue could result in ‘Too many connections‘ errors. Various issues in the scheduler task event view were fixed: The main Gentics Content.Node connection pool can now be configured. Deleting of a single page could fail under the following circumstances: The issue has been fixed now, deleting pages will now work under all circumstances. When using the feature publish_cache in multichannelling environments, it was possible that channel specific data was cached, which could cause incorrect rendering of pages. This has been fixed now. Additionally, rendering of tag.visible did not return the correct value when using publish_cache, which also has been fixed. GenticsImageStore paths were not correctly recognized when a CDATA XML Tag was used to wrap the URL. Example: CDATA[//some-thing.at.com/stop_pan_thing/GenticsImageStore/200/230/smart{fileName} ]] GenticsImageStore: On some occasions, when resizing a JPEG image with sRGB colorspace the resulting image has wrong colors. This has been fixed. Sometimes, when a successful multithreaded publish process was finalized, errors like “An already closed connction got into the pool.” would be logged (as FATAL errors), which did not indicate any real errors. The finalizing algorithm has been changed to avoid those error messages. Fetching some commonly used data during a publish process was done very iffenciently and has been improved. Added missing documentation to the PermResource, the resource for reading and writing permissions in the REST Api. Previously it was unclear how to get the folder and role permissions and how to read the permission bit strings in the response. This has been fixed. When a file was dirted and then deleted during the next publish run, the publish run possibly failed, when the file should be published into a Content Repository where the attribute binarycontent was a filesystem attribute. This has been fixed now, the behavior in such cases will now be the same as when the attribute binarycontent is no filesystem attribute. In some cases, due to incorrect tagmap data, the content repository synchronization during the publish process would detect changes in the content repository structure every time. This caused “changing” the structure on every publish run, which did not actually change anything, but just took some unnecessary time. This has been fixed now, the content repository structure will now only be modified if really necessary. Pages that were published into a multichannelling aware contentrepository during a regular publish process did not get the correct updatetimestamp set. As a result, caches were not cleared by syncchecking. This has been fixed now. When deleting tagtype parts a SGB error was thrown. This error occurred since GCN 5.16.0 and has now been fixed. The error only occured on systems that have been migrated to the new package structure with distribution Apache and PHP CURL support. The handling of “internal” datasources Tagtype fill: When editing a tagtype that has a “Select (multiple)“-part in the “Fill“ dialog, a broken error message appeared when saving the properties with “OK“. This happened on systems where GCN runs with PHP 5.3 or higher and has been fixed now. Error message: “A tag name contains invalid characters: Line: 1 Tag:”. If a content file has no file extension, then the meta attribute file.extension returned the file name instead of an empty string. This has been fixed. Manual Change Aloha Link Plugin: Links were not escaped correctly when inserted with the aloha link plugin. With this manual change you can place special characters in a link and it will be escaped according to html standards. To do the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. Some incorrect and unclear parts of the documentation of the Migration Tool have been improved: The documentation now states, that the Migration Tool is available for object property definitions, not for Tagtypes. Also the unclear german translation of the description of the checkbox to “apply a migration to all pages using the same template as this page” has been corrected. The handling of dirt events that affected many objects was done very inefficient, which could cause long processing times during which the publish process would not start. This has been fixed now, dirting is done more efficient now. The output generated by the function “Check data” for Content Repositories will now contain some detailed information about why objects are not supposed to be contained in the checked Content Repository. For users that are restricted to channels, sometimes the context menu in the folder tree was not shown for inherited folders in the channel due to an incorrect permission check. This occurred right after the login, before the user entered a specific node by clicking onto a folder in the folder tree. After entering a node and refreshing the folder tree, the context menu was shown correctly for all folders. This has been fixed now, the context menu will now be correct right from the start. The database connections for Content Repositories did no use connection pools. This caused many reconnects to the Content Repository databases when instant publishing is used. This has been changed now. Database connections to Content Repository databases will now be pooled (with very conservative settings). This means that connections will be kept alive and can be reused after the publish process is finished. When creating a page with non-ASCII characters in its name in the backend, the automatically created filename would sometimes be empty. When pages were moved to other folders, they were left in the “locked“ state, even if they were not locked before. Also when pages were copied, the copy was “locked”. Both issues have been fixed now, moving or copying pages will not lock them. Doubleclicking on the duplicate button when doing image manipulation could create two duplicates with the same file name. This has been fixed. Sorting the Queue by Node caused an SGB, which has been fixed now. The Apache Tomcat will automatically be updated to version 6.0.41 in order to secure various vulnerabilities. The date formatter imp that was removed in GCN Update 5.17.0 was added back to Gentics Content.Node. The documentation for the imp can be found in the Gentics Content.Node Guides GenticsImageStore: URLs inside tags in pages were not correctly recognized during the publish process. Dirting: Previously, when opening the properties of a folder and clicking “OK” without changing any values, all objects depending on this folder have been dirted and re-published. From now on this will only happen when one of the values changes. When using the copy_tags feature to copy & paste tags from one page into another, the new inserted tags would not get the edit buttons right away. It was necessary to save and reopen the page in edit mode to get the edit buttons for the copied tag. This has been fixed now, copied tags will immediately get the edit buttons. When using the feature omit_publish_table, changing and republishing pages caused excessive dirting. This has been fixed now. Some inperformant SQL queries that were used while versioning pages could cause long database locks. Those SQL queries have been fixed now. Fixed webapp startup issues: When triggered, the safety check for mappedglobalidsequence would prevent the detection of a new license key. In some configurations, the startup safety checks would not output any error message. Now, there‘s additional logging as well as output to stderr, in case something prevents the startup of the webapp. The webapp will now refuse to startup if no globalprefix is set and no valid license can be found. When creating page variants on a system using multichannelling, variants created in nodes (not channels) were also marked as belonging to a channel. This caused the “synchronisation” of page variants to fail: When a variant is modified and published, a new version containing the new content is supposed to be created for all page variants, which did not happen in these cases. This has been fixed now. The update will also correct the incorrect channel setting of the page variants. Missing page versions will be added and affected pages will be scheduled to be republished in the next publish run. When a page was scheduled to be published at a certain time in the future, and was then processed by a publish run with multithreaded publishing, the publishtimestamp that was written into the Content Repository was not the one from the publish process but from the time, the editor scheduled the publishing. This has been fixed now, the publishtimestamp written into the Content Repository will now be correct. The quickjump did not work as expected when using multichannelling: inherited pages in channels were not found and pages in master nodes were shown as result, even if the user was restricted see pages in channels only. Both issues have been fixed now. Fixed too strict permission check that would hide the “OK” button when editing a user. This way changing a user‘s group assignments directly from the user‘s edit view was not possible any more. Publishing to content repositories: Updatetimestamps are now created from wallclock time instead of from transaction time. This will mitigate portal cache consistency issues when instant publishing is used during a publish run. Manual Change Aloha Link Plugin: Links were not escaped correctly when inserted with the aloha link plugin. With this manual change you can place special characters in a link and it will be escaped according to html standards. To do the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. Setting permissions on custom tree entries did not work as expected and has been fixed now. Deleting a node could sometimes lead to database inconsistencies (leaving a node entry without its root folder). Those database inconsistencies would subsequently cause publish failures. The process of deleting nodes has been modified, so that no database inconsistencies can occur, even if the process itself is interrupted or fails. When publishing into a content repository that has instant publishing enabled, the publish process could fail with various errors thrown by the JDBC driver, which were caused by not-threadsafe usage of the database connection. This has been fixed now, access to the content repository database will now be properly synchronized. Localizing folders in a deep folder structure failed with an Exception. The Exception was thrown when the folder property “Directory” was more than 64 characters long. This has been fixed. Now folder paths can be 255 characters long. Implementations using the Datasource PartType did not work as expected. Dirting of dependent objects did not work, when tags containing a Datasource PartType were changed and doing imports of tags with Datasource PartTypes could cause Internal Errors. These errors have been fixed now. Possibly incorrect references to datasources in the database will automatically be corrected during the next initialization of Gentics Content.Node. Fixed multiple issues with roles: Group permission dialog would not display the assigned role count. Roles would not be assigned recursively to child objects in the Group permission dialog. All roles except one would be ignored most of the time if multiple roles are assigned to an object. The language shown in the page properties dialog was not the page‘s language, but the currently selected content language. This has been fixed now. The page‘s language will be shown now. If the page has no language set, the field will be empty. When using Roles to grant permissions on languages to users, the “translate“ role was not sufficient to create language variants of existing pages. This has been fixed now, users with the “translate“ role for a specific language are allowed to create translations (language variants of existing pages), whereas creation of new pages still requires the “create“ role (or the “create” group permission). Microsoft Internet Explorer 7 is no longer supported. Please update to Internet Explorer 8 or newer. Aloha Editor Change Summary Manual Change Java Project Structure Changes Various changes to the internal Gentics Content.Node project structure have been made. These changes might affect existing build setups that make use of the provided maven artifacts. The following libraries have been added: The following shared libraries have been removed: Manual Change Deprecation of the date formatter imp Optional Manual Change The feature “disableIE7StandardsMode” is now officially supported. If you have websites that rely on having the latest Internet Explorer document mode, you might want consider setting it to true. The publish_folder_startpage feature was added. With this feature it is possible to automatically publish the startpage of the parentfolder of a page that is published during a instant publishing run. Feature Overview New Rest API method to get External links inside a folder. With the new feature omit_publish_table turned on, pages that are not published into the filesystem will no longer be written into the publish table. This reduces the size of the backend database and increases the overall publish performance if not all nodes publish into the filesystem. Several performance optimizations for the publish process have been done: The REST Model for pages and templates has been extended to contain multichannelling information. Also the REST Model of Properties has been extended to support all existing PartTypes. See the Gentics Content.Node REST API Documentation for details. The new feature publish_inherited_source allows reusing the published source of the master page when publishing an inherited page into a channel. This might improve the publish performance, if checking for localization of the page‘s dependencies is faster than actually rendering the page. The REST API for templates has been extended with two new methods: See the REST API Documentation for details. The default pagesize for various lists has been set to 20 to increase system performance. Additional page size options have been added. It is now possible to select a page size of 100 and 250. Previously the default pagesize limit was set to unlimited. The new feature publish_cache improves the publish performance by caching page data. Please consult the Gentics Content.Node Documentation for details. The method TagAPI.parts() is introduced to allow one to enumerate a tag‘s parts. Pasting a link didn‘t mark it as Aloha Page link. This has been fixed. Gentics Image Store: Resizing an image produced an exception so the image did not resize and instead the original image was returned. This has been fixed. Using an apostrophe in a folder name would lead to a javascript error in the folder listings. Also, javascript escape sequences were interpreted by mistake. This has been fixed. A javascript error in the webdav (folder open) dialog was fixed. Internet Explorer 11 does no longer support opening of webdav folders. Instead webdav folders have to be opened manually now. The infotext in the webdav dialog was adapted. It is no longer possible to store files (or images) with empty filename using the properties dialog, the imagemanipulation2 or the REST API. Importing an object property definition containing an overview sometimes failed with an “Internal error”, because the export contained an invalid reference. This has been fixed now. New exports of object property definitions containing overviews can now be successfully imported. Some actions on tagtypes, like adding or removing a part did not change the editor and edittime of the construct itself. This has been changed now. Also log entries will now be added on all actions of constructs. Fixed the GCN JS API to enable it to recover after a JavaScript exception occurs with no ‘error-encountered‘ handler registered to. 2dotool integration: “Request translation” would log out the user immediately. When creating page variants on a system using multichannelling, variants created in nodes (not channels) were also marked as belonging to a channel. This caused the “synchronisation” of page variants to fail: When a variant is modified and published, a new version containing the new content is supposed to be created for all page variants, which did not happen in these cases. This has been fixed now. The update will also correct the incorrect channel setting of the page variants. Missing page versions will be added and affected pages will be scheduled to be republished in the next publish run. When a page was scheduled to be published at a certain time in the future, and was then processed by a publish run with multithreaded publishing, the publishtimestamp that was written into the Content Repository was not the one from the publish process but from the time, the editor scheduled the publishing. This has been fixed now, the publishtimestamp written into the Content Repository will now be correct. The quickjump did not work as expected when using multichannelling: inherited pages in channels were not found and pages in master nodes were shown as result, even if the user was restricted see pages in channels only. Both issues have been fixed now. Fixed too strict permission check that would hide the “OK” button when editing a user. This way changing a user‘s group assignments directly from the user‘s edit view was not possible any more. Publishing to content repositories: Updatetimestamps are now created from wallclock time instead of from transaction time. This will mitigate portal cache consistency issues when instant publishing is used during a publish run. Deleting a node could sometimes lead to database inconsistencies (leaving a node entry without its root folder). Those database inconsistencies would subsequently cause publish failures. The process of deleting nodes has been modified, so that no database inconsistencies can occur, even if the process itself is interrupted or fails. Localizing folders in a deep folder structure failed with an Exception. The Exception was thrown when the folder property “Directory” was more than 64 characters long. This has been fixed. Now folder paths can be 255 characters long. Implementations using the Datasource PartType did not work as expected. Dirting of dependent objects did not work, when tags containing a Datasource PartType were changed and doing imports of tags with Datasource PartTypes could cause Internal Errors. These errors have been fixed now. Possibly incorrect references to datasources in the database will automatically be corrected during the next initialization of Gentics Content.Node. The language shown in the page properties dialog was not the page‘s language, but the currently selected content language. This has been fixed now. The page‘s language will be shown now. If the page has no language set, the field will be empty. Manual Change Aloha Link Plugin: Links were not escaped correctly when inserted with the aloha link plugin. With this manual change you can place special characters in a link and it will be escaped according to html standards. To do the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. Setting permissions on custom tree entries did not work as expected and has been fixed now. Fixed multiple issues with roles: Group permission dialog would not display the assigned role count. Roles would not be assigned recursively to child objects in the Group permission dialog. All roles except one would be ignored most of the time if multiple roles are assigned to an object. When using Roles to grant permissions on languages to users, the “translate“ role was not sufficient to create language variants of existing pages. This has been fixed now, users with the “translate“ role for a specific language are allowed to create translations (language variants of existing pages), whereas creation of new pages still requires the “create“ role (or the “create” group permission). Pasting a link didn‘t mark it as Aloha Page link. This has been fixed. Using an apostrophe in a folder name would lead to a javascript error in the folder listings. Also, javascript escape sequences were interpreted by mistake. This has been fixed. A javascript error in the webdav (folder open) dialog was fixed. Internet Explorer 11 does no longer support opening of webdav folders. Instead webdav folders have to be opened manually now. The infotext in the webdav dialog was adapted. It is no longer possible to store files (or images) with empty filename using the properties dialog, the imagemanipulation2 or the REST API. Importing an object property definition containing an overview sometimes failed with an “Internal error”, because the export contained an invalid reference. This has been fixed now. New exports of object property definitions containing overviews can now be successfully imported. Some actions on tagtypes, like adding or removing a part did not change the editor and edittime of the construct itself. This has been changed now. Also log entries will now be added on all actions of constructs. Fixed the GCN JS API to enable it to recover after a JavaScript exception occurs with no ‘error-encountered‘ handler registered to. 2dotool integration: “Request translation” would log out the user immediately. Tagfill popup (Internet Explorer): fix automatic scroll to the bottom of the popup when editing a Tagfill. When opening the todo tool, the user was automatically logged out. This has been fixed now, the todo tool can now be used normally. Image Manipulation 2: Fixed manipulating images not working on certain systems with a webserver proxy that filters URL‘s for security and doesn‘t allow full URLs to be passed as URL parameter. When exporting an object that can have object tags (folder, template, page, image or file), only enabled object tags will be exported. This fixes the problem, that object property definitions need to be exported together with objects, although the object tag has never been used (filled) for the object. If removing pages or files during an incremental page import lasted longer than 5 seconds, an error was logged in the import log, and possibly not all removed files or pages were deleted in the CMS. This has been fixed now by increasing the timeout to a reasonable high number of seconds. When a tagtype is deleted, that was used by an object property, this could cause excessive dirting (delaying the publish process for a long time), even in the object property was not used by a large number of objects. This has been optimized now, deleting a tagtype will only cause a dirt event, if the tag that used the tagtype was enabled. When attributes in a multichannelling aware ContentRepository were made ‘optimized‘ manually, but the entries in table contentattribute were not removed, this could cause the problem that the value could not be changed, if the quick column was set to NULL, but the value in contentattribute was the correct one. quickjump: if a page exists but is not visible to a user and the user searches for the page name in the quickjump box, the system will try to access the page and an error message is shown. This has been changed to a “Page not found” message. When deleting a tagtype or object property definition takes longer than 5 seconds, the user will now be informed, that the process is continued in the background. When deleting object property definitions, dirting for deleted object tags will only be done for enabled object tags. A file descriptor leak has been discovered in the scheduler that could potentially eat up all available file descriptors for scheduled processes. This fix removes a leaked file descriptor of a lock file. If a page is moved to another node and taken offline before the next publishrun, then it will not be removed correctly from the source node. This has been fixed. Multichanneling: The order functionality within the list views (folders, files, pages, templates) did not work correctly when ordering the column “Master”. This issue is now resolved. Fixed an issue where role permissions were sometimes not loaded correctly and users had too little or too many permissions. Also, existing role permissions sometimes wouldn‘t show in the role editor and be deleted on save even if not modified. Fixed an issue where pages couldn‘t be listed in the backend if you only had permissions for a specific language using a role and the language had not yet been set. Tagtype migration: When doing a migration on an object property definition in the Administration, there somtimes occured a SGB error or a white page was shown. This has been fixed now. A bug in the page version restore was fixed. In some cases a version restore could create a new mappedglobalid record which conflicted with the existing one. This duplicate record could lead to import/export problems. In some cases an import of a page which would overwrite a page tag would recreate the tag without a value. The duplicate mappedglobalid records will automatically be purged. Please note that the purge process may a take while depending on your mappedglobalid size. Gentics Content.Node tree-view: When there were too many open folders, an error occurred so the tree-view was not loaded. An error was log when loading an inexistent php file (‘get_folder_tree.func.php‘). This error has been fixed. Multichanneling: When editing the value of a part type URL and the file/image is inside a localized folder, the displayed path name was wrong. contentfile-auto-offline: Previously, when a page contained an Image-URL for an Image in the same contentrepository, the target image file was not taken online automatically. This has been fixed. Fixed a NPE when trying to read role permissions from the database that have no permissions set for files. When uploading a file, the temporary file of the File-Upload-Manipulator was never deleted. This has been fixed. GenticsImageStore: jpeg resizing quality setting is not ignored when cropping. Validation feature: Fixed that some page properties and page tags/object properties weren‘t validated in the Rest API page/save request. This only affects GCN systems where the validation feature is enabled. Previously, a rollback of a Contentrepository transaction of a publish run could result in a hangup of the publish process. This has been fixed now. Improved the documentation for the Navigation Part Type Publishing: File names with ‘)‘ and ‘]‘ didn‘t work with the Gentics Image Store. GCN JS API / REST-API: Fixed page.preview() not working for pages in channels. When setting a startpage for a folder in the folder object properties a log entry is written. This log entry is missing, when doing the same via the context menu in the page list of a folder. Now both actions will produce the same log entry. An import would previously under certain circumstances delete a freshly imported value from a contenttag. These values are now imported correctly. linkBrowser: only channel nodes from the master node are displayed in the link Browser. The ‘Web adresse‘ regular expression now accepts ‘https://‘ URLs and network-path reference URLs (‘//‘). Occasionally, in Wiki-Edit-Mode, when clicking “edit” in the Real-Editor an error message was shown instead of the editing mask. During import, objects with translatable names or descriptions (Tagtypes, Parts,...) previously would have empty names or descriptions replaced by non-empty strings of other translations. Now, empty names or descriptions can be imported normally. Previously, Navigation parts would use and count pages that were not not yet published or already taken offline. They have been fixed to only use and count pages that are actually online. Information related to the Heartbleed openSSL security vulnerability Copying nodes: Fixed copying nodes with the user interface not correctly working. When copying a node, the copy would not appear in the users tree or node list because the permission cache was not refreshed. Email sending: Fixed GCN not setting the “Return-Path“ in some cases when “$MAILRETURNPATH” is specified in the configuration. This happened for example when someone took pages back into revision in the publish queue. When defining velocity macros in tag implementations, the macros were globally available and would be overwritten by macros defined in other tags but with the same name. This resulted in unexpected and random behavior if multiple macros with the same name were defined. The scope of inline defined macros has been changed to be local to the template, like documented in the Gentics Content.Node Guides. Multiple bugs concerning overviews have been fixed: An overview would be dirted if a matching object was added in a channel. A recursive overview of images would not be dirted if an image was added in a subfolder of a selected folder. An overview would not render objects created in the same channel, if there were no other dependencies of the page in that channel (as compared to the parent channel). Improved robustness of publish process A race condition that allowed the publish process to run multiple times in parallel has been removed. A potential deadlock in error handling during the initialisation phase of the publish process has been removed. When only a tagmap entry was modified for a ContentRepository, but no data was changed, the subsequent call to CRSync or MCCRSync would not synchronize this changed tagmap entry to the target CR. This has been fixed now, CRSync and MCCRSync will always synchronize modified tagmap entries, even if no actual data was changed. Fixed wrong permission checking when assigning/unlinking nodes from a CR in the administration. Previously the following permissions where checked: Now the following permissions are checked: File properties: Fixed a Javascript error that occured when opening the minibrowser and then clicking “ok“. When importing pages containing overviews over images, where the images have been selected manually, the references to the images were not set correctly, which resulted in empty overviews. This has been fixed now. Overview tags in pages: When editing new overview tags in pages the wizard starts with page 1 correctly. Previously it started with page 2 if any changes were made to the page. When importing a new node with a new object property definition, that is restricted to the node, the restriction was not set correctly. On the target system, the object property definition was available to all nodes. This has been fixed now. The way, older publish logs are archived was inefficient and has been improved. Before this fix, having many publish logs (e.g. because the publish process runs very often) which were very large could cause the archiving to take a very long time (up to several hours). An internal shutdown method for Gentics Content.Node has been fixed. Previously the shutdown command did not close the MySQL connection pool. Login mask: Fixed that the login is possible for LDAP-users that don‘t have a password set. Internal connections that use the IPv6 loopback interface are now also whitelisted by default. Previously IPv6 connections that used ‘::1‘ were not accepted by default. It is now possible to use the meta attribute “inherited” in implementations. For details, see the List of meta attributes in the Gentics Content.Node Guides. The documentation of the feature “cr_filesystem_attributes” has been enhanced to clarify that it is mandatory to repair the ContentRepository structures after switching on the feature, even if no filesystem attribute is used yet. Fixed a content repository consistency issue: If you moved a file between two nodes that publish to the same content repository, that has instant publishing enabled, it would get deleted from the contentrepository on the next publish run. When cancelling a page while editing it in Aloha Editor or using the REST API, the global ID of the page might change, which would cause unexpected behavior when the page was exported to another system, since the page would then have different global IDs on the systems and could not be overwritten by a subsequent export. This has been fixed now, the global IDs of pages will no longer change when cancelling editing. Pages that are already affected by changed global IDs need to manually be modified if necessary. File upload: Fixed image recognition for JPG images not correctly working in rare cases. Previously those images would not be recognized as image and the mimetype would be “application/octet-stream”. Now they are correctly recognized as images. When a page variant of an inherited page was created in a channel local folder, the master page could not be edited any more. Additionally, loading the master page over the REST API in the scope of the master with page variants attached resulted in an error. These errors have been fixed now. When rendering a channel local page for editing without specifying a nodeId, this failed because the page could not be loaded from the master channel. Now, the channel of the page will implicitly set and rendering will work as expected. This also affected frontend editing using Gentics Portal.Node Java, which did not work for channel specific pages. When using the new feature “resumable_publish_process” and publishing into non MCCR Content Repositories, the publish process could hang. This has been fixed now. Editing folder permissions: the page for viewing and editing the folder permissions was not displayed if the multichannelling feature was not activated. LDAP Login: Fixed that the LDAP login is not working on certain LDAP server configurations, when using the setting $LDAP_LOGIN_FIELDS[“dontuse_uniquememberattribute“] = true; in the GCN configuration. The problem only occured with LDAP servers that use the field “uid“ or others for the unique user identifier, instead of “cn”. Text area for the number of online users is wider so that it stays on a single line. The process of resizing images during a publish process with the GenticsImageStore has been modified to be more stable. Before this fix, images were fetched from the cache or resized (if not found in the cache) while subsequently reading data from the database. When many images needed to be resized this could take a long time and could cause the open database statement to run into a timeout. In these cases, the publish process would fail. Now, the database statement to get the information, which images are resized using the GenticsImageStore is processed before the actual image resizing takes place. Resizing the images may still take long, but will not cause a timeout in the database any more, so the likeliness of publish failures is reduced. Folder creation: A rare error has been fixed that occured when creating a folder. During the creation of the folder an SGB error occured and a “tag_duplicate“-error was logged. This happened when the mother folder had an object property set, that was created inside another object property. When an object property definition was added to folders afterwards, with the same keyword and “inheration” enabled, the tag duplication (for inherited tags) while creating a folder didn‘t work properly. On a rollback of a publishrun with instant publishing enabled, Gentics Content.Node would previously leave already published objects in the content repository, but delete their filesystem attributes. This behaviour has been corrected so that only the filesystem attributes of actually rolled back objects are deleted. The error handling for publishing into contentrepositories with multithreaded publishing has been improved. Certain inconsistencies in the database Time management will now also be done in nodes, that have publishing disabled. Pages affected from time management will be set offline or online due to time management, but those changes will still not be published as long as publishing is disabled for the node. This will enable time management in situations, where pages from nodes with publishing disabled are inherited into channels that have publishing enabled. Additionally, time management is more efficient now, which reduces the publishing time for every publish process. New Aloha Editor features: Aloha Editor now supports definitionlists. The format plugin has been extended to be able to remove a wider range of formattings. The list plugin now allows to apply classes to lists from a list of pre-rendered style definitions. The headerid plugin now allows you to use a translation table to transform headers into ids. Manual Change The flag-icons plugin is not shipped anymore and must be removed from the Aloha configuration in node.conf. Manual Change This changeset may require a manual change to your implementation. The version of jQuery UI that is used by the repository browser in the tagfill dialog has been upgraded from 1.8.1 to 1.9.1 . This has been done in order to fix a bug that prevented the minibrowser‘s left and right panels from being resizable in IE9 when $FEATURE[“disableIE7StandardsMode“] is set to “true”. The jQuery UI that is used in the tag fill is not supported as offical API by Gentics Content.Node . If any implemenation made use of it, those implementations may be affected by this change. Manual Change Gentics Portal.Node 2 removed Gentics Portal.Node 2, which has been deprecated years ago, was now removed from the Gentics Content.Node codebase. Please remove the $LOAD_MODULE[“portal”] setting from your node.conf. Optional Manual Change Multichannelling ContentRepository changes Optimized attributes of multichannelling aware content repositories are not stored in the table contentattribute any more. Since the data for optimized attributes is stored in quick columns of the table contentmap, the additionaly storage in the table contentattribute was redundant an unnecessary. Reducing the number of entries in the table contentattribute will reduce the memory consumption of the database and will improve the overall performance. Optional Manual Change Distribution binary support With this release you no longer have to use the included package Apache webserver, package PHP binaries and various utility binaries. The distribution tools, distribution Apache webserver and distribution PHP installation can be used instead. Thus support for distribution Apache webserver and PHP has been added to Gentics Content.Node. Note that the migrated package installation will no longer support the public apache site configuration thus legacy XNL Functions that make use of the public apache will no longer work. Additionally it is mandatory to migrate to the system MySQL Server when this manual change is being applied. Filenames in Gentics Content.Node will now be sanitized using a character transcription table that can be customized. The Aloha Editor headerids Plugin will also make use of this table to generate html ids from the header text content. Link-plugin: Link attribute ‘hreflang‘ can be edited for external links. For internal links, the hreflang is set to the default language of the page. When publishing into ContentRepositories using MS SQL Server, the newest Microsoft JDBC driver 4.0 is now supported. Removed unsupported context menu entries “in page changeable“ and “not in page changeable” from folder and template object property dialogs. /Node/bin/env.sh was updated in order to enable compatibility with standard linux distribution binaries. The behaviour of the multithreaded publish process regarding writing pages into Content Repositories can now be configured. It is now possible to set the group size and queue limit for the job queues that are processed in separate threads. See the Gentics Content.Node Guides for details about the multithreaded publish process. The performance of multithreaded publishing has been improved by reducing the number of SQL statements necessary to load the dependencies of pages and to load the data of the pages. The number of necessary SQL statements to publish objects into a multichannelling aware contentrepository has been reduced to optimize performance. Publishlogs now provide more fine grained information during the INITIALIZING and DIRTQUEUE phases of the publish process. When migrating a project from Live Editor to Aloha Editor, Table Tags will now be automatically migrated to inline editable tables. Additionally, it is possible to migrate other tagtypes to be edited inline with Aloha Editor as well. For a full description, please see the Aloha Editor Migration Guide in the Gentics Content.Node Guides. It is now possible to synchronize groups with restrictions to nodes when using SSO login with the REST API. See the Gentics Content.Node Guides for more details. The content maintenance now contains a new tool to reload the configuration. See the chapter about content maintenance in the guides for details. When boolean meta attributes are published as content repository attributes of type “Integer“, “true“ will now be published as 1 and “false“ will be published as 0. Before this fix, boolean meta attributes had to be manually converted when publishing as “Integer” attributes. The new Gentics Content.Node FileLink Plugin allows to implement a tagtype, that is used to render links to files with additional (not editable) information. See the Gentics Content.Node Guides for a detailed documentation. The start screen will now also show information about folders and files that need to be published. During a running publish process, the numbers show the remaining folders and files. Pages, folders and files now have a new meta attribute “ismaster”, which tells, whether the object is a master object, or a localized copy. See the Gentics Content.Node Guides for details about the available meta attributes. Added a new feature disable_instant_delete. It can be activated per node and will prevent instant publishing from deleting objects. The new feature “resumable_publish_process” allows to resume publish processes that were cancelled or failed due to errors. See the the Gentics Content.Node Documentation for details. Two new velocity directives #gtx_render and #gtx_edit can be used to render other tags or parts in velocity tags. See the ”Gentics Content.Node Guides+:http://www.gentics.com/Content.Node/guides/impl_using_velocity.html#render-directives for details. Sanitizing allows white spaces in filenames Selecting a item using the link browser, when targetregex has not be configured, caused the target attribute of the active anchor element to unexpectedly be overwritten to “framename”. This behavior has been fixed so that the target attribute will only change if targetregex is configured and matches the specified regular expression. When creating page variants on a system using multichannelling, variants created in nodes (not channels) were also marked as belonging to a channel. This caused the “synchronisation” of page variants to fail: When a variant is modified and published, a new version containing the new content is supposed to be created for all page variants, which did not happen in these cases. This has been fixed now. The update will also correct the incorrect channel setting of the page variants. Missing page versions will be added and affected pages will be scheduled to be republished in the next publish run. When a page was scheduled to be published at a certain time in the future, and was then processed by a publish run with multithreaded publishing, the publishtimestamp that was written into the Content Repository was not the one from the publish process but from the time, the editor scheduled the publishing. This has been fixed now, the publishtimestamp written into the Content Repository will now be correct. The quickjump did not work as expected when using multichannelling: inherited pages in channels were not found and pages in master nodes were shown as result, even if the user was restricted see pages in channels only. Both issues have been fixed now. Fixed too strict permission check that would hide the “OK” button when editing a user. This way changing a user‘s group assignments directly from the user‘s edit view was not possible any more. Publishing to content repositories: Updatetimestamps are now created from wallclock time instead of from transaction time. This will mitigate portal cache consistency issues when instant publishing is used during a publish run. Deleting a node could sometimes lead to database inconsistencies (leaving a node entry without its root folder). Those database inconsistencies would subsequently cause publish failures. The process of deleting nodes has been modified, so that no database inconsistencies can occur, even if the process itself is interrupted or fails. Implementations using the Datasource PartType did not work as expected. Dirting of dependent objects did not work, when tags containing a Datasource PartType were changed and doing imports of tags with Datasource PartTypes could cause Internal Errors. These errors have been fixed now. Possibly incorrect references to datasources in the database will automatically be corrected during the next initialization of Gentics Content.Node. The language shown in the page properties dialog was not the page‘s language, but the currently selected content language. This has been fixed now. The page‘s language will be shown now. If the page has no language set, the field will be empty. Manual Change Aloha Link Plugin: Links were not escaped correctly when inserted with the aloha link plugin. With this manual change you can place special characters in a link and it will be escaped according to html standards. To do the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. Setting permissions on custom tree entries did not work as expected and has been fixed now. Fixed multiple issues with roles: Group permission dialog would not display the assigned role count. Roles would not be assigned recursively to child objects in the Group permission dialog. All roles except one would be ignored most of the time if multiple roles are assigned to an object. When using Roles to grant permissions on languages to users, the “translate“ role was not sufficient to create language variants of existing pages. This has been fixed now, users with the “translate“ role for a specific language are allowed to create translations (language variants of existing pages), whereas creation of new pages still requires the “create“ role (or the “create” group permission). Pasting a link didn‘t mark it as Aloha Page link. This has been fixed. Using an apostrophe in a folder name would lead to a javascript error in the folder listings. Also, javascript escape sequences were interpreted by mistake. This has been fixed. A javascript error in the webdav (folder open) dialog was fixed. Internet Explorer 11 does no longer support opening of webdav folders. Instead webdav folders have to be opened manually now. The infotext in the webdav dialog was adapted. It is no longer possible to store files (or images) with empty filename using the properties dialog, the imagemanipulation2 or the REST API. Importing an object property definition containing an overview sometimes failed with an “Internal error”, because the export contained an invalid reference. This has been fixed now. New exports of object property definitions containing overviews can now be successfully imported. Some actions on tagtypes, like adding or removing a part did not change the editor and edittime of the construct itself. This has been changed now. Also log entries will now be added on all actions of constructs. Fixed the GCN JS API to enable it to recover after a JavaScript exception occurs with no ‘error-encountered‘ handler registered to. 2dotool integration: “Request translation” would log out the user immediately. Tagfill popup (Internet Explorer): fix automatic scroll to the bottom of the popup when editing a Tagfill. When opening the todo tool, the user was automatically logged out. This has been fixed now, the todo tool can now be used normally. Image Manipulation 2: Fixed manipulating images not working on certain systems with a webserver proxy that filters URL‘s for security and doesn‘t allow full URLs to be passed as URL parameter. When exporting an object that can have object tags (folder, template, page, image or file), only enabled object tags will be exported. This fixes the problem, that object property definitions need to be exported together with objects, although the object tag has never been used (filled) for the object. If removing pages or files during an incremental page import lasted longer than 5 seconds, an error was logged in the import log, and possibly not all removed files or pages were deleted in the CMS. This has been fixed now by increasing the timeout to a reasonable high number of seconds. When a tagtype is deleted, that was used by an object property, this could cause excessive dirting (delaying the publish process for a long time), even in the object property was not used by a large number of objects. This has been optimized now, deleting a tagtype will only cause a dirt event, if the tag that used the tagtype was enabled. quickjump: if a page exists but is not visible to a user and the user searches for the page name in the quickjump box, the system will try to access the page and an error message is shown. This has been changed to a “Page not found” message. When deleting a tagtype or object property definition takes longer than 5 seconds, the user will now be informed, that the process is continued in the background. When deleting object property definitions, dirting for deleted object tags will only be done for enabled object tags. A file descriptor leak has been discovered in the scheduler that could potentially eat up all available file descriptors for scheduled processes. This fix removes a leaked file descriptor of a lock file. If a page is moved to another node and taken offline before the next publishrun, then it will not be removed correctly from the source node. This has been fixed. Multichanneling: The order functionality within the list views (folders, files, pages, templates) did not work correctly when ordering the column “Master”. This issue is now resolved. Fixed an issue where role permissions were sometimes not loaded correctly and users had too little or too many permissions. Also, existing role permissions sometimes wouldn‘t show in the role editor and be deleted on save even if not modified. Fixed an issue where pages couldn‘t be listed in the backend if you only had permissions for a specific language using a role and the language had not yet been set. Tagtype migration: When doing a migration on an object property definition in the Administration, there somtimes occured a SGB error or a white page was shown. This has been fixed now. A bug in the page version restore was fixed. In some cases a version restore could create a new mappedglobalid record which conflicted with the existing one. This duplicate record could lead to import/export problems. In some cases an import of a page which would overwrite a page tag would recreate the tag without a value. The duplicate mappedglobalid records will automatically be purged. Please note that the purge process may a take while depending on your mappedglobalid size. An error was log when loading an inexistent php file (‘get_folder_tree.func.php‘). This error has been fixed. Multichanneling: When editing the value of a part type URL and the file/image is inside a localized folder, the displayed path name was wrong. contentfile-auto-offline: Previously, when a page contained an Image-URL for an Image in the same contentrepository, the target image file was not taken online automatically. This has been fixed. Fixed a NPE when trying to read role permissions from the database that have no permissions set for files. When uploading a file, the temporary file of the File-Upload-Manipulator was never deleted. This has been fixed. GenticsImageStore: jpeg resizing quality setting is not ignored when cropping. Validation feature: Fixed that some page properties and page tags/object properties weren‘t validated in the Rest API page/save request. This only affects GCN systems where the validation feature is enabled. Previously, a rollback of a Contentrepository transaction of a publish run could result in a hangup of the publish process. This has been fixed now. Improved the documentation for the Navigation Part Type Publishing: File names with ‘)‘ and ‘]‘ didn‘t work with the Gentics Image Store. GCN JS API / REST-API: Fixed page.preview() not working for pages in channels. When setting a startpage for a folder in the folder object properties a log entry is written. This log entry is missing, when doing the same via the context menu in the page list of a folder. Now both actions will produce the same log entry. An import would previously under certain circumstances delete a freshly imported value from a contenttag. These values are now imported correctly. linkBrowser: only channel nodes from the master node are displayed in the link Browser. The ‘Web adresse‘ regular expression now accepts ‘https://‘ URLs and network-path reference URLs (‘//‘). Occasionally, in Wiki-Edit-Mode, when clicking “edit” in the Real-Editor an error message was shown instead of the editing mask. During import, objects with translatable names or descriptions (Tagtypes, Parts,...) previously would have empty names or descriptions replaced by non-empty strings of other translations. Now, empty names or descriptions can be imported normally. Previously, Navigation parts would use and count pages that were not not yet published or already taken offline. They have been fixed to only use and count pages that are actually online. Information related to the Heartbleed openSSL security vulnerability Copying nodes: Fixed copying nodes with the user interface not correctly working. When copying a node, the copy would not appear in the users tree or node list because the permission cache was not refreshed. Email sending: Fixed GCN not setting the “Return-Path“ in some cases when “$MAILRETURNPATH” is specified in the configuration. This happened for example when someone took pages back into revision in the publish queue. When defining velocity macros in tag implementations, the macros were globally available and would be overwritten by macros defined in other tags but with the same name. This resulted in unexpected and random behavior if multiple macros with the same name were defined. The scope of inline defined macros has been changed to be local to the template, like documented in the Gentics Content.Node Guides. Multiple bugs concerning overviews have been fixed: An overview would be dirted if a matching object was added in a channel. A recursive overview of images would not be dirted if an image was added in a subfolder of a selected folder. An overview would not render objects created in the same channel, if there were no other dependencies of the page in that channel (as compared to the parent channel). Improved robustness of publish process A race condition that allowed the publish process to run multiple times in parallel has been removed. A potential deadlock in error handling during the initialisation phase of the publish process has been removed. When only a tagmap entry was modified for a ContentRepository, but no data was changed, the subsequent call to CRSync or MCCRSync would not synchronize this changed tagmap entry to the target CR. This has been fixed now, CRSync and MCCRSync will always synchronize modified tagmap entries, even if no actual data was changed. Fixed wrong permission checking when assigning/unlinking nodes from a CR in the administration. Previously the following permissions where checked: Now the following permissions are checked: File properties: Fixed a Javascript error that occured when opening the minibrowser and then clicking “ok“. When importing pages containing overviews over images, where the images have been selected manually, the references to the images were not set correctly, which resulted in empty overviews. This has been fixed now. Overview tags in pages: When editing new overview tags in pages the wizard starts with page 1 correctly. Previously it started with page 2 if any changes were made to the page. When importing a new node with a new object property definition, that is restricted to the node, the restriction was not set correctly. On the target system, the object property definition was available to all nodes. This has been fixed now. The way, older publish logs are archived was inefficient and has been improved. Before this fix, having many publish logs (e.g. because the publish process runs very often) which were very large could cause the archiving to take a very long time (up to several hours). An internal shutdown method for Gentics Content.Node has been fixed. Previously the shutdown command did not close the MySQL connection pool. Login mask: Fixed that the login is possible for LDAP-users that don‘t have a password set. Internal connections that use the IPv6 loopback interface are now also whitelisted by default. Previously IPv6 connections that used ‘::1‘ were not accepted by default. The documentation of the feature “cr_filesystem_attributes” has been enhanced to clarify that it is mandatory to repair the ContentRepository structures after switching on the feature, even if no filesystem attribute is used yet. Fixed a content repository consistency issue: If you moved a file between two nodes that publish to the same content repository, that has instant publishing enabled, it would get deleted from the contentrepository on the next publish run. When cancelling a page while editing it in Aloha Editor or using the REST API, the global ID of the page might change, which would cause unexpected behavior when the page was exported to another system, since the page would then have different global IDs on the systems and could not be overwritten by a subsequent export. This has been fixed now, the global IDs of pages will no longer change when cancelling editing. Pages that are already affected by changed global IDs need to manually be modified if necessary. File upload: Fixed image recognition for JPG images not correctly working in rare cases. Previously those images would not be recognized as image and the mimetype would be “application/octet-stream”. Now they are correctly recognized as images. When a page variant of an inherited page was created in a channel local folder, the master page could not be edited any more. Additionally, loading the master page over the REST API in the scope of the master with page variants attached resulted in an error. These errors have been fixed now. When rendering a channel local page for editing without specifying a nodeId, this failed because the page could not be loaded from the master channel. Now, the channel of the page will implicitly set and rendering will work as expected. This also affected frontend editing using Gentics Portal.Node Java, which did not work for channel specific pages. Editing folder permissions: the page for viewing and editing the folder permissions was not displayed if the multichannelling feature was not activated. LDAP Login: Fixed that the LDAP login is not working on certain LDAP server configurations, when using the setting $LDAP_LOGIN_FIELDS[“dontuse_uniquememberattribute“] = true; in the GCN configuration. The problem only occured with LDAP servers that use the field “uid“ or others for the unique user identifier, instead of “cn”. Text area for the number of online users is wider so that it stays on a single line. The process of resizing images during a publish process with the GenticsImageStore has been modified to be more stable. Before this fix, images were fetched from the cache or resized (if not found in the cache) while subsequently reading data from the database. When many images needed to be resized this could take a long time and could cause the open database statement to run into a timeout. In these cases, the publish process would fail. Now, the database statement to get the information, which images are resized using the GenticsImageStore is processed before the actual image resizing takes place. Resizing the images may still take long, but will not cause a timeout in the database any more, so the likeliness of publish failures is reduced. Folder creation: A rare error has been fixed that occured when creating a folder. During the creation of the folder an SGB error occured and a “tag_duplicate“-error was logged. This happened when the mother folder had an object property set, that was created inside another object property. When an object property definition was added to folders afterwards, with the same keyword and “inheration” enabled, the tag duplication (for inherited tags) while creating a folder didn‘t work properly. On a rollback of a publishrun with instant publishing enabled, Gentics Content.Node would previously leave already published objects in the content repository, but delete their filesystem attributes. This behaviour has been corrected so that only the filesystem attributes of actually rolled back objects are deleted. The error handling for publishing into contentrepositories with multithreaded publishing has been improved. Certain inconsistencies in the database Time management will now also be done in nodes, that have publishing disabled. Pages affected from time management will be set offline or online due to time management, but those changes will still not be published as long as publishing is disabled for the node. This will enable time management in situations, where pages from nodes with publishing disabled are inherited into channels that have publishing enabled. Additionally, time management is more efficient now, which reduces the publishing time for every publish process. Updated the feature overview guides and added the missing features: Also, the list of deprecated features has been updated with: When subscribing to the event channel ‘tag.rendered‘ or ‘page.rendered‘ in the Gentics Content.Node JavaScript API, the handlers were not called when inserting new tags and the insertion failed (tag was not inserted) without any visible error messages. These errors have been fixed now, when inserting a new tag, the handler for the channel ‘tag.rendered‘ will be called and insertion will succeed. When opening a page for editing with Aloha Editor, the toolbar entries to insert new tags into editables are created asynchronously. In cases, where this takes longer and the editor activates an editable before the initialization is done, a wrong set of icons was shown. This has been fixed now. If an editor activates an editable before the tag insert icons are initialized, a “loading” icon will be shown in the toolbar as placeholder for the tag insert menu. When the the tag insert icons are ready to be used, the placeholder will immediately be replaced with the tag insert icons. When user assignment to a group with the permission to modify tagtypes of several nodes was restricted to only some of that nodes, the list of construct did not always show the tagtype icons accordingly (icons for tagtypes that are not editable by the user should be displayed greyed out). This has been fixed now, so the icons will always show the editing permissions correctly. Follow-up from Bugfix RT57627. When a Page is imported and no weekdays are set for per-weekday-publishing it automatically sets all weekdays. Since GCN 5.15.8 all weekdays are set for per-weekday-publishing by default. This fixes importing a page from a system prior 5.15.8, where pages would appear online if no weekday was set for per-weekday-publishing. Multiple fixes/enhancements for the GCN fileuploader: An broken i18n translation string was fixed in the User administration. The broken translation caused an input error when a new user was being added. This issue has now been resolved. A bug in the File Upload Manipulator was fixed. Previously the “fileId” property was not set in the request to the FUM script. This issue has now been resolved. Internet Explorer 11 failed to be recognized as browser that is compatible with Live Editor, therefore the Live Editor was deactivated when using Internet Explorer 11. This has been fixed now. Part types: Fixed some tag part types not having a “cnTagPart_“ HTML class set. This has been added for the following types now: Nodes having updates of filesystem/ContentRepository disabled were not rendered italic in the content maintenance dialog. This has been fixed now. Previously, the purgeversions job would corrupt the page cache and a subsequent “Page Cancel” on a corrupted page would revert it to its first recorded version. This has been fixed now. The created white spaces at the beginning and the end of inline tags are now bein removed. To be able to set the caret after inline blocks, empty ‘span‘ elements are added at the beginning and the end of all inline blocks. When saving the page, these elements were saved too. With this fix these ‘span‘ are ephemeral and are deleted once the page is saved. These ‘span‘ elements are also removed if the inline blocks are removed. The message count in the top right corner had a bug that caused it to always be 0. It has been fixed to show the current number of unread messages of the user. Page import: Fixed links sometimes not being rendered correctly when publising the pages during import. The links were published as static links (like they have not been transformed), however in the page preview it was rendered correctly. Now when using instant publishing, links will probably be rendered as “#” first (when the target page does not exist yet and will be imported later), but with the next publish run they will be rendered correctly. Publish Queue: Fixed SGB error occuring, when trying to publish multiple pages at once. This error only occured when you went straight to the publish queue without clicking on a folder first. Fixed the permissions check when moving a folder into another folder. The user needed the “create File“ permission on the target folder and the “create Folder” permission was ignored. Fixed a database consistency problem that occured whenever a master folder with localizations was moved inside a channel node. Previously, Gentics Content.Node would not publish pages from a channel in the filesystem, if the master node has either updates disabled or publishing into filesystem disabled. Now it will correctly publish as indicated in the properties of the channel node. When pushing pages to master nodes using the channel synchronization, pushing of pages will be prevented, if they use local templates (that are not available in the master node). The user will receive a notification about the inability to push pages due to local templates. In the list of scheduler jobs, some execution plans of jobs were not readable in the tooltip due to css styling issues. This has been fixed now. When a page in the master node links to another object (file, image, page or folder) that exists locally in a channel and the source page is rendered in the master node, the link will be rendered as empty (#) now. Before this fix, the URL to the channel local page was rendered, which resulted in a dead link. Gentics Content.Node now fails earlier if it detects common serious problems with GlobalID generation. (e.g. if you accidentally reset globalidsequence, import different objects with identical GlobalIDs or try to generate GlobalIDs with a NULL globalprefix) When the name of a node was changed using the backend UI, dependent objects were not dirted. This has been fixed now, changing the node name will now correctly trigger object dirting. FileUploadManipulator: Fixed the “folder” object not being sent in the json script request object. See the FUM documentation for more information. Page versions: Fixed data inconsistencies in the database table (duplicate data in nodeversion table) caused by users double clicking on the publish link. Manual Change Server JRE Update A jvm bug was discovered that caused OutOfMemory errors due to non garbage collected image data. The documentation about the publish process has be reorganized and enhanced. A bug in the migration feature was fixed. In some cases the migration of pages changed the page status to ‘being edited‘. This issue only occurred for pages that used templates that were modified recently. Additionally the logging of the migration process was enhanced. $cms.rendermode.frontend will now be set to true when rendering a page using the preview() method. This makes the flag consistent with the fact that links are rendered in frontend mode in previews. When saving or importing a template, a NullPointerException would sometimes be thrown if the containing folder of the template has been deleted. Now you can also handle templates where the containing folder is deleted. A behaviour in IE caused fields to remain greyed out in the tagfill dialogue. When clicking the “display content” checkbox the area should change. The behaviour was fixed for IE. The performance of rendering statistics in the maintenance dialog has been improved by around 50% on systems with many nodes. Various small fixes concerning per-weekday publishing in timemanagement. Previously, per weekday publishing only worked with a start time set. Now it works unconditonally. Previously, page/load REST-API calls would return time management information with weekdays initialized to false if a start time was not set, now they are more intuitively initialized to true. When using the REST API to create a page, file or folder in a folder that exists locally in a channel without specifying a nodeId, the object was created in the master node, but could never be seen in the master node, because its folder did not exist in the master node. This has been changed now, if no nodeId is specified in the request, the object will be created in the folder‘s channel. If an invalid nodeId is specified (nodeId of a channel, in which the specified folder is not visible), the request will fail now. A potential php out of memory error has been fixed in the maintenance dialog. File upload: The description field in the “New -> File / Image” dialog has been removed. It was confusing for some users that the description was only set for files that were added/uploaded afterwards. The way the changelog will be presented in the autoupdate dialog has been changed. Previously all changelog entries would be shown in the changelog dialog. Starting with the next release only the new changelog entries will be shown. Additionally the way how the changelog must be confirmed was changed. It is now mandatory to confirm each manual change. Permission checking for translation was updated, so that edit rights are not required anymore for the source language of a translation. A NullPointerException that sporadically happens if a dependency gets deleted while the publishing process is running has been fixed. Live URLs: Fixed icons not being displayed anymore because the image is broken. When using the tagfill dialog via frontend editing for uploading a new file or image into a page in a channel, the new file or image was not uploaded to the page‘s channel, but to the master node instead. This has been changed now, new files or images uploaded in the tagfill dialog will now be created in the page‘s channel. A bug has been fixed, that prevented instant publishing of new folders, that were imported using the page import. When importing a folder but not the templates, which are assigned to the folder on the source system, the templates will now be assigned to the folder on the target system, if the templates already exist on the target system. Before this fix, templates were only assigned to folders, if the templates were imported. Previously, certain filenames of pages could not be uniquified automatically. This has been known to cause problems with e.g. imports. The code has been changed to allow for more filenames to be uniquified automatically. Fileuploader: Enhanced the mimetype detection of uploaded Files, mimetypes in container formats are now correctly recognized. Previously, a Microsoft Office .docx document was recognized as application/zip because the container is actually a zip. It is now recognized as “application/vnd.openxmlformats-officedocument.wordprocessingml.document”. Instant publishing a page that uses XNL functions will no longer hang when there is a concurrent publish process that uses XNL functions. A bug in the migration feature was fixed. Previously the tagtype migration changed the status of offline pages to being edited. This issue only affected the offline pages within migration jobs. In some cases a Gentics Content.Node Import could cause an exception directly after restart of the Apache Tomcat Server. The exception was related to the permission handling. The initialization of the permissions has been altered to fix this issue. Since a recent Chrome Update, the first column with the checkbox in GCN lists (pages in folders, scheduler, etc.) was cut. This is fixed now. Previously, when moving files in the backend, the permission check on possible target folders was not performed correctly. This has been fixed now. Previously, some templates found in recursive searches could not be displayed even if the user had permission to do so. This has been fixed now. An additional info text has been added to the keyword field in the creation dialog for object properties, tagtypes and tagtype parts. The info text will notify the user that special characters inside the keyword may cause problems when those element are being referenced within an tagmap mapping. When deleting folders, localized copies of templates linked to that folder were deleted, regardless of whether the (master) template was still linked to other folders or used in pages. This bug, which was introduced in Gentics Content.Node 5.13.25, 5.14.13 and 5.15.0 has been fixed now. Removing of objects from a multichannelling aware contentrepository with instant publishing did not work. The objects were removed at the next publish run. This has been fixed now, when instant publishing is enabled, objects will be immediately be removed unless more than one object is deleted at once. Importing of localized templates always created a conflict due to missing target folder, if the localized template did not yet exist on the target system. Because of this, it was impossible to successfully finish the import. This has been fixed now. For localized templates, no check for target folders is done, because localized templates are always linked to the same folders as their masters. When files in the CMS lost their binary content (or were incompletely created without binary content), the publish process failed (due to missing binary data). The display of such files in the backend was inconsistent and it was not possible to delete such files to resolve the publishing error by using the backend. This has been fixed now, broken files that cause the publish process to fail will now be shown in the backend specially marked (with an alert icon and in red) and it is possible to delete them. Additionally, it is now possible to search broken files using either the extended search in the backend or the REST API. The SQL statements used to find reusable data files for filesystem attributes in multichannelling aware contentrepositories were inperformant and have been improved. The GCNJSAPI has been fixed to work as documented when you try to get or set a value of a “Tag (page)” part. Documentation on this has been clarified, too. Inherited content and properties are rendered in REST-API ‘render‘ call (only localized pages). When calling /rest/page/render/{id} now it is possible to get the inherited content and the inherited properties when the parameter ‘inherited‘ is set to true. The response then will add 2 new properties: Enhanced the permission page for folders (Accessed through the folders context menu) The permissions are now directly shown for all groups for the currently selected folder. When using small browser windows (e.g. on systems with low resolutions), some data shown on the startpage of the CMS could overlap each other. This has been fixed now. If the window is too small to show the info boxes side by side the boxes will be shown one on top of the other. A bug in the scheduler view was fixed. Previously no error message was being displayed when the user was trying to delete a scheduler task that still got tasks that depended upon it. This issue has now been resolved. On some systems the Regex.Admin view did not display properly. A security check prevented the correct rendering of the view. The check has been adapted and the view will now render correctly. When part of type “URL (Page)“ was set to be required in the tagtype, the tagtype itself could not be filled without providing a default value for that part. This behaviour was different than the behaviour for other parts (e.g. type “Text”) where the part only has to be filled for tags, but not for the tagtype itself. The behaviour has been changed now to be consistent for all part types: If a part is required, it still can be left empty for the tagtype, but has to be filled in tags (e.g. in pages). Pausing the scheduler could take a very long time due to an inperformant SQL statement. This has been fixed now. A minor issue in the autoupdate feature was fixed. Additional protection checks were added to prevent multiple autoupdate invocations. When selecting elements for an overview using the repository browser, the order of the already selected elements was not always shown consistently. This has been fixed now. When loading the binary contents of a file via the REST API by using /rest/file/content/load/{id} the response always had the ‘Content-Type‘ ‘application/octet-stream‘. This has been changed now, the response to /rest/file/content/load/{id} will now have the correct ‘Content-Type‘ set. When writing pages into the contentrepositories was slower than rendering the pages, the internal job queues could grow very big, which could cause memory problems. This has been fixed now. If one of the queue exceeds the limit of 1000 pages, no more pages will be rendered (and put into the queue), until the queue is below the limit. Previously, when an error occured while requesting a page from Tomcat (404 or 500), the Tomcat version number and a detailed message was shown. That information is now hidden (a static error page is shown). Detailed error output can be found in the log files. Fixed security issue that could possibly allow someone to take over your user account by sending you an URL and doing social engineering. Rest API: Removed the “description“ and “login” field for all responses that return user objects (ie. creator and author) However, methods in the UserResource will still output those two fields for user objects. When migrating tags from a tagtype that contained non-editable parts using the tagtype migration tool, the filled value of the non-editable part in the source tagtype was removed, which should not happen. This has been fixed now. When migrating tags the source and target tagtypes are not changed. When the action “check data“ or “repair data“ for a ContentRepository was started, the status changed to “Running“, even though the job was actually queued (along with other dirt or maintenance events or even the publish process). This has been changed now. The status will now show “Queued“ as long as the job is in the Queue and will only switch to “Running“ when the job really is started. Additionally, queued ContentRepository jobs will now be shown as “ContentRepository Maintenance Action“ instead of “Dependency Calculation” in the maintenance dialog. Moving of inherited or localized folders is not allowed, because they must be moved in their master node. If an editor tried to move a localized or inherited folder, nothing happened, but the editor got no information telling why. This has been fixed now: If an editor tries to move an inherited or localized folder, an information will be displayed that this is not possible (similar to moving pages, images or files). When editing tags as blocks using Aloha Editor and the tagtype implementation contained script tags and a jQuery version >= 1.9.0 was used, the script tags were replaced by some random numbers when the tag was re-rendered in the page after being modified using the tagfill dialog. These numbers were not saved to the page and did not affect the published content of the page, but were just shown while editing the page. This has been fixed now, re-rendering tags containing script tags will now also work with jQuery versions >= 1.9.0. When creating folder overviews by manually selecting the folders and having the “recursive“ flag activated, the subfolders were not added, if the feature multichannelling was activated. This has been fixed now, manual folder overviews with “recursive” activated will now render like expected. Documented tag icon rendering for node style syntax. When pages were dirted due to changed dependencies, this was not logged any more. This has been fixed now: when a page is dirted, an entry in the logcmd table will be made. Previously, if you translated a page using the page/translate REST-API call, it would create excessive language versions of the same language if the master page was not located in a master node. Now, the page/translate call will not create multiple language variants of the same language any more. The dirting mechanism has been slightly changed to avoid changes to the page table. This will avoid unnecessary locks of the page table that could cause errors while pages are edited during a long running dirt process. Ordering the file or image list by file size works now correctly. Diagonal resizing in the MiniBrowser works properly now. The diagonal resizing region was very small and therefore very difficult to select. Sending messages to groups using the GCN Javascript API did not work at all and has been fixed. Multichannelling: Fixed the mother_obj_id of a folder not getting updated in the CR when the mother folder gets localized. The action “Delete (only this language)“ on pages has been removed for nodes with no languages assigned, for it does nothing. You can use “Delete (all languages)“ instead. For pages that have no language set, although the node has languages assigned, the action “Delete (only this language)” will now delete the page. Email sending: Fixed deleted user receiving notification emails from GCN Now deleted users don‘t receive notification emails anymore. Executing the command ‘Change Template‘ on page variants failed with an error, which has been fixed now. When changing the template for multiple pages at once, the pages will now be processed one by one so changes to every single page will now be visible immediately. When resizing images during a publish run using the GenticsImageStore, some file handles were not closed. This subsequently could cause publish run failures caused by a “too many open files” error. This has been fixed now, file handles will now immediately be closed after usage. Manual Change Permission settings, that were set on channels (root folders of channels) will not be effective any more. Permission settings on channels will now always be inherited from the master node, even for the root folder of the channel. In order to restrict user access to specific channels, the assignment of the user to the group granting this permissions has to be restricted to the channels. Improvements have been to the repository browser UI. The way that notifications are shown when an item is selected with the resopsitory browser has also been be replaced with a better implemenation, and improved UI. The performance for checking permissions The following meta attributes have been added for Velocity and the node notation: Check out the documentation for more information. The error log now shows all errors – displaying errors as “internal errors” has been removed. Also, additional data like the request query string and the user is displayed if available. Various enhancements have been made to the repository browser. Resizing the repository browser now works. The permission system has been enhanced to allow restricting user-group assignments to specific nodes/channels. This allows granting permissions to specific channels, without granting the permissions to other channels or the master node of the same channel structure. The feature “always_localize” has been introduced. It allows you to skip the dialogue that asks, whether Gentics Content.Node should localize an inherited object before editing or just edit the inherited object. If it is skipped, the default answer is to localize. If the feature is enabled in your node.conf, You can configure it separately for every node in the Node Features menu. When a file was dirted and then deleted during the next publish run, the publish run possibly failed, when the file should be published into a Content Repository where the attribute binarycontent was a filesystem attribute. This has been fixed now, the behavior in such cases will now be the same as when the attribute binarycontent is no filesystem attribute. In some cases, due to incorrect tagmap data, the content repository synchronization during the publish process would detect changes in the content repository structure every time. This caused “changing” the structure on every publish run, which did not actually change anything, but just took some unnecessary time. This has been fixed now, the content repository structure will now only be modified if really necessary. Pages that were published into a multichannelling aware contentrepository during a regular publish process did not get the correct updatetimestamp set. As a result, caches were not cleared by syncchecking. This has been fixed now. The handling of “internal” datasources If a content file has no file extension, then the meta attribute file.extension returned the file name instead of an empty string. This has been fixed. Manual Change Aloha Link Plugin: Links were not escaped correctly when inserted with the aloha link plugin. With this manual change you can place special characters in a link and it will be escaped according to html standards. To do the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. Some incorrect and unclear parts of the documentation of the Migration Tool have been improved: The documentation now states, that the Migration Tool is available for object property definitions, not for Tagtypes. Also the unclear german translation of the description of the checkbox to “apply a migration to all pages using the same template as this page” has been corrected. The output generated by the function “Check data” for Content Repositories will now contain some detailed information about why objects are not supposed to be contained in the checked Content Repository. The database connections for Content Repositories did no use connection pools. This caused many reconnects to the Content Repository databases when instant publishing is used. This has been changed now. Database connections to Content Repository databases will now be pooled (with very conservative settings). This means that connections will be kept alive and can be reused after the publish process is finished. When creating a page with non-ASCII characters in its name in the backend, the automatically created filename would sometimes be empty. When pages were moved to other folders, they were left in the “locked“ state, even if they were not locked before. Also when pages were copied, the copy was “locked”. Both issues have been fixed now, moving or copying pages will not lock them. Doubleclicking on the duplicate button when doing image manipulation could create two duplicates with the same file name. This has been fixed. Sorting the Queue by Node caused an SGB, which has been fixed now. The Apache Tomcat will automatically be updated to version 6.0.41 in order to secure various vulnerabilities. Dirting: Previously, when opening the properties of a folder and clicking “OK” without changing any values, all objects depending on this folder have been dirted and re-published. From now on this will only happen when one of the values changes. When using the copy_tags feature to copy & paste tags from one page into another, the new inserted tags would not get the edit buttons right away. It was necessary to save and reopen the page in edit mode to get the edit buttons for the copied tag. This has been fixed now, copied tags will immediately get the edit buttons. Some inperformant SQL queries that were used while versioning pages could cause long database locks. Those SQL queries have been fixed now. Fixed webapp startup issues: When triggered, the safety check for mappedglobalidsequence would prevent the detection of a new license key. In some configurations, the startup safety checks would not output any error message. Now, there‘s additional logging as well as output to stderr, in case something prevents the startup of the webapp. The webapp will now refuse to startup if no globalprefix is set and no valid license can be found. When a page was scheduled to be published at a certain time in the future, and was then processed by a publish run with multithreaded publishing, the publishtimestamp that was written into the Content Repository was not the one from the publish process but from the time, the editor scheduled the publishing. This has been fixed now, the publishtimestamp written into the Content Repository will now be correct. Fixed too strict permission check that would hide the “OK” button when editing a user. This way changing a user‘s group assignments directly from the user‘s edit view was not possible any more. Publishing to content repositories: Updatetimestamps are now created from wallclock time instead of from transaction time. This will mitigate portal cache consistency issues when instant publishing is used during a publish run. Deleting a node could sometimes lead to database inconsistencies (leaving a node entry without its root folder). Those database inconsistencies would subsequently cause publish failures. The process of deleting nodes has been modified, so that no database inconsistencies can occur, even if the process itself is interrupted or fails. Implementations using the Datasource PartType did not work as expected. Dirting of dependent objects did not work, when tags containing a Datasource PartType were changed and doing imports of tags with Datasource PartTypes could cause Internal Errors. These errors have been fixed now. Possibly incorrect references to datasources in the database will automatically be corrected during the next initialization of Gentics Content.Node. The language shown in the page properties dialog was not the page‘s language, but the currently selected content language. This has been fixed now. The page‘s language will be shown now. If the page has no language set, the field will be empty. Manual Change Aloha Link Plugin: Links were not escaped correctly when inserted with the aloha link plugin. With this manual change you can place special characters in a link and it will be escaped according to html standards. To do the manual change please update the tagfill of the tagtype “Aloha Link“ (keyword: “gtxalohapagelink”) to match the code in the Aloha Page Link Tag Description. Setting permissions on custom tree entries did not work as expected and has been fixed now. When using Roles to grant permissions on languages to users, the “translate“ role was not sufficient to create language variants of existing pages. This has been fixed now, users with the “translate“ role for a specific language are allowed to create translations (language variants of existing pages), whereas creation of new pages still requires the “create“ role (or the “create” group permission). Pasting a link didn‘t mark it as Aloha Page link. This has been fixed. Using an apostrophe in a folder name would lead to a javascript error in the folder listings. Also, javascript escape sequences were interpreted by mistake. This has been fixed. A javascript error in the webdav (folder open) dialog was fixed. Internet Explorer 11 does no longer support opening of webdav folders. Instead webdav folders have to be opened manually now. The infotext in the webdav dialog was adapted. It is no longer possible to store files (or images) with empty filename using the properties dialog, the imagemanipulation2 or the REST API. Importing an object property definition containing an overview sometimes failed with an “Internal error”, because the export contained an invalid reference. This has been fixed now. New exports of object property definitions containing overviews can now be successfully imported. Some actions on tagtypes, like adding or removing a part did not change the editor and edittime of the construct itself. This has been changed now. Also log entries will now be added on all actions of constructs. Fixed the GCN JS API to enable it to recover after a JavaScript exception occurs with no ‘error-encountered‘ handler registered to. 2dotool integration: “Request translation” would log out the user immediately. Tagfill popup (Internet Explorer): fix automatic scroll to the bottom of the popup when editing a Tagfill. When opening the todo tool, the user was automatically logged out. This has been fixed now, the todo tool can now be used normally. Image Manipulation 2: Fixed manipulating images not working on certain systems with a webserver proxy that filters URL‘s for security and doesn‘t allow full URLs to be passed as URL parameter. When exporting an object that can have object tags (folder, template, page, image or file), only enabled object tags will be exported. This fixes the problem, that object property definitions need to be exported together with objects, although the object tag has never been used (filled) for the object. If removing pages or files during an incremental page import lasted longer than 5 seconds, an error was logged in the import log, and possibly not all removed files or pages were deleted in the CMS. This has been fixed now by increasing the timeout to a reasonable high number of seconds. When a tagtype is deleted, that was used by an object property, this could cause excessive dirting (delaying the publish process for a long time), even in the object property was not used by a large number of objects. This has been optimized now, deleting a tagtype will only cause a dirt event, if the tag that used the tagtype was enabled. quickjump: if a page exists but is not visible to a user and the user searches for the page name in the quickjump box, the system will try to access the page and an error message is shown. This has been changed to a “Page not found” message. When deleting a tagtype or object property definition takes longer than 5 seconds, the user will now be informed, that the process is continued in the background. When deleting object property definitions, dirting for deleted object tags will only be done for enabled object tags. A file descriptor leak has been discovered in the scheduler that could potentially eat up all available file descriptors for scheduled processes. This fix removes a leaked file descriptor of a lock file. If a page is moved to another node and taken offline before the next publishrun, then it will not be removed correctly from the source node. This has been fixed. Multichanneling: The order functionality within the list views (folders, files, pages, templates) did not work correctly when ordering the column “Master”. This issue is now resolved. Fixed an issue where role permissions were sometimes not loaded correctly and users had too little or too many permissions. Also, existing role permissions sometimes wouldn‘t show in the role editor and be deleted on save even if not modified. Fixed an issue where pages couldn‘t be listed in the backend if you only had permissions for a specific language using a role and the language had not yet been set. Tagtype migration: When doing a migration on an object property definition in the Administration, there somtimes occured a SGB error or a white page was shown. This has been fixed now. A bug in the page version restore was fixed. In some cases a version restore could create a new mappedglobalid record which conflicted with the existing one. This duplicate record could lead to import/export problems. In some cases an import of a page which would overwrite a page tag would recreate the tag without a value. The duplicate mappedglobalid records will automatically be purged. Please note that the purge process may a take while depending on your mappedglobalid size. Multichanneling: When editing the value of a part type URL and the file/image is inside a localized folder, the displayed path name was wrong. contentfile-auto-offline: Previously, when a page contained an Image-URL for an Image in the same contentrepository, the target image file was not taken online automatically. This has been fixed. When uploading a file, the temporary file of the File-Upload-Manipulator was never deleted. This has been fixed. GenticsImageStore: jpeg resizing quality setting is not ignored when cropping. Validation feature: Fixed that some page properties and page tags/object properties weren‘t validated in the Rest API page/save request. This only affects GCN systems where the validation feature is enabled. Previously, a rollback of a Contentrepository transaction of a publish run could result in a hangup of the publish process. This has been fixed now. Improved the documentation for the Navigation Part Type Publishing: File names with ‘)‘ and ‘]‘ didn‘t work with the Gentics Image Store. GCN JS API / REST-API: Fixed page.preview() not working for pages in channels. When setting a startpage for a folder in the folder object properties a log entry is written. This log entry is missing, when doing the same via the context menu in the page list of a folder. Now both actions will produce the same log entry. An import would previously under certain circumstances delete a freshly imported value from a contenttag. These values are now imported correctly. linkBrowser: only channel nodes from the master node are displayed in the link Browser. The ‘Web adresse‘ regular expression now accepts ‘https://‘ URLs and network-path reference URLs (‘//‘). Occasionally, in Wiki-Edit-Mode, when clicking “edit” in the Real-Editor an error message was shown instead of the editing mask. During import, objects with translatable names or descriptions (Tagtypes, Parts,...) previously would have empty names or descriptions replaced by non-empty strings of other translations. Now, empty names or descriptions can be imported normally. Previously, Navigation parts would use and count pages that were not not yet published or already taken offline. They have been fixed to only use and count pages that are actually online. Information related to the Heartbleed openSSL security vulnerability Email sending: Fixed GCN not setting the “Return-Path“ in some cases when “$MAILRETURNPATH” is specified in the configuration. This happened for example when someone took pages back into revision in the publish queue. When defining velocity macros in tag implementations, the macros were globally available and would be overwritten by macros defined in other tags but with the same name. This resulted in unexpected and random behavior if multiple macros with the same name were defined. The scope of inline defined macros has been changed to be local to the template, like documented in the Gentics Content.Node Guides. Multiple bugs concerning overviews have been fixed: An overview would be dirted if a matching object was added in a channel. A recursive overview of images would not be dirted if an image was added in a subfolder of a selected folder. An overview would not render objects created in the same channel, if there were no other dependencies of the page in that channel (as compared to the parent channel). Improved robustness of publish process A race condition that allowed the publish process to run multiple times in parallel has been removed. A potential deadlock in error handling during the initialisation phase of the publish process has been removed. When only a tagmap entry was modified for a ContentRepository, but no data was changed, the subsequent call to CRSync or MCCRSync would not synchronize this changed tagmap entry to the target CR. This has been fixed now, CRSync and MCCRSync will always synchronize modified tagmap entries, even if no actual data was changed. Fixed wrong permission checking when assigning/unlinking nodes from a CR in the administration. Previously the following permissions where checked: Now the following permissions are checked: File properties: Fixed a Javascript error that occured when opening the minibrowser and then clicking “ok“. When importing pages containing overviews over images, where the images have been selected manually, the references to the images were not set correctly, which resulted in empty overviews. This has been fixed now. Overview tags in pages: When editing new overview tags in pages the wizard starts with page 1 correctly. Previously it started with page 2 if any changes were made to the page. When importing a new node with a new object property definition, that is restricted to the node, the restriction was not set correctly. On the target system, the object property definition was available to all nodes. This has been fixed now. The way, older publish logs are archived was inefficient and has been improved. Before this fix, having many publish logs (e.g. because the publish process runs very often) which were very large could cause the archiving to take a very long time (up to several hours). An internal shutdown method for Gentics Content.Node has been fixed. Previously the shutdown command did not close the MySQL connection pool. Login mask: Fixed that the login is possible for LDAP-users that don‘t have a password set. Internal connections that use the IPv6 loopback interface are now also whitelisted by default. Previously IPv6 connections that used ‘::1‘ were not accepted by default. The documentation of the feature “cr_filesystem_attributes” has been enhanced to clarify that it is mandatory to repair the ContentRepository structures after switching on the feature, even if no filesystem attribute is used yet. Fixed a content repository consistency issue: If you moved a file between two nodes that publish to the same content repository, that has instant publishing enabled, it would get deleted from the contentrepository on the next publish run. When cancelling a page while editing it in Aloha Editor or using the REST API, the global ID of the page might change, which would cause unexpected behavior when the page was exported to another system, since the page would then have different global IDs on the systems and could not be overwritten by a subsequent export. This has been fixed now, the global IDs of pages will no longer change when cancelling editing. Pages that are already affected by changed global IDs need to manually be modified if necessary. File upload: Fixed image recognition for JPG images not correctly working in rare cases. Previously those images would not be recognized as image and the mimetype would be “application/octet-stream”. Now they are correctly recognized as images. When a page variant of an inherited page was created in a channel local folder, the master page could not be edited any more. Additionally, loading the master page over the REST API in the scope of the master with page variants attached resulted in an error. These errors have been fixed now. When rendering a channel local page for editing without specifying a nodeId, this failed because the page could not be loaded from the master channel. Now, the channel of the page will implicitly set and rendering will work as expected. This also affected frontend editing using Gentics Portal.Node Java, which did not work for channel specific pages. LDAP Login: Fixed that the LDAP login is not working on certain LDAP server configurations, when using the setting $LDAP_LOGIN_FIELDS[“dontuse_uniquememberattribute“] = true; in the GCN configuration. The problem only occured with LDAP servers that use the field “uid“ or others for the unique user identifier, instead of “cn”. The process of resizing images during a publish process with the GenticsImageStore has been modified to be more stable. Before this fix, images were fetched from the cache or resized (if not found in the cache) while subsequently reading data from the database. When many images needed to be resized this could take a long time and could cause the open database statement to run into a timeout. In these cases, the publish process would fail. Now, the database statement to get the information, which images are resized using the GenticsImageStore is processed before the actual image resizing takes place. Resizing the images may still take long, but will not cause a timeout in the database any more, so the likeliness of publish failures is reduced. Folder creation: A rare error has been fixed that occured when creating a folder. During the creation of the folder an SGB error occured and a “tag_duplicate“-error was logged. This happened when the mother folder had an object property set, that was created inside another object property. When an object property definition was added to folders afterwards, with the same keyword and “inheration” enabled, the tag duplication (for inherited tags) while creating a folder didn‘t work properly. On a rollback of a publishrun with instant publishing enabled, Gentics Content.Node would previously leave already published objects in the content repository, but delete their filesystem attributes. This behaviour has been corrected so that only the filesystem attributes of actually rolled back objects are deleted. The error handling for publishing into contentrepositories with multithreaded publishing has been improved. Certain inconsistencies in the database Time management will now also be done in nodes, that have publishing disabled. Pages affected from time management will be set offline or online due to time management, but those changes will still not be published as long as publishing is disabled for the node. This will enable time management in situations, where pages from nodes with publishing disabled are inherited into channels that have publishing enabled. Additionally, time management is more efficient now, which reduces the publishing time for every publish process. Updated the feature overview guides and added the missing features: Also, the list of deprecated features has been updated with: When subscribing to the event channel ‘tag.rendered‘ or ‘page.rendered‘ in the Gentics Content.Node JavaScript API, the handlers were not called when inserting new tags and the insertion failed (tag was not inserted) without any visible error messages. These errors have been fixed now, when inserting a new tag, the handler for the channel ‘tag.rendered‘ will be called and insertion will succeed. When opening a page for editing with Aloha Editor, the toolbar entries to insert new tags into editables are created asynchronously. In cases, where this takes longer and the editor activates an editable before the initialization is done, a wrong set of icons was shown. This has been fixed now. If an editor activates an editable before the tag insert icons are initialized, a “loading” icon will be shown in the toolbar as placeholder for the tag insert menu. When the the tag insert icons are ready to be used, the placeholder will immediately be replaced with the tag insert icons. Follow-up from Bugfix RT57627. When a Page is imported and no weekdays are set for per-weekday-publishing it automatically sets all weekdays. Since GCN 5.15.8 all weekdays are set for per-weekday-publishing by default. This fixes importing a page from a system prior 5.15.8, where pages would appear online if no weekday was set for per-weekday-publishing. Multiple fixes/enhancements for the GCN fileuploader: An broken i18n translation string was fixed in the User administration. The broken translation caused an input error when a new user was being added. This issue has now been resolved. A bug in the File Upload Manipulator was fixed. Previously the “fileId” property was not set in the request to the FUM script. This issue has now been resolved. Internet Explorer 11 failed to be recognized as browser that is compatible with Live Editor, therefore the Live Editor was deactivated when using Internet Explorer 11. This has been fixed now. Part types: Fixed some tag part types not having a “cnTagPart_“ HTML class set. This has been added for the following types now: Nodes having updates of filesystem/ContentRepository disabled were not rendered italic in the content maintenance dialog. This has been fixed now. Previously, the purgeversions job would corrupt the page cache and a subsequent “Page Cancel” on a corrupted page would revert it to its first recorded version. This has been fixed now. The message count in the top right corner had a bug that caused it to always be 0. It has been fixed to show the current number of unread messages of the user. Page import: Fixed links sometimes not being rendered correctly when publising the pages during import. The links were published as static links (like they have not been transformed), however in the page preview it was rendered correctly. Now when using instant publishing, links will probably be rendered as “#” first (when the target page does not exist yet and will be imported later), but with the next publish run they will be rendered correctly. Fixed the permissions check when moving a folder into another folder. The user needed the “create File“ permission on the target folder and the “create Folder” permission was ignored. Fixed a database consistency problem that occured whenever a master folder with localizations was moved inside a channel node. Previously, Gentics Content.Node would not publish pages from a channel in the filesystem, if the master node has either updates disabled or publishing into filesystem disabled. Now it will correctly publish as indicated in the properties of the channel node. When pushing pages to master nodes using the channel synchronization, pushing of pages will be prevented, if they use local templates (that are not available in the master node). The user will receive a notification about the inability to push pages due to local templates. In the list of scheduler jobs, some execution plans of jobs were not readable in the tooltip due to css styling issues. This has been fixed now. When a page in the master node links to another object (file, image, page or folder) that exists locally in a channel and the source page is rendered in the master node, the link will be rendered as empty (#) now. Before this fix, the URL to the channel local page was rendered, which resulted in a dead link. Gentics Content.Node now fails earlier if it detects common serious problems with GlobalID generation. (e.g. if you accidentally reset globalidsequence, import different objects with identical GlobalIDs or try to generate GlobalIDs with a NULL globalprefix) When the name of a node was changed using the backend UI, dependent objects were not dirted. This has been fixed now, changing the node name will now correctly trigger object dirting. FileUploadManipulator: Fixed the “folder” object not being sent in the json script request object. See the FUM documentation for more information. Page versions: Fixed data inconsistencies in the database table (duplicate data in nodeversion table) caused by users double clicking on the publish link. Manual Change Server JRE Update A jvm bug was discovered that caused OutOfMemory errors due to non garbage collected image data. The documentation about the publish process has be reorganized and enhanced. A bug in the migration feature was fixed. In some cases the migration of pages changed the page status to ‘being edited‘. This issue only occurred for pages that used templates that were modified recently. Additionally the logging of the migration process was enhanced. When saving or importing a template, a NullPointerException would sometimes be thrown if the containing folder of the template has been deleted. Now you can also handle templates where the containing folder is deleted. A behaviour in IE caused fields to remain greyed out in the tagfill dialogue. When clicking the “display content” checkbox the area should change. The behaviour was fixed for IE. The performance of rendering statistics in the maintenance dialog has been improved by around 50% on systems with many nodes. Various small fixes concerning per-weekday publishing in timemanagement. Previously, per weekday publishing only worked with a start time set. Now it works unconditonally. Previously, page/load REST-API calls would return time management information with weekdays initialized to false if a start time was not set, now they are more intuitively initialized to true. When using the REST API to create a page, file or folder in a folder that exists locally in a channel without specifying a nodeId, the object was created in the master node, but could never be seen in the master node, because its folder did not exist in the master node. This has been changed now, if no nodeId is specified in the request, the object will be created in the folder‘s channel. If an invalid nodeId is specified (nodeId of a channel, in which the specified folder is not visible), the request will fail now. A potential php out of memory error has been fixed in the maintenance dialog. File upload: The description field in the “New -> File / Image” dialog has been removed. It was confusing for some users that the description was only set for files that were added/uploaded afterwards. The way the changelog will be presented in the autoupdate dialog has been changed. Previously all changelog entries would be shown in the changelog dialog. Starting with the next release only the new changelog entries will be shown. Additionally the way how the changelog must be confirmed was changed. It is now mandatory to confirm each manual change. Permission checking for translation was updated, so that edit rights are not required anymore for the source language of a translation. A NullPointerException that sporadically happens if a dependency gets deleted while the publishing process is running has been fixed. Live URLs: Fixed icons not being displayed anymore because the image is broken. When using the tagfill dialog via frontend editing for uploading a new file or image into a page in a channel, the new file or image was not uploaded to the page‘s channel, but to the master node instead. This has been changed now, new files or images uploaded in the tagfill dialog will now be created in the page‘s channel. A bug has been fixed, that prevented instant publishing of new folders, that were imported using the page import. When importing a folder but not the templates, which are assigned to the folder on the source system, the templates will now be assigned to the folder on the target system, if the templates already exist on the target system. Before this fix, templates were only assigned to folders, if the templates were imported. Previously, certain filenames of pages could not be uniquified automatically. This has been known to cause problems with e.g. imports. The code has been changed to allow for more filenames to be uniquified automatically. Fileuploader: Enhanced the mimetype detection of uploaded Files, mimetypes in container formats are now correctly recognized. Previously, a Microsoft Office .docx document was recognized as application/zip because the container is actually a zip. It is now recognized as “application/vnd.openxmlformats-officedocument.wordprocessingml.document”. Instant publishing a page that uses XNL functions will no longer hang when there is a concurrent publish process that uses XNL functions. A bug in the migration feature was fixed. Previously the tagtype migration changed the status of offline pages to being edited. This issue only affected the offline pages within migration jobs. Since a recent Chrome Update, the first column with the checkbox in GCN lists (pages in folders, scheduler, etc.) was cut. This is fixed now. Previously, when moving files in the backend, the permission check on possible target folders was not performed correctly. This has been fixed now. Previously, some templates found in recursive searches could not be displayed even if the user had permission to do so. This has been fixed now. An additional info text has been added to the keyword field in the creation dialog for object properties, tagtypes and tagtype parts. The info text will notify the user that special characters inside the keyword may cause problems when those element are being referenced within an tagmap mapping. When deleting folders, localized copies of templates linked to that folder were deleted, regardless of whether the (master) template was still linked to other folders or used in pages. This bug, which was introduced in Gentics Content.Node 5.13.25, 5.14.13 and 5.15.0 has been fixed now. Removing of objects from a multichannelling aware contentrepository with instant publishing did not work. The objects were removed at the next publish run. This has been fixed now, when instant publishing is enabled, objects will be immediately be removed unless more than one object is deleted at once. Importing of localized templates always created a conflict due to missing target folder, if the localized template did not yet exist on the target system. Because of this, it was impossible to successfully finish the import. This has been fixed now. For localized templates, no check for target folders is done, because localized templates are always linked to the same folders as their masters. When files in the CMS lost their binary content (or were incompletely created without binary content), the publish process failed (due to missing binary data). The display of such files in the backend was inconsistent and it was not possible to delete such files to resolve the publishing error by using the backend. This has been fixed now, broken files that cause the publish process to fail will now be shown in the backend specially marked (with an alert icon and in red) and it is possible to delete them. Additionally, it is now possible to search broken files using either the extended search in the backend or the REST API. The SQL statements used to find reusable data files for filesystem attributes in multichannelling aware contentrepositories were inperformant and have been improved. The GCNJSAPI has been fixed to work as documented when you try to get or set a value of a “Tag (page)” part. Documentation on this has been clarified, too. When using small browser windows (e.g. on systems with low resolutions), some data shown on the startpage of the CMS could overlap each other. This has been fixed now. If the window is too small to show the info boxes side by side the boxes will be shown one on top of the other. A bug in the scheduler view was fixed. Previously no error message was being displayed when the user was trying to delete a scheduler task that still got tasks that depended upon it. This issue has now been resolved. On some systems the Regex.Admin view did not display properly. A security check prevented the correct rendering of the view. The check has been adapted and the view will now render correctly. When part of type “URL (Page)“ was set to be required in the tagtype, the tagtype itself could not be filled without providing a default value for that part. This behaviour was different than the behaviour for other parts (e.g. type “Text”) where the part only has to be filled for tags, but not for the tagtype itself. The behaviour has been changed now to be consistent for all part types: If a part is required, it still can be left empty for the tagtype, but has to be filled in tags (e.g. in pages). Pausing the scheduler could take a very long time due to an inperformant SQL statement. This has been fixed now. A minor issue in the autoupdate feature was fixed. Additional protection checks were added to prevent multiple autoupdate invocations. When selecting elements for an overview using the repository browser, the order of the already selected elements was not always shown consistently. This has been fixed now. When loading the binary contents of a file via the REST API by using /rest/file/content/load/{id} the response always had the ‘Content-Type‘ ‘application/octet-stream‘. This has been changed now, the response to /rest/file/content/load/{id} will now have the correct ‘Content-Type‘ set. When writing pages into the contentrepositories was slower than rendering the pages, the internal job queues could grow very big, which could cause memory problems. This has been fixed now. If one of the queue exceeds the limit of 1000 pages, no more pages will be rendered (and put into the queue), until the queue is below the limit. Previously, when an error occured while requesting a page from Tomcat (404 or 500), the Tomcat version number and a detailed message was shown. That information is now hidden (a static error page is shown). Detailed error output can be found in the log files. Fixed security issue that could possibly allow someone to take over your user account by sending you an URL and doing social engineering. Rest API: Removed the “description“ and “login” field for all responses that return user objects (ie. creator and author) However, methods in the UserResource will still output those two fields for user objects. When migrating tags from a tagtype that contained non-editable parts using the tagtype migration tool, the filled value of the non-editable part in the source tagtype was removed, which should not happen. This has been fixed now. When migrating tags the source and target tagtypes are not changed. When the action “check data“ or “repair data“ for a ContentRepository was started, the status changed to “Running“, even though the job was actually queued (along with other dirt or maintenance events or even the publish process). This has been changed now. The status will now show “Queued“ as long as the job is in the Queue and will only switch to “Running“ when the job really is started. Additionally, queued ContentRepository jobs will now be shown as “ContentRepository Maintenance Action“ instead of “Dependency Calculation” in the maintenance dialog. Moving of inherited or localized folders is not allowed, because they must be moved in their master node. If an editor tried to move a localized or inherited folder, nothing happened, but the editor got no information telling why. This has been fixed now: If an editor tries to move an inherited or localized folder, an information will be displayed that this is not possible (similar to moving pages, images or files). When editing tags as blocks using Aloha Editor and the tagtype implementation contained script tags and a jQuery version >= 1.9.0 was used, the script tags were replaced by some random numbers when the tag was re-rendered in the page after being modified using the tagfill dialog. These numbers were not saved to the page and did not affect the published content of the page, but were just shown while editing the page. This has been fixed now, re-rendering tags containing script tags will now also work with jQuery versions >= 1.9.0. When creating folder overviews by manually selecting the folders and having the “recursive“ flag activated, the subfolders were not added, if the feature multichannelling was activated. This has been fixed now, manual folder overviews with “recursive” activated will now render like expected. When pages were dirted due to changed dependencies, this was not logged any more. This has been fixed now: when a page is dirted, an entry in the logcmd table will be made. Previously, if you translated a page using the page/translate REST-API call, it would create excessive language versions of the same language if the master page was not located in a master node. Now, the page/translate call will not create multiple language variants of the same language any more. The dirting mechanism has been slightly changed to avoid changes to the page table. This will avoid unnecessary locks of the page table that could cause errors while pages are edited during a long running dirt process. Ordering the file or image list by file size works now correctly. Sending messages to groups using the GCN Javascript API did not work at all and has been fixed. Multichannelling: Fixed the mother_obj_id of a folder not getting updated in the CR when the mother folder gets localized. The action “Delete (only this language)“ on pages has been removed for nodes with no languages assigned, for it does nothing. You can use “Delete (all languages)“ instead. For pages that have no language set, although the node has languages assigned, the action “Delete (only this language)” will now delete the page. Email sending: Fixed deleted user receiving notification emails from GCN Now deleted users don‘t receive notification emails anymore. Executing the command ‘Change Template‘ on page variants failed with an error, which has been fixed now. When changing the template for multiple pages at once, the pages will now be processed one by one so changes to every single page will now be visible immediately. When resizing images during a publish run using the GenticsImageStore, some file handles were not closed. This subsequently could cause publish run failures caused by a “too many open files” error. This has been fixed now, file handles will now immediately be closed after usage. When a folder was deleted in a multichannelling environment, local channel objects existing in that folder were not removed. This caused data inconsistencies in the database, which could cause errors in subsequent publish processes. This has been fixed now. When editing a page with Aloha Editor the tagname is now shown when hovering the mouse over a tag icon. The sorting of folders has been changes to be closer to Content.Node‘s canonical order. This means that folders that start with square brackets (eg: “[Templates]”) will be listed towards the bottom of the list. Clicking publish from the page menu or the assistant frame will now also trigger the GCN JS API channel ‘before.page-publish‘ After editing a file/image you are redirected to the list of files or images, depending on the type of the object you were editing. Before this fix: after editing a file/image you were always redirected to the list of files, no matter if you were editing a file or image. Rest API: Fixed /user/me not returning the user‘s groups as shown in the documentation example response. A new query parameter “groups” (default: false) has been added for this. Fixed unnecessary dirting of dependent pages when other pages were republished (and did not go online or offline). Fixed some Javascript Errors when loading page object properties. Fix problem with scrollbars when editing an object property of a page. The scollbar show for the body element and for the frame, this cause very difficult to scroll to the properties. Changing the creation date of a page in the time management changes the page status to ‘modified‘. Clicking in ‘Back to folder‘ after loading images/files redirects to Files or Images depending on the type of file(s) we uploaded. When uploading images/files in a new GCN session and then clicking on ‘Back to Folder‘ button, it takes us to File Folder but the side bar component which contains the history and folder elements are not shown. Also when uploading Images it takes us to the File Folder. The tooltip on folder‘s “directory” field has been rewritten to clarify the field‘s restrictions. When creating page variants using the REST API (or the Gentics Content.Node Javascript API) from pages having very long page names, the REST call returned an error, but created a page with empty filename. This has been fixed now. Previously, when publishing files took longer than the MySQL wait_timeout, the publish process would fail because of a lost MySQL connection. Now, there‘s a keepalive in the file publishing loop, which prevents the MySQL connection from timing out. GCN JS API: Fixed page.takeOffline() not working Added proper escaping for : and = in $ALOHA_SETTINGS which enables you to use :not selectors etc. Previously, publishing or taking offline individually selected pages in an overview would not cause the overview to be updated. Now, the overview is updated correctly. Migration feature: In some cases the page status would not be handled correctly. The page status of migrated pages was set to modified instead. This issue only affected migrations that were using at least one post processor. A regression within the fileuploader was fixed. A fileupload could fail while updating an exiting file with a new file upload. The performance of checking for online/offline files during a publish run (when feature contentfile_auto_offline is used) has been improved. Fixed a possible dependency issue that affects files being taken offline when using the contentfile_auto_offline feature. Pages: Fixed object properties sometimes not being returned by the RestAPI (/page/load) and GCN JS API when creating a page in a channel. The problem occured when the object properties are restricted to the master node. Because restriction only works for master nodes the channels are inheriting the restriction from the master node. Previously, an exception would halt the publish process, if the number of characters of the “directory“ field of a page‘s folder and the “hostname“ and “page directory” fields of the page‘s node exceeded a total of 255. Now, you can use the full length of all of those fields and still have the corresponding pages published correctly. When encountering errors during editing the page, like when the backend server is offline, several technical error messages were displayed to the editor. A single message now replaces these messages. Technical messages are displayed on the console. A translation issue was fixed in the tag type creation view. Validation feature: Fixed SGB error The error occured in the tagfill dialog, when using using Frontend-Editing with the “proxyprefix” URL parameter. The proxyprefix was wrongly used for doing internal request to the RestAPI in the validation feature. Channel folders: When creating a new folder inside a local(ized) folder in a channel, it didn‘t inherite the object properties from the mother folder from the channel, but from the master. This has been fixed now. The DB structure of the table nodesetup has been changed so that the table now has a primary key. This should improve the performance of statements against this table and minimize locks when changing the table. Additionally, a dependency from INSERT statements into other tables to the nodesetup table has been removed. When publishing pages into non MCCR contentrepositories using multithreaded publishing, the log entries for writing the pages into the CR showed the contentid of the folder instead of the page. This bug only affected the publish log, but had no other functional consequences and has been fixed now. A browser caching issue was fixed. Previously the login/logout action did not enforce the update of all cached javascript files. This issue has now been fixed. Creating and saving multiple object with the GCN JS API will not result in having the JavaScript objects‘ ids going out of sync. Previously, when importing a template with templatetag with a changed construct, pages containing contenttags based on that tag would not be updated to the new tagtype as it would be the case if you changed the template by hand in the backend. Now the behavior is the same in both scenarios. The regression that was introduced through an attempt to fix positioning of context menus in IE with RTL (Right-To-Left) pages has now been removed. The problemantic fix has been reverted. The issue with positioning menus in RTL pages therefore remains. When selecting folders for an overview to list pages, images or files in multichannelling environments, in rare cases, the folders were not stored correctly. This has been fixed now. This update will make a structural change in the table dependencymap2, that might take longer than usual depending on the size of the table. The storing of channel specific dependencies of inherited objects has been optimized to reduce the number of entries in the dependencymap2. Additionally, the number of statements necessary to read the dependencies of inherited objects has been reduced. Both optimizations will reduce the size of the dependencymap2 table and will improve the overall publishing performance for systems that have many channels with many inherited objects. A possible NullPointerException during the publish process has been fixed, that occurred when using the feature contentfile_auto_offline and dependencies of non-existing objects were still found in the dependencymap2 (due to unclean removal of objects). Using the REST API pages could be saved with an empty string for page name or page filename. This is not possible any longer now. The quickjump box was starting to search for pages right after the first character being typed. This has been increased to a minimum of three characters to lessen database load and provide more meaningful search results. It is now possible to upload files over https on NodeJS with the GCN JS API. Previously, pages with links to a newly localized page would not get dirted and therefore would not be updated correctly. Now, these pages will be dirted, too. Previously, when multichanneling was used, the languageset.pages meta attribute would not honor the language ordering of the node. Now, the order of page.languageset.pages is the correct sort order. Folder images/file/page views: Fixed two problems. Previously, a scheduler task could be started twice at the same time under certain conditions. Synchronisation has been added to prevent this from happening. Localized files and images inside a channel were not correctly displayed in their respective list overviews. This issue has now been resolved. Sometimes, the scheduler loses the connection to a publish process it started, although the publish process is still running due to timeout problems. In this cases, the scheduler job is marked as “failed“. When the scheduler tries to start the publish process again, this also failed, because the process was still running. Such cases will be handled differently now: if the scheduler tries to start a publish process and finds the process already running, it will “join“ the publish process, like if it just had been created. Therefore if the scheduler loses the connection to a still running publish process, subsequent job runs will not fail with reason “Publish process already running” any more. Taking offline of pages did not work due to a caching problem. The displayed page status did not change and the page would not go offline in the next publish run. This has been fixed now. Tagtype parts: Fixed performance issue when deleting a part of a tagtype. When the database contains lots of pages, this could take multiple hours. It should take only a few seconds (or less) anymore now. Manual Change The database layer has been updated to better estimate the length semantics of varchar/varchar2 columns. This will enable you to use more of the characters in “Text (short)“ attributes in contentrepositories. If you are using Oracle for content repositories, you must check if your NLS_LENGTH_SEMANTICS is set to “CHAR“. If so, you must ensure that contentattribute.text_value as well as all optimized “Text (short)“ columns in contentmap also use “CHAR” semantics. The title of the icon for pages in status “publish at“ in the page list incorrectly was “not in time frame” and has been fixed now. Folder settings: Fixed “Cancel”-button not redirecting back to the last folder view. If an online page was scheduled to be republished using the function “publish at”, in special cases it could happen that the page was republished too early. This has been fixed now. Editables that are nested inside of other editables will now be encoded and saved correctly when editing with the GCN JS API. The default folder for file and image upload now correctly depends on the user‘s view permissions for the folder. It is now possible to change the cache clear behavior. For more information please take a look at the following FAQ Updater: There will be a warning printed now, when starting a Gentics Content.Node update when there have been java patches installed. The performance of the tagtype migration was enhanced. A new option was added to the tag type migration in order to skip the dependency calculation and internal event handling. When the time management of pages was handled during a multithreaded publish process, the publish process could freeze (never finish). This has been fixed now. Folder image/file view: Fixed performance issues with folders that contain more than 1000 images or files. The performance issues were caused by always loading all objects in the folder instead of only the objects for the current pagination view. A misleading tooltip that was shown when choosing elements in a selection-tagpart was removed. Fixed an error with the REST API that would not allow to create pages in a channel – the pages were always created in the master. Possible missing publish log error messages have been fixed. When using IE10 to translate pages that modify their DOM, under some circumstances, the upper frame used to shrink sometimes. Now the frame stays correctly sized. The time management for pages did not always work as expected. Sometimes, pages were not taken off- or online due to time management at all, sometimes not at the desired time, but some time later. This has been fixed now. Deleting nodes is now no longer possible if tagtypes are linked to no other nodes than the deleted ones. This prevents a data inconsistency, where orphaned tagtypes were invisibly lingering inside tagtype categories. A dialog informs the user which tagtypes are blocking the deletion of the node. The internal logging of a publish error has been enhanced. Multichannelling contentrepositories have now a new option to choose between differential check for removed objects (which is faster) or the full check (which is saver) on every publish run. The default value is the differential check. Additionally, the number of SQL statements necessary to publish an object into a multichannelling contentrepository has been reduced to improve performance. Fixed an error when using the feature contentfile_auto_offline is used when publishing into a multichannelling contentrepository. The number of SQL Statements for publishing objects into contentrepositories, when using multithreaded publishing has been reduced to increase the overall publish performance. Fixed selection of translators in the todo tool. Previously, a task scheduled to be executed after another task finishes would sometimes start twice at the same time. Now it will only start once. Previously, in the page translate view, syncing of scrollbars didn‘t work if the lower page contained an iframe and Aloha Editor was not used. Now, syncing works under these conditions, too. Accessing the table dependencymap2 has been optimized to avoid synchronization between threads when using multithreaded publishing. This will increase the overall performance of a multithreaded publish process. As a side-effect, the table dependencymap2 is no longer locked during a publish process. Previously, an SGB occured when pressing “cancel” in the page create dialog. Now the list of pages appears instead. Part type “Url (image)”: Fixed this part not correctly working in the tagfill dialog, when there were multiple parts of this type. Fixed regression in the GCN JS API so that, now, the callback that is passed to the tag.save() method will receive the saved tag as its only argument. Moving pages/files/folders: Fixed multiple issues A bug in the tagtype migration post processor handling was fixed. Removed tags will now be deleted. Previously tags that were removed from the restmodel would not be removed. Various minor enhancements were added to the migration feature. Scheduler: Updated documentation, documented setting $MAX_SCHEDULE_RUNTIME. Page publishing: Fixed Nullpointer exception when publishing a page that contained an objecttag or templatetag with an invalid part type. Quickjump: Fixed wrong folder when opening a multichannelling page. When selecting a page in the quickjump autocomplete dropdown and then going from the page into the folder you landed in the master folder instead of the channel folder. Calling tag.edit() will no longer result in a 404 error in frontend editing if the GCN Intergration plugin‘s “link“ property is not configured. We now default this property to “backend” so that links are rendered as they would appear when using the GCN Intergration Plugin in Content.Node backend. Fixed problems with permission checks that would keep a user from updating his own email address. A minor bug was fixed in the new tag type migration enhancement in version 5.14.2. Previously not all pages were added to the set of pages that should be migrated. A bug in the tag type migration of pages was fixed. Previously the post processors did not receive the migrated page. Migrations that did not use postprocessors were not affected. When publishing a node and its channels into content repositories, it could happen, for a localized object, also the master was published into the channel‘s contentrepository. Additionally, too many dependencies were stored for localized objects, which could lead to unnecessary dirting of objects. Both issues have been fixed. The word “Folder“ and “Name” in the mini-browser now has the proper internationalization for both German and English. When translating localized or inherited pages in a channel that already existed in this language, a new copy of the page was created in the channel. This issue has been fixed, the translate call now correctly returns the page that existed before. An additional option was added to the tag type migration of single pages. This option allows the user to specify whether the defined mapping should be used as a template on a set of pages. The option is documented in detail in the GCN guides. The Content.Repository check and repair action was enhanced. Similar to the CRSync sanitycheck2 and autorepair2 option a check for quick columns will be performed when the check or repair method was invoked. Page editing: Fixed rendering error that occured when editing pages with velocity tags that are not visible (visible when first edited). Those tags were not rendered at all, and the following errors in the browser console were shown: “gcn: Error while rendering part type“ and “No template found”. When inherited pages were published in channels and the rendered source of the master page was reused, the dependencies of that page were re-written even if they did not change. This was unnecessary and will be avoided now. Dependencies will only be written to the database if they effectively changed. The logging of multithreaded publish processes has been improved. Jobs, that are processed in separate threads (like writing data into content repositories), will now also be logged. Fileuploader: Fixed multiple issues: If the property gcnLibVersion is not configured for the GCN Intergration Plugin, it will automatically default to “bin“, in order to use the “binary” version of the GCN JS API in production. Previously, some kinds of JPEG images that trigger bugs in Java ImageIO could not be uploaded using the REST API, as they were saved as files with content type “application/octet-stream“. These images are now correctly recognized as “image/jpeg”. The GCN Intergration Plugin will properly use the renderBlockContentURL setting, when provided to process rendered tags. This makes it possible to render plink as proper urls for frontend editing. When publishing multiple master nodes into the same multichannelling contentrepository, the objects in the contentrepository were checked more than once for deleted objects. This has been fixed now, so that unnecessary checks are avoided. When using multithreaded publishing in very long running publish processes (longer than 8 hours) a timeout in the database connection to the backend database could occur, which has been fixed now. When a filesystem attribute is written again with unchanged value, and the data file does not exist, the data file will be recreated. This enables recreation of missing filesystem attribute data files by republishing the objects in the backend. When publishing into an Oracle MCCR, integer attributes of objects were written again, even if they did not change. This produced unnecessary UPDATEs in the DB and has been fixed now. This fix makes the “publish at” feature work again. When a file or image was marked for being republished using the maintenance dialog, its binarycontent was not written (again) into the content repository. This could lead to missing binarycontent attributes in the content repository, if e.g. the content repository was newly assigned to the node, and has been fixed now. Optional Manual Change Rest API: Removed the template “source” attribute from all Rest API responses except /template/load/. This has been removed to decrease the size of the response, it was too big and could lead to memory_limit issues in the rest client when there were many elements returned. With /template/load/ you can still get the templates source. The REST API getItems performance for folders with many pages was improved. Previously, whenever you opened the properties dialog of a page, that page stayed locked for the rest of the lock‘s duration unless you performed a “Page Save“ or “Page Cancel“ on that page. Now, if you click on “Cancel” in the properties dialog of a page, the lock is released instantly. Page variants: Fixed bug that caused all variants of a page to be set to the status “Being edited” when opening and saving a overview tag in one page. Now the status of the other variants will not be touched anymore. When creating a new page from the backend the filename now will convert colons to underscore too, as colon is a reserved character by rfc3986#section-2.2 Memory usage and performance of displaying the message inbox have been improved. This prevents memory exhaustion even for very large numbers of messages. Object properties that are used or inherited in a page can now properly be disabled. Previously, deactivating an object property did not cause the entry linked to it via the tagmap editor to be properly removed from the Contentrepository. There was a bug in the calculation of the set of object properties available to channel root folders. This used to prevent the user from seeing and editing object properties of a channel root folder in the object property editor dialog. Objecttag Definitions in export files are now annotated with information on whether “assign to all nodes” has been selected for them. If such an annotated Objecttag Definition is imported, the importer makes sure that the imported object is associated with all nodes if the exported object was associated with all nodes. A scheduler task‘s editor is now updated correctly. Manual Change Java 7 Update Please update the used Java version to Server JRE 1.7.0_25-b15 64 bit. Download the ‘Server JRE‘ package and extract it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the tomcat once you finished this step using the /Node/bin/nodectl script. Manual Change Fileuploader: The node.conf options “alwaysfileuploadfallback“ & “multifileupload” have been removed with the introduction of the new fileuploader. As the new fileuploader comes with an automatic browser feature detection those settings are now obsolete, you can remove the settings from the node.conf. Optional Manual Change MySQL 5.5 / 5.6 Update It is recommended to update the used MySQL Database Server to When selecting an item with the link browser, the link element‘s title attribute will be automatically set based on Aloha Editor Link Plugin‘s new titleregex/title configuration options. The import/export feature was enhanced. It is now possible to select update files which have been placed into the /Node/node/system/fs_import_bundles. An additional drop down box was added to the import dialog. Folder objects returned by the REST API now contain the additional (read only) fields masterId, channelsetId, channelId and isMaster. The GCN JS API TagAPI.save() method has now been corrected to rather than just saving the whole page straight away a mockup object is created to save a single tag specifically. The common/autoparagraph plugin was added to the list of default plugin. Please take a look at the aloha editor plugin documentation to learn more about the autoparagraph plugin. This release comes with a new fileuploader which replaces the old flash uploader, its fallback and the old PHP legacy fileuploader. It combines the features of all the old fileuploaders with automatic browser feature detection and also has HTML 5 & drag&drop support. Fileupload Manipulator (FUM): The timeouts and connection retries for the HTTP Client that will be used to call the FUM script are now configurable. See the File Upload Manipulator for more details. Page translation has been improved with multichannelling functionalities. If an inherited or a localized page is translated and the corresponding language variant does not yet exist in the master node, this page is created there and taken offline, linking the versions to each other while basing the translated page‘s content on that of the localized version. This enhancement is applied to all translation actions (direct REST call, Edit in, Translate to, Quick Recursive Translation). Fileupload & GenticsImageStore: CMYK JPG images are now recognized as images by the fileuploader and supported by the GenticsImageStore. The GenticsImageStore will automatically convert CMYK input images to RGB JPEGs when manipulating an image. Rest API: Disabled the automatic output indentation of all JSON responses by default for performance reasons. The JSON responses are now ~33% smaller. This feature can now be turned on in the GCN configuration if needed. More info can be found in the documentation. Added a “Localize” option to the context menu of channel folders in the tree view of the left frame of the backend. An error within the tagtype list was fixed. Previously it was not possible to reassign a tagtype category to a tagtype using the tagtype list context menu. This issue has now been resvoled. When a folder was deleted in a multichannelling environment, local channel objects existing in that folder were not removed. This caused data inconsistencies in the database, which could cause errors in subsequent publish processes. This has been fixed now. When editing a page with Aloha Editor the tagname is now shown when hovering the mouse over a tag icon. Clicking publish from the page menu or the assistant frame will now also trigger the GCN JS API channel ‘before.page-publish‘ Rest API: Fixed /user/me not returning the user‘s groups as shown in the documentation example response. A new query parameter “groups” (default: false) has been added for this. Fixed unnecessary dirting of dependent pages when other pages were republished (and did not go online or offline). Fixed some Javascript Errors when loading page object properties. Fix problem with scrollbars when editing an object property of a page. The scollbar show for the body element and for the frame, this cause very difficult to scroll to the properties. Changing the creation date of a page in the time management changes the page status to ‘modified‘. The tooltip on folder‘s “directory” field has been rewritten to clarify the field‘s restrictions. When creating page variants using the REST API (or the Gentics Content.Node Javascript API) from pages having very long page names, the REST call returned an error, but created a page with empty filename. This has been fixed now. Previously, when publishing files took longer than the MySQL wait_timeout, the publish process would fail because of a lost MySQL connection. Now, there‘s a keepalive in the file publishing loop, which prevents the MySQL connection from timing out. GCN JS API: Fixed page.takeOffline() not working Added proper escaping for : and = in $ALOHA_SETTINGS which enables you to use :not selectors etc. Previously, publishing or taking offline individually selected pages in an overview would not cause the overview to be updated. Now, the overview is updated correctly. The performance of checking for online/offline files during a publish run (when feature contentfile_auto_offline is used) has been improved. Fixed a possible dependency issue that affects files being taken offline when using the contentfile_auto_offline feature. Pages: Fixed object properties sometimes not being returned by the RestAPI (/page/load) and GCN JS API when creating a page in a channel. The problem occured when the object properties are restricted to the master node. Because restriction only works for master nodes the channels are inheriting the restriction from the master node. Previously, an exception would halt the publish process, if the number of characters of the “directory“ field of a page‘s folder and the “hostname“ and “page directory” fields of the page‘s node exceeded a total of 255. Now, you can use the full length of all of those fields and still have the corresponding pages published correctly. When encountering errors during editing the page, like when the backend server is offline, several technical error messages were displayed to the editor. A single message now replaces these messages. Technical messages are displayed on the console. A translation issue was fixed in the tag type creation view. Validation feature: Fixed SGB error The error occured in the tagfill dialog, when using using Frontend-Editing with the “proxyprefix” URL parameter. The proxyprefix was wrongly used for doing internal request to the RestAPI in the validation feature. Channel folders: When creating a new folder inside a local(ized) folder in a channel, it didn‘t inherite the object properties from the mother folder from the channel, but from the master. This has been fixed now. The DB structure of the table nodesetup has been changed so that the table now has a primary key. This should improve the performance of statements against this table and minimize locks when changing the table. Additionally, a dependency from INSERT statements into other tables to the nodesetup table has been removed. When publishing pages into non MCCR contentrepositories using multithreaded publishing, the log entries for writing the pages into the CR showed the contentid of the folder instead of the page. This bug only affected the publish log, but had no other functional consequences and has been fixed now. A browser caching issue was fixed. Previously the login/logout action did not enforce the update of all cached javascript files. This issue has now been fixed. Previously, when importing a template with templatetag with a changed construct, pages containing contenttags based on that tag would not be updated to the new tagtype as it would be the case if you changed the template by hand in the backend. Now the behavior is the same in both scenarios. The regression that was introduced through an attempt to fix positioning of context menus in IE with RTL (Right-To-Left) pages has now been removed. The problemantic fix has been reverted. The issue with positioning menus in RTL pages therefore remains. When selecting folders for an overview to list pages, images or files in multichannelling environments, in rare cases, the folders were not stored correctly. This has been fixed now. This update will make a structural change in the table dependencymap2, that might take longer than usual depending on the size of the table. The storing of channel specific dependencies of inherited objects has been optimized to reduce the number of entries in the dependencymap2. Additionally, the number of statements necessary to read the dependencies of inherited objects has been reduced. Both optimizations will reduce the size of the dependencymap2 table and will improve the overall publishing performance for systems that have many channels with many inherited objects. A possible NullPointerException during the publish process has been fixed, that occurred when using the feature contentfile_auto_offline and dependencies of non-existing objects were still found in the dependencymap2 (due to unclean removal of objects). Using the REST API pages could be saved with an empty string for page name or page filename. This is not possible any longer now. The quickjump box was starting to search for pages right after the first character being typed. This has been increased to a minimum of three characters to lessen database load and provide more meaningful search results. Previously, pages with links to a newly localized page would not get dirted and therefore would not be updated correctly. Now, these pages will be dirted, too. Previously, when multichanneling was used, the languageset.pages meta attribute would not honor the language ordering of the node. Now, the order of page.languageset.pages is the correct sort order. Folder images/file/page views: Fixed two problems. Previously, a scheduler task could be started twice at the same time under certain conditions. Synchronisation has been added to prevent this from happening. Localized files and images inside a channel were not correctly displayed in their respective list overviews. This issue has now been resolved. Sometimes, the scheduler loses the connection to a publish process it started, although the publish process is still running due to timeout problems. In this cases, the scheduler job is marked as “failed“. When the scheduler tries to start the publish process again, this also failed, because the process was still running. Such cases will be handled differently now: if the scheduler tries to start a publish process and finds the process already running, it will “join“ the publish process, like if it just had been created. Therefore if the scheduler loses the connection to a still running publish process, subsequent job runs will not fail with reason “Publish process already running” any more. Taking offline of pages did not work due to a caching problem. The displayed page status did not change and the page would not go offline in the next publish run. This has been fixed now. Tagtype parts: Fixed performance issue when deleting a part of a tagtype. When the database contains lots of pages, this could take multiple hours. It should take only a few seconds (or less) anymore now. Manual Change The database layer has been updated to better estimate the length semantics of varchar/varchar2 columns. This will enable you to use more of the characters in “Text (short)“ attributes in contentrepositories. If you are using Oracle for content repositories, you must check if your NLS_LENGTH_SEMANTICS is set to “CHAR“. If so, you must ensure that contentattribute.text_value as well as all optimized “Text (short)“ columns in contentmap also use “CHAR” semantics. The title of the icon for pages in status “publish at“ in the page list incorrectly was “not in time frame” and has been fixed now. Folder settings: Fixed “Cancel”-button not redirecting back to the last folder view. If an online page was scheduled to be republished using the function “publish at”, in special cases it could happen that the page was republished too early. This has been fixed now. Editables that are nested inside of other editables will now be encoded and saved correctly when editing with the GCN JS API. The default folder for file and image upload now correctly depends on the user‘s view permissions for the folder. It is now possible to change the cache clear behavior. For more information please take a look at the following FAQ Updater: There will be a warning printed now, when starting a Gentics Content.Node update when there have been java patches installed. The performance of the tagtype migration was enhanced. A new option was added to the tag type migration in order to skip the dependency calculation and internal event handling. When the time management of pages was handled during a multithreaded publish process, the publish process could freeze (never finish). This has been fixed now. Folder image/file view: Fixed performance issues with folders that contain more than 1000 images or files. The performance issues were caused by always loading all objects in the folder instead of only the objects for the current pagination view. A misleading tooltip that was shown when choosing elements in a selection-tagpart was removed. Possible missing publish log error messages have been fixed. When using IE10 to translate pages that modify their DOM, under some circumstances, the upper frame used to shrink sometimes. Now the frame stays correctly sized. The time management for pages did not always work as expected. Sometimes, pages were not taken off- or online due to time management at all, sometimes not at the desired time, but some time later. This has been fixed now. Deleting nodes is now no longer possible if tagtypes are linked to no other nodes than the deleted ones. This prevents a data inconsistency, where orphaned tagtypes were invisibly lingering inside tagtype categories. A dialog informs the user which tagtypes are blocking the deletion of the node. Manual Change Java Server JDK Update A defect in the Java JRE 6 was discovered. This defects affects the behavior of Gentics Content.Node. Update changelog: http://www.oracle.com/technetwork/java/javase/6u18–142093.html Bugreport: http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6699669 The affected version are 1.6.0_14 to 1.6.0_18. The internal logging of a publish error has been enhanced. Multichannelling contentrepositories have now a new option to choose between differential check for removed objects (which is faster) or the full check (which is saver) on every publish run. The default value is the differential check. Additionally, the number of SQL statements necessary to publish an object into a multichannelling contentrepository has been reduced to improve performance. The number of SQL Statements for publishing objects into contentrepositories, when using multithreaded publishing has been reduced to increase the overall publish performance. Fixed selection of translators in the todo tool. Previously, a task scheduled to be executed after another task finishes would sometimes start twice at the same time. Now it will only start once. Previously, in the page translate view, syncing of scrollbars didn‘t work if the lower page contained an iframe and Aloha Editor was not used. Now, syncing works under these conditions, too. Accessing the table dependencymap2 has been optimized to avoid synchronization between threads when using multithreaded publishing. This will increase the overall performance of a multithreaded publish process. As a side-effect, the table dependencymap2 is no longer locked during a publish process. Previously, an SGB occured when pressing “cancel” in the page create dialog. Now the list of pages appears instead. Part type “Url (image)”: Fixed this part not correctly working in the tagfill dialog, when there were multiple parts of this type. Moving pages/files/folders: Fixed multiple issues A bug in the tagtype migration post processor handling was fixed. Removed tags will now be deleted. Previously tags that were removed from the restmodel would not be removed. Various minor enhancements were added to the migration feature. Scheduler: Updated documentation, documented setting $MAX_SCHEDULE_RUNTIME. An additional option was added to the tag type migration of single pages. This option allows the user to specify whether the defined mapping should be used as a template on a set of pages. The option is documented in detail in the GCN guides. Page publishing: Fixed Nullpointer exception when publishing a page that contained an objecttag or templatetag with an invalid part type. Quickjump: Fixed wrong folder when opening a multichannelling page. When selecting a page in the quickjump autocomplete dropdown and then going from the page into the folder you landed in the master folder instead of the channel folder. Calling tag.edit() will no longer result in a 404 error in frontend editing if the GCN Intergration plugin‘s “link“ property is not configured. We now default this property to “backend” so that links are rendered as they would appear when using the GCN Intergration Plugin in Content.Node backend. Fixed problems with permission checks that would keep a user from updating his own email address. A minor bug was fixed in the new tag type migration enhancement in version 5.14.2. Previously not all pages were added to the set of pages that should be migrated. A bug in the tag type migration of pages was fixed. Previously the post processors did not receive the migrated page. Migrations that did not use postprocessors were not affected. When publishing a node and its channels into content repositories, it could happen, for a localized object, also the master was published into the channel‘s contentrepository. Additionally, too many dependencies were stored for localized objects, which could lead to unnecessary dirting of objects. Both issues have been fixed. The word “Folder“ and “Name” in the mini-browser now has the proper internationalization for both German and English. The Content.Repository check and repair action was enhanced. Similar to the CRSync sanitycheck2 and autorepair2 option a check for quick columns will be performed when the check or repair method was invoked. Page editing: Fixed rendering error that occured when editing pages with velocity tags that are not visible (visible when first edited). Those tags were not rendered at all, and the following errors in the browser console were shown: “gcn: Error while rendering part type“ and “No template found”. When inherited pages were published in channels and the rendered source of the master page was reused, the dependencies of that page were re-written even if they did not change. This was unnecessary and will be avoided now. Dependencies will only be written to the database if they effectively changed. The logging of multithreaded publish processes has been improved. Jobs, that are processed in separate threads (like writing data into content repositories), will now also be logged. If the property gcnLibVersion is not configured for the GCN Intergration Plugin, it will automatically default to “bin“, in order to use the “binary” version of the GCN JS API in production. Previously, some kinds of JPEG images that trigger bugs in Java ImageIO could not be uploaded using the REST API, as they were saved as files with content type “application/octet-stream“. These images are now correctly recognized as “image/jpeg”. The GCN Intergration Plugin will properly use the renderBlockContentURL setting, when provided to process rendered tags. This makes it possible to render plink as proper urls for frontend editing. When using multithreaded publishing in very long running publish processes (longer than 8 hours) a timeout in the database connection to the backend database could occur, which has been fixed now. When a filesystem attribute is written again with unchanged value, and the data file does not exist, the data file will be recreated. This enables recreation of missing filesystem attribute data files by republishing the objects in the backend. When publishing into an Oracle MCCR, integer attributes of objects were written again, even if they did not change. This produced unnecessary UPDATEs in the DB and has been fixed now. This fix makes the “publish at” feature work again. Optional Manual Change Rest API: Removed the template “source” attribute from all Rest API responses except /template/load/. This has been removed to decrease the size of the response, it was too big and could lead to memory_limit issues in the rest client when there were many elements returned. With /template/load/ you can still get the templates source. The REST API getItems performance for folders with many pages was improved. Previously, whenever you opened the properties dialog of a page, that page stayed locked for the rest of the lock‘s duration unless you performed a “Page Save“ or “Page Cancel“ on that page. Now, if you click on “Cancel” in the properties dialog of a page, the lock is released instantly. Page variants: Fixed bug that caused all variants of a page to be set to the status “Being edited” when opening and saving a overview tag in one page. Now the status of the other variants will not be touched anymore. When creating a new page from the backend the filename now will convert colons to underscore too, as colon is a reserved character by rfc3986#section-2.2 Memory usage and performance of displaying the message inbox have been improved. This prevents memory exhaustion even for very large numbers of messages. Object properties that are used or inherited in a page can now properly be disabled. Previously, deactivating an object property did not cause the entry linked to it via the tagmap editor to be properly removed from the Contentrepository. There was a bug in the calculation of the set of object properties available to channel root folders. This used to prevent the user from seeing and editing object properties of a channel root folder in the object property editor dialog. Objecttag Definitions in export files are now annotated with information on whether “assign to all nodes” has been selected for them. If such an annotated Objecttag Definition is imported, the importer makes sure that the imported object is associated with all nodes if the exported object was associated with all nodes. A scheduler task‘s editor is now updated correctly. In some cases the page status was not handled correctly. This caused the publish process to ignore some pages. This defect first appeared in 5.12.27 / 5.13.11. This issue was now resolved. Manual Change It is now possible to deactivate tags using the GCN JS API. Newly created tags will be automatically activated, but before the page is saved, that tag can be deactivated. Improved and extended list of supported and discontinued features in the guides. It is now possible to use the ModelBuilderApiHelper class to render REST Models. This is useful if you want to render a page within a Tag Type Migration Post processor. The REST API getItems performance for folders with many pages was improved. Fixed export selection in multichanneling environments. Previously, if you added a folder that has been created in a channel in the channel where it was created, its contained elements would not be automatically selected as dependencies. Import: Fixed setting permissions when important content repositories. When the import was started with a different group, it did not get permissions on the new content repository. The chosen group and all parent groups will now get permission on the content repository when doing imports. Fixed GCNs internal sorting function not respecting whitespace in strings like MySQLs sorting does. This caused the repository browsers to sort entries (nodes, folders) with whitespaces in the name differently than the main GCN node tree did. When a contentrepository contained a tagmap entry of type “[7] Foreign Link“ that had a non-empty tagname set, this could lead to objects being removed from the contentrepository, although they should not be removed. This behaviour has been fixed now. Please note however, that having a tagname set for a tagmap entry of type “[7] Foreign Link“ is wrong, because such an attribute will not be rendered in the backend. Therefore it is stronly recommended to leave the tagname of tagmap entries of type “[7] Foreign Link” empty! A performance issue has been fixed that slowed down the listing of files/images in folders with a big number of files/images. Fixed the assignment of constructs to nodes during the import. Create page: Fixed error that ocurred when no filename was given and there was another file in the same publish path with an empty filename. Also fixed broken i18n translation for this error messages. Import: Fixed permission bug when importing content repositories. The group used for importing never got the “Assign user permissions”-permission flag. Therefore users were never able to grant permissions for imported content repositories to other groups. A issue within the sanitycheck2 was fixed. Previously an alter column statement for MSSQL only failed due to an syntax error. This is issue is now resolved. When a file or image was marked for being republished using the maintenance dialog, its binarycontent was not written (again) into the content repository. This could lead to missing binarycontent attributes in the content repository, if e.g. the content repository was newly assigned to the node, and has been fixed now. When a page that has no language set shall be translated or modified in a specific language, the user will now be informed that he has to set the page language first. This will reduce the chance of users unexpectedly overwriting the page‘s content with another language. Setting references to other objects during an import has been fixed. Before this fix, objects were possibly overwritten (even if they should not have been changed) and references could be lost during an import. When uploading images using the REST API, some temporary files named imageio*.tmp were created and left open until the garbage collector would remove them. This could lead to a “Too many open files” error. This has been fixed now, those temporary files are now removed as soon as they are no longer needed. Fixed possible NPE when running a multithreaded publish process, where pages needed to be published, because they were scheduled with the “publish at” action. Fixed too strict security check when linking workflows to folders. Before this fix, linking workflows to folders was only possibly, when the user had the permission to manage the workflows, now the permission to link workflows is sufficient. The top menu was incorrectly positioned in the translate page view. This has been fixed now. If an online page is moved to a different folder and taken offline, it is now possible to create a new page having the same filename. With this fix, it is possible to subsitute an online page with a new page having the same filename, even if a wastebin workflow moves the old page away and takes it offline instead of deleting it. Synchronizing the scrollbars in the translate page view did not work anymore and has been fixed. LDAP Login: Fixed the LDAP Advanced Groups feature not working, when the LDAP server (ie.: Microsoft Active Directory) doesn‘t have objectclass=groupofUniqueNames & “uniquemember“ enabled. In this case please enable the following feature in your node.conf: LDAP Login: Fixed LDAP login being case sensitive when using advanced groups and fixed SGB occuring when a LDAP group couldn‘t be found in GCN. The javascript error logging for the tagtype migration and template migration has been enhanced. Under some circumstances, page-editable template tags were previously not correctly inherited when using multichanneling. Now a page created in a channel always inherits from the relevant channel version of the template. Fixed in backend as well as in REST page/create. Fixed a bug that prevented starting due scheduler jobs because of a database inconsistency. Various issues within the template migration / tagtype migration were fixed. Publish runs that remove many objects from a content repository at once can lead to idle database connections, which in certain circumstances could be closed during this interval. The connections are now kept alive with the algorithm and configurable variable described in Bugfix RT47489. Fixed Permission Error when editing a page in a channel without permission to see the master node. When offline pages are imported, sometimes the pages are left in status “being edited“ instead of “offline” on the target system. This has been fixed now. The documentation about filesystem attributes has been extended to contain information about handling filesystem attributes in CRSync. Saving complex dependencies between objects sometimes failed due to insufficient space in a database column, subsequently causing failure to the publish process. This column was adjusted accordingly. Also, publish log entries were improved for removing objects from contentrepositories without multichannelling functionality. Various Oracle MySQL 5.6.12 compatibilty issues were resolved. For more information please check the compatibility list Localizing a channel was erroneously bound to the “delete folder“ permission in the backend ui. Now the “create folder” permission is checked. A feature “always_allow_page_create_variant” has been added to allow for backwards compatiblity for installations that rely on the user‘s ability to create a page variant without edit permissions, a bug that has been fixed in RT54981 (5.12.18 and 5.13.5) In order to avoid massively overblown log files, certain non-critical warnings concerning objects that have previously been deleted are no longer included in the publishing log. Aloha Editor – gcnfileupload plugin: Fixed the text color in the modal dialog being inherated from the page. Fixed possible publish error for very long running publish processes when multithreaded publishing is used. Before making an editable part “not editable”, the user will now be informed that all existing values for that part will be lost. A bug has been fixed that prevented GCNJSAPI from editing tags in frontend mode. Also, the documentation has been updated to clarify the scope of usefulness of $cms.rendermode.frontend and $cms.rendermode.backend Fix possible SGB when pressing F5 in the browser while having the user form open. Fixed possible multithreading problem when publishing pages into multichannelling content repository using multithreaded publishing. Chaining calls onto the edit() function will now results in the chained functions being queued and processed in the correct order in which they are called. Therefore `javascript tag.edit(onEdit).save(onSave)` will now correctly invoke onEdit() first before calling onSave(). Restoring certain forms (eg. folder or file properties) could lead to an SGB error due to an invalid attempt to recreate the form from the session. If data is missing now to re-create a form a new form will be generated. Previously, if you didn‘t define a “macros“ part (or “template“ part) for a velocity part rendered by another velocity part, the “macros“ part (or “template“ part) of the “outer“ velocity part would be incorrectly inherited to the “inner“ velocity part for the duration of rendering. Now, the velocity part only looks at the current tag when it is searching for a “macros“ part (or a “template” part). Error messages emitted when calling unimplemented methods of the GCN JS API Node objects will now have their arguments passed in the correct order. Saving multiple tags with recursive callbacks, passed throw tag.save(), will no longer result in only the first tag‘s changes being sent to the backend. The rendering performance was improved. Especially overviews will now render faster. It was possible that the migration job for the dirted objects, which should run only once after the update from an older GCN version was triggered more than once. This has been fixed now. Some database indices have been added to speed up channel specific queries. This will increase rendering performance of pages in channels that use lot‘s of other pages (e.g. overviews). Mandatory tags: Fixed small typo in the error message when publishing a page. Fix some SQL statements to no longer use subselects, which do not perform on MySQL under specific circumstances. This fixes bad performance when getting objects for multichannelling. The memory consumption of the server while writing pages into the filesystem has been reduced. Before this fix, if large numbers of pages had to be written to the filesystem, the total amount of all page contents had to fit into the server memory, which could lead errors in the publish process due to OutOfMemory exceptions. Fixed possible “hanging” of publish process when using multithreaded publishing. When handling a dirtqueue event fails, the event will now be marked as failed (together with the reason) in the database. Before this fix, handling the event was tried again, which possibly delayed starting of the publish process until the failure reason was removed. Editables that are contained in blocks which become wrapped (because their root element is not among those configured in allowed rootTags) will now still activate properly and show the correct floating menu configuration. Manual Change A typo in the tag type migration post processor option name was fixed. It was renamed from TAGTYPEMIGRATION_POSTPROCESSTORS to TAGTYPEMIGRATION_POSTPROCESSORS When a node is detached from a ContentRepository, the node data will be removed from the ContentRepository at the start of the next publish run instead of a separate maintenance task. Removing the data is done more efficient now and will be done in single transactions per object, if the ContentRepository is configured to use instant publishing. Due to changes in permission handling, users without user administration rights were not able to access several dialogs concerning their personal user settings. After this fix, access to these settings now again depends on their correctly associated permissions only. Various issues in the Tag Type / Template Migration feature were fixed. Fixed possible error in the publish process due to a lock on the table node (e.g. caused by an import process running at the same time). Improved performance and added logging for dirt migration task (the task, that is done once after updating from Gentics Content.Node versions <= 5.12). The table columns that will hold the check result of contentrepository have been increased to hold up to 4GB of data each. When a file was to be published, and then deleted during the publish process, a failed constraint caused the publish run to fail. This issue was fixed, and the described situation no longer causes a publisher failure. The visual appearance of the log table header row has been changed. Previously each row header was clickable in order to sort the elements. The sorting of logs is not supported. The log column have been updated in order to visualize this limitation. A user will now need edit permission on a page in order to create a page variant of it. Fix bug that prevented publishing of pages that were dirted using the maintenance dialog when versioned publishing was disabled. Fix creation of user without a group due to not running (or not reachable) internal Tomcat. Additionally prohibit login with a user that is not member of a single group. When a file is renamed using the backend, and the entered new filename contains illegal characters, there will be no warning any more, but the illegal characters will be replaced in the same way as when uploading a new file. The REST API will now return an error when a folder create request publishdir field value contains more than 255 characters. Previously a generic database error would be returned. Fixed filename verification regular expression. It is now possible to include the following characters in filenames. When a user tries to publish a page that misses some mandatory tags, a message will now be shown, telling that the page could not be published. A performance issue within the REST API folder/getPages method was resolved. It is now possible to add contenttags and objecttags references using the contenttags and objecttags query parameter. Previously all contenttags and objecttags for the pages were returned. Additionally the referenced template also included all objecttags and templatetags. This issue affected 5.13.0 and newer versions. Fixed the display of pages to be published/delayed on the start screen to not include pages in nodes, that have updating the filesystem/ContentRepository disabled. Additionally, the nodes that have updating the filesystem/ContentRepository disabled will be marked in the maintenance dialog. Fixed possible database lock during a publish run that could cause an error while deleting a file. Manual Change Validation feature: Fixed special characters like umlauts in strings (eg.: filenames when uploading files), causing the strict AntiSamy validation to fail. AntiSamy is now updated to version 1.5.2, which introduces a new setting “entityEncodeIntlChars” that can disable the encoding of special characters. A race condition producing exceptions on concurrent database accesses (e.g. multithreaded page create REST calls) has been fixed. Overview: Fixed pages that were marked for publishing and then delayed in the “Maintenance”, not showing up in overview listings when publishing the page again. The delay_publish value was not cleared when the page was published. Creating files in the REST API where the number suffix (name_number.extension) in the given filename exceeded maximum integer limits previously caused an exception. The algorithm calculating filename suggestions for existing filenames has been improved to avoid these issues in the future. New object tags are now correctly prefilled with the default values of the underlying tagtype in the tag fill form. The behavior of instant publishing was changed to disable immediate removal of deleted objects in ContentRepositories when deleting multiple objects at a time. Import/Export: Fixed the automatic export download system (via URL) not working anymore because the export system denies the connection. Feature Live URLs: Fixed liveurl icon not being displayed in the page list sometimes. When listing the templates included in an export, the used SQL statement was very inperformant and could take a very long time. This has been fixed now, display of templates is much faster now. Long running imports caused some unnecessary locks in the DB, which caused problems while changing objects (pages, folders, ...), even if those objects were not touched by the import. Those unnecessary locks will be avoided now, so that modification of unrelated objects or creation of new objects will be possible now. It is however still the case that objects, which were modified by the import will be locked by the database until the import process finishes. This fix improves visibility constraints for the tagmap editor if the user does not have permission to access it by removing it from the menus of the contentrepository, thus avoiding permission exceptions. When the data should be checked or repaired in a content repository and this caused an Exception (e.g. due to connection problems, an invalid URL, locking issues, ...), the task to do the checking/repairing remained in the dirtqueue until the problem was resolved. This blocked all subsequent dirtqueue entries, including the publish process. This behaviour has been fixed now, Exceptions thrown during the checking/repairing process will now be logged as result of the action (visible in the UI for the content repository) and the dirtqueue entry will be removed. Fixed saving pages not working when the magiclink tagtype “gtxalohapagelink“ was not linked to the node where the page is in. When clicking “Save” in the menu it appearently didn‘t do anything. Folder property dialog now disables the form fields and removes the OK button if you are not allowed to change the folder properties. Fix possible not threadsafe usage of the database driver when using multithreaded publishing to write into several ContentRepositories during very long publish runs. If your setup only allows for HTTPS access to your backend and REST-API, you can enable the Secure flag in session cookies by activating the “secure_cookie” feature. When authenticating via REST API, Session secret cookies are now sent with the HttpOnly flag set. It is now possible to resolve the stag prefix (‘/.Node/‘) and the proxy prefix within the custom form tag part using the following tags: When trying to save text values with more than 255 characters into a text (short) attribute of an MCCR datasource, the value will now be truncated (and a warning will be logged). Before this fix, publishing too long values into a database, that does not automatically truncate (like Oracle) failed with an SQLException. Improved the error handling for unchecked exceptions, that might be thrown while publishing into a content repository. It is now possible to save changes to a content object‘s cdate via the GCN JS API Aloha.GCN.openTagFill() would result in an error when trying to open it to edit object tags, this behavior is now fixed. When a language variant of a page was synchronized with another language variant, and that other language variant was deleted afterwards, getting the page with its translation status using the REST API caused a NullPointerException. This has been fixed now. Fixed a minor bug that sometimes caused flag icons not to be shown for start pages set in a folder. When using the Gentics Content.Node Javascript API and node.js to upload a File into a Channel, the File was uploaded into the Master Node instead. This has been fixed now, uploading files into channels is now possible using node.js. Aloha Editor Fixed possible DB locks during a publish process that caused problems when editing pages. This also fixes possible errors at the start of a publish process (because a lock could not be acquired). When exporting, export warnings were generated for excluded objects. This is fixed now, export warnings are generated only for non-excluded object types. When getting pages from a folder via the REST API with the inSync parameter set, an exception was thrown if pages were synchronized with another page that could no longer be found on the system (i.e. was deleted). When starting a multithreaded publish run, all tables were locked while connections were started, in order to get a 100% consistent state among those connections. When some other SQL Statement was already running at the same time, this could lead to DB locks, and could subsequently freeze the whole CMS. Therefore the tables will no longer be locked while starting the connections for a multithreaded publish run. When using instant publishing, this possibly caused DB deadlocks while accessing the ContentRepository DB during a publish process. This has been fixed now. Dependent pages were previously not dirted when a tag type was overwritten by an import. The new behaviour is to dirt all dependent pages whenever a tag type is changed. Links tags will have their anchor text cleaned before saving. This will ensure that wai-lang attributes will be cleaned up from GCN magic link tag anchor text before they are saved. Added guide about migrating from Live Editor to Aloha Editor GCN Rest API: Fixed /folder/getImages/ method returning images as type “file”. This also broke displaying the image width & height in the repository Browser thumbnail preview. When a local page inside a channel was translated and the language version did not exist yet, a new page in the target language was created in the master node. This was not intended and caused incorrect behaviour, and has been fixed now: the translation of a local page is now local as well. When using instant publishing for a content repository, the (regular) publish process used to create a new connection for every published object. This has been changed now, so that the publish process will open a single connection for every content repository, that is kept open while publishing, and only open a new transaction for every object, if instant publishing is used. Fix possible (but rare) NPE while finishing a multithreaded publish process. Instant publishing: Fixed error messages being shown for none-critical problems like Velocity rendering errors. Also fixed a Javascript error when the message included linebreaks. Fix the inability to set the startpage for new created folders over the page context menu. Setting the startpage could duplicate the object tags of the folder, which could also lead to subsequent errors. Tag-fill: Fixed the object name not being displayed (eg.: pages, ...) in a tag URL-part under certain (rare) circumstances when using multichannelling. This only happened when the page was created in a channel and was localized again in a subchannel of this channel. Pages were previously not dirted when only a template tag inside their template was changed, but the template itself was unchanged. Now, a change in a tag or its values also properly triggers dirting. Fixes an error that occurred during template migration when linking the target template with the folders linked with the source template. Improved permission checks for error log, workflow administration and inbox messages. Corrected a previous fix for a NullPointerException in the publish process due to a synchronization problem. Previously it was not possible to create two pages with the same name in different channels of the same master node. The same problem also appeared when creating two folders with the same name in different channels of the same master node. Now, you can create pages or folders with the same name in different channels, as long as one channel is not a master of the other. Optional Manual Change A potential security issue has been fixed. Important: If you are using Gentics Portal.Node Java with the GCNAuthenticationManager (e.g. for frontend editing), you have to update it first, before updating Gentics Content.Node. Optional Manual Change This release of Gentics Content.Node contains all bugfixes from 5.12.12 and below. This release of Gentics Content.Node contains all bugfixes from 5.12.12 and below. Improved documentation by adding a list of discontinued features. The new optional feature “move_perm_with_edit“ will modify the necessary permission for moving pages, images and files. If the feature is off, users will need to have the “delete“ permission in the source folder, which is the same behavior as before this enhancement. If the feature is on, users will need to have the “edit“ permission in the source folder for moving objects to other folders. In all cases, users will need to have the “create” permission in the target folder. The template and tagtype migration feature was added to Gentics Content.Node. This feature allow the node administrator to migrate pages using a predefined mapping. More information about the feature can be found within the guides. The minified version of the Gentics Content.Node Javascript API will now be used within Gentics Content.Node. Previously only a concatenated version was used. GCN JS API‘s pubsub message channels and guides have been improved. The following message are new: The internal dirting mechanism has been changed. The new mechanism offers the following advantages: After the update, the system will have one additional maintenance task scheduled (that will be performed before the next publish run). This maintenance task will migrate the currently dirted objects to the new mechanism. See Content Maintenance for more information about the maintenance tools. It is now possible to create multichanneling Content.Repositories. See Multichannelling aware content repository for more information about this feature and on information about configuration and further settings. We no longer load all constructs that are available across en entire system when editing a page with Aloha Editor becuase this can result in large payloads that slow down page load times. We now only load constructs that are either in the same node as the page being edited, or are used by tags in that page. The list of nodes in the backend will now show with icons, which nodes have publishing disabled, which nodes will be published into the filesystem and which nodes will be published into a content repository. Added support for configurable RequestDecorators to intercept and modify requests to the GenticsImageStore. The internal storage of objects, that can be localized (using multichannelling) has been modified. Before this fix, objects (pages, folders, templates, files and images) were initially created with channelset_id = 0. When the objects were localized, a new channelset_id was assigned. This caused some additional overhead in handling channelset_ids and could cause some problems. Therefore, when objects are created, they will immediately get a non-zero channelset_id. Also this update will change all existing objects to have a non-zero channelset_id. In some cases the page status was not handled correctly. This caused the publish process to ignore some pages. This defect first appeared in 5.12.27 / 5.13.11. This issue was now resolved. The REST API getItems performance for folders with many pages was improved. Fixed export selection in multichanneling environments. Previously, if you added a folder that has been created in a channel in the channel where it was created, its contained elements would not be automatically selected as dependencies. Import: Fixed setting permissions when important content repositories. When the import was started with a different group, it did not get permissions on the new content repository. The chosen group and all parent groups will now get permission on the content repository when doing imports. Fixed GCNs internal sorting function not respecting whitespace in strings like MySQLs sorting does. This caused the repository browsers to sort entries (nodes, folders) with whitespaces in the name differently than the main GCN node tree did. A performance issue has been fixed that slowed down the listing of files/images in folders with a big number of files/images. Fixed the assignment of constructs to nodes during the import. Create page: Fixed error that ocurred when no filename was given and there was another file in the same publish path with an empty filename. Also fixed broken i18n translation for this error messages. Import: Fixed permission bug when importing content repositories. The group used for importing never got the “Assign user permissions”-permission flag. Therefore users were never able to grant permissions for imported content repositories to other groups. When a page that has no language set shall be translated or modified in a specific language, the user will now be informed that he has to set the page language first. This will reduce the chance of users unexpectedly overwriting the page‘s content with another language. Setting references to other objects during an import has been fixed. Before this fix, objects were possibly overwritten (even if they should not have been changed) and references could be lost during an import. When uploading images using the REST API, some temporary files named imageio*.tmp were created and left open until the garbage collector would remove them. This could lead to a “Too many open files” error. This has been fixed now, those temporary files are now removed as soon as they are no longer needed. Fixed possible NPE when running a multithreaded publish process, where pages needed to be published, because they were scheduled with the “publish at” action. Fixed too strict security check when linking workflows to folders. Before this fix, linking workflows to folders was only possibly, when the user had the permission to manage the workflows, now the permission to link workflows is sufficient. The top menu was incorrectly positioned in the translate page view. This has been fixed now. If an online page is moved to a different folder and taken offline, it is now possible to create a new page having the same filename. With this fix, it is possible to subsitute an online page with a new page having the same filename, even if a wastebin workflow moves the old page away and takes it offline instead of deleting it. Synchronizing the scrollbars in the translate page view did not work anymore and has been fixed. LDAP Login: Fixed the LDAP Advanced Groups feature not working, when the LDAP server (ie.: Microsoft Active Directory) doesn‘t have objectclass=groupofUniqueNames & “uniquemember“ enabled. In this case please enable the following feature in your node.conf: LDAP Login: Fixed LDAP login being case sensitive when using advanced groups and fixed SGB occuring when a LDAP group couldn‘t be found in GCN. Under some circumstances, page-editable template tags were previously not correctly inherited when using multichanneling. Now a page created in a channel always inherits from the relevant channel version of the template. Fixed in backend as well as in REST page/create. Fixed a bug that prevented starting due scheduler jobs because of a database inconsistency. Publish runs that remove many objects from a content repository at once can lead to idle database connections, which in certain circumstances could be closed during this interval. The connections are now kept alive with the algorithm and configurable variable described in Bugfix RT47489. When offline pages are imported, sometimes the pages are left in status “being edited“ instead of “offline” on the target system. This has been fixed now. The documentation about filesystem attributes has been extended to contain information about handling filesystem attributes in CRSync. Various Oracle MySQL 5.6.12 compatibilty issues were resolved. For more information please check the compatibility list Localizing a channel was erroneously bound to the “delete folder“ permission in the backend ui. Now the “create folder” permission is checked. A feature “always_allow_page_create_variant” has been added to allow for backwards compatiblity for installations that rely on the user‘s ability to create a page variant without edit permissions, a bug that has been fixed in RT54981 (5.12.18 and 5.13.5) In order to avoid massively overblown log files, certain non-critical warnings concerning objects that have previously been deleted are no longer included in the publishing log. Aloha Editor – gcnfileupload plugin: Fixed the text color in the modal dialog being inherated from the page. Fixed possible publish error for very long running publish processes when multithreaded publishing is used. Before making an editable part “not editable”, the user will now be informed that all existing values for that part will be lost. A bug has been fixed that prevented GCNJSAPI from editing tags in frontend mode. Also, the documentation has been updated to clarify the scope of usefulness of $cms.rendermode.frontend and $cms.rendermode.backend Chaining calls onto the edit() function will now results in the chained functions being queued and processed in the correct order in which they are called. Therefore `javascript tag.edit(onEdit).save(onSave)` will now correctly invoke onEdit() first before calling onSave(). Restoring certain forms (eg. folder or file properties) could lead to an SGB error due to an invalid attempt to recreate the form from the session. If data is missing now to re-create a form a new form will be generated. Previously, if you didn‘t define a “macros“ part (or “template“ part) for a velocity part rendered by another velocity part, the “macros“ part (or “template“ part) of the “outer“ velocity part would be incorrectly inherited to the “inner“ velocity part for the duration of rendering. Now, the velocity part only looks at the current tag when it is searching for a “macros“ part (or a “template” part). Error messages emitted when calling unimplemented methods of the GCN JS API Node objects will now have their arguments passed in the correct order. Saving multiple tags with recursive callbacks, passed throw tag.save(), will no longer result in only the first tag‘s changes being sent to the backend. Fix some SQL statements to no longer use subselects, which do not perform on MySQL under specific circumstances. This fixes bad performance when getting objects for multichannelling. Manual Change It is now possible to deactivate tags using the GCN JS API. Newly created tags will be automatically activated, but before the page is saved, that tag can be deactivated. Some database indices have been added to speed up channel specific queries. This will increase rendering performance of pages in channels that use lot‘s of other pages (e.g. overviews). Mandatory tags: Fixed small typo in the error message when publishing a page. The memory consumption of the server while writing pages into the filesystem has been reduced. Before this fix, if large numbers of pages had to be written to the filesystem, the total amount of all page contents had to fit into the server memory, which could lead errors in the publish process due to OutOfMemory exceptions. Fixed possible “hanging” of publish process when using multithreaded publishing. When handling a dirtqueue event fails, the event will now be marked as failed (together with the reason) in the database. Before this fix, handling the event was tried again, which possibly delayed starting of the publish process until the failure reason was removed. Editables that are contained in blocks which become wrapped (because their root element is not among those configured in allowed rootTags) will now still activate properly and show the correct floating menu configuration. When a node is detached from a ContentRepository, the node data will be removed from the ContentRepository at the start of the next publish run instead of a separate maintenance task. Removing the data is done more efficient now and will be done in single transactions per object, if the ContentRepository is configured to use instant publishing. Due to changes in permission handling, users without user administration rights were not able to access several dialogs concerning their personal user settings. After this fix, access to these settings now again depends on their correctly associated permissions only. Fixed possible error in the publish process due to a lock on the table node (e.g. caused by an import process running at the same time). The table columns that will hold the check result of contentrepository have been increased to hold up to 4GB of data each. When a file was to be published, and then deleted during the publish process, a failed constraint caused the publish run to fail. This issue was fixed, and the described situation no longer causes a publisher failure. The visual appearance of the log table header row has been changed. Previously each row header was clickable in order to sort the elements. The sorting of logs is not supported. The log column have been updated in order to visualize this limitation. A user will now need edit permission on a page in order to create a page variant of it. Fix creation of user without a group due to not running (or not reachable) internal Tomcat. Additionally prohibit login with a user that is not member of a single group. When a file is renamed using the backend, and the entered new filename contains illegal characters, there will be no warning any more, but the illegal characters will be replaced in the same way as when uploading a new file. The REST API will now return an error when a folder create request publishdir field value contains more than 255 characters. Previously a generic database error would be returned. Fixed filename verification regular expression. It is now possible to include the following characters in filenames. When a user tries to publish a page that misses some mandatory tags, a message will now be shown, telling that the page could not be published. Fixed possible database lock during a publish run that could cause an error while deleting a file. Manual Change Validation feature: Fixed special characters like umlauts in strings (eg.: filenames when uploading files), causing the strict AntiSamy validation to fail. AntiSamy is now updated to version 1.5.2, which introduces a new setting “entityEncodeIntlChars” that can disable the encoding of special characters. A race condition producing exceptions on concurrent database accesses (e.g. multithreaded page create REST calls) has been fixed. Overview: Fixed pages that were marked for publishing and then delayed in the “Maintenance”, not showing up in overview listings when publishing the page again. The delay_publish value was not cleared when the page was published. Creating files in the REST API where the number suffix (name_number.extension) in the given filename exceeded maximum integer limits previously caused an exception. The algorithm calculating filename suggestions for existing filenames has been improved to avoid these issues in the future. New object tags are now correctly prefilled with the default values of the underlying tagtype in the tag fill form. The behavior of instant publishing was changed to disable immediate removal of deleted objects in ContentRepositories when deleting multiple objects at a time. Import/Export: Fixed the automatic export download system (via URL) not working anymore because the export system denies the connection. Feature Live URLs: Fixed liveurl icon not being displayed in the page list sometimes. When listing the templates included in an export, the used SQL statement was very inperformant and could take a very long time. This has been fixed now, display of templates is much faster now. Long running imports caused some unnecessary locks in the DB, which caused problems while changing objects (pages, folders, ...), even if those objects were not touched by the import. Those unnecessary locks will be avoided now, so that modification of unrelated objects or creation of new objects will be possible now. It is however still the case that objects, which were modified by the import will be locked by the database until the import process finishes. This fix improves visibility constraints for the tagmap editor if the user does not have permission to access it by removing it from the menus of the contentrepository, thus avoiding permission exceptions. When the data should be checked or repaired in a content repository and this caused an Exception (e.g. due to connection problems, an invalid URL, locking issues, ...), the task to do the checking/repairing remained in the dirtqueue until the problem was resolved. This blocked all subsequent dirtqueue entries, including the publish process. This behaviour has been fixed now, Exceptions thrown during the checking/repairing process will now be logged as result of the action (visible in the UI for the content repository) and the dirtqueue entry will be removed. Fixed saving pages not working when the magiclink tagtype “gtxalohapagelink“ was not linked to the node where the page is in. When clicking “Save” in the menu it appearently didn‘t do anything. Folder property dialog now disables the form fields and removes the OK button if you are not allowed to change the folder properties. Fix possible not threadsafe usage of the database driver when using multithreaded publishing to write into several ContentRepositories during very long publish runs. If your setup only allows for HTTPS access to your backend and REST-API, you can enable the Secure flag in session cookies by activating the “secure_cookie” feature. When authenticating via REST API, Session secret cookies are now sent with the HttpOnly flag set. Improved the error handling for unchecked exceptions, that might be thrown while publishing into a content repository. It is now possible to save changes to a content object‘s cdate via the GCN JS API Aloha.GCN.openTagFill() would result in an error when trying to open it to edit object tags, this behavior is now fixed. When a language variant of a page was synchronized with another language variant, and that other language variant was deleted afterwards, getting the page with its translation status using the REST API caused a NullPointerException. This has been fixed now. Fixed a minor bug that sometimes caused flag icons not to be shown for start pages set in a folder. When using the Gentics Content.Node Javascript API and node.js to upload a File into a Channel, the File was uploaded into the Master Node instead. This has been fixed now, uploading files into channels is now possible using node.js. Aloha Editor Fixed possible DB locks during a publish process that caused problems when editing pages. This also fixes possible errors at the start of a publish process (because a lock could not be acquired). When exporting, export warnings were generated for excluded objects. This is fixed now, export warnings are generated only for non-excluded object types. When getting pages from a folder via the REST API with the inSync parameter set, an exception was thrown if pages were synchronized with another page that could no longer be found on the system (i.e. was deleted). When starting a multithreaded publish run, all tables were locked while connections were started, in order to get a 100% consistent state among those connections. When some other SQL Statement was already running at the same time, this could lead to DB locks, and could subsequently freeze the whole CMS. Therefore the tables will no longer be locked while starting the connections for a multithreaded publish run. When using instant publishing, this possibly caused DB deadlocks while accessing the ContentRepository DB during a publish process. This has been fixed now. Dependent pages were previously not dirted when a tag type was overwritten by an import. The new behaviour is to dirt all dependent pages whenever a tag type is changed. Links tags will have their anchor text cleaned before saving. This will ensure that wai-lang attributes will be cleaned up from GCN magic link tag anchor text before they are saved. Optional Manual Change A potential security issue has been fixed. Important: If you are using Gentics Portal.Node Java with the GCNAuthenticationManager (e.g. for frontend editing), you have to update it first, before updating Gentics Content.Node. Accessing a page or a folder from the history on the start screen caused an error in the tree if the action was issued directly at the start of a session. This issue has been fixed. Improved permission checks for error log, workflow administration and inbox messages. Corrected a previous fix for a NullPointerException in the publish process due to a synchronization problem. Previously it was not possible to create two pages with the same name in different channels of the same master node. The same problem also appeared when creating two folders with the same name in different channels of the same master node. Now, you can create pages or folders with the same name in different channels, as long as one channel is not a master of the other. GCN Rest API: Fixed /folder/getImages/ method returning images as type “file”. This also broke displaying the image width & height in the repository Browser thumbnail preview. When a local page inside a channel was translated and the language version did not exist yet, a new page in the target language was created in the master node. This was not intended and caused incorrect behaviour, and has been fixed now: the translation of a local page is now local as well. When using instant publishing for a content repository, the (regular) publish process used to create a new connection for every published object. This has been changed now, so that the publish process will open a single connection for every content repository, that is kept open while publishing, and only open a new transaction for every object, if instant publishing is used. Fix possible (but rare) NPE while finishing a multithreaded publish process. Instant publishing: Fixed error messages being shown for none-critical problems like Velocity rendering errors. Also fixed a Javascript error when the message included linebreaks. Fix the inability to set the startpage for new created folders over the page context menu. Setting the startpage could duplicate the object tags of the folder, which could also lead to subsequent errors. Tag-fill: Fixed the object name not being displayed (eg.: pages, ...) in a tag URL-part under certain (rare) circumstances when using multichannelling. This only happened when the page was created in a channel and was localized again in a subchannel of this channel. Pages were previously not dirted when only a template tag inside their template was changed, but the template itself was unchanged. Now, a change in a tag or its values also properly triggers dirting. Old values in tags which already existed on the target system, but have been changed since, were not removed properly during import, resulting in duplicate entries. This has been fixed now. Fixed possible SGB when creating new folders. Fixed instant publishing of folders when the folder startpage was set the first time using the page context menu. Before this fix, instant publishing of the folder was only triggered when the startpage was set using the object properties dialog, or when the startpage was changed. When creating a new channel, the root folder will now get its object properties set identical to the object properties of the immediate parent node. The root folder of a channel was missing the object properties, that are assigned to the master node. Only the object properties that are available to all nodes were possible to use. This has been fixed now. The root folder of a channel will now have the same object properties available as any other folder of the channel (and the master node). On pages where the dir=“rtl” attribute is specified for languages that read from right to left, the GCN menu wasn‘t displayed correctly sometimes if the menu entry contained special characters. This is now fixed. Reduced the memory consumption when deleting big folder structures to avoid possible OutOfMemory situations e.g. when deleting nodes that contain many folders. Folders that were fetched using the GCN JS API‘s FolderAPI.folders() method will now have their tags available when they are needed. When using quick recursive translation to create language variants, an issue in caching caused newly created pages not to be displayed in the page list. This has been fixed. Editing pages: Fixed the error “GCN ERROR (AJAX_ERROR)” sometimes occuring when doing another action after a previous one too fast (eg.: Editing a page and then immediately publishing it). The src url of the preview image in Image Editing Tool will no longer be a broken url when cropping or resizing the image in front-end editing through a proxy. The proxy prefix will now be prepended to the preview image‘s url. The object lists for localizable objects (folders, pages, templates, files and images) in channels have a column Master that should show the name of the node, to which the master object belongs to. This column however showed the name of the node, the displayed object belongs to, which made channel-local and localized objects indistinguishable. This has been fixed now, the Master column will now show the current channel for channel-local objects and the name of the node/channel, where the master object belongs to for localized objects. Internet Explorer 8, in “Browser Mode: IE8“ / “Document Mode:IE7-Standards”, will no longer warn that a script is taking a long time to complete when initializing an page that contains many tags. When a page with page variants is published, the page variants also get new page versions created. Due to a caching error, it sometimes happened, that although a new version was created for the page variants, the next publish process rendered the older version of the page variant. This has been fixed now, so that when a page variants gets a new version created, the cache will always be cleared and that new version will always be published during the next publish run. Several issues in the export selection dialog have been fixed: Pagination was added for content tags and template tags when using the repository browser. It is now possible to navigate through and choose from multiple pages of tags in a tag fill. When a user or a group was deleted in Gentics Content.Node, it was not deleted in the todo tool during synchronization. Also, deleting a group did not trigger synchronization at all. Both issues have been fixed. Manual Change The implementation of the Aloha Editor Page Link Tagtype in the guides contained an error. This erroneous implementation caused multiple problems when editing pages containing links, among them the inability to remove the links. It is strongly recommended to update the implementation for the Aloha Editor Page Link tagtype according to the updated guides example. Fixed reloading the tree, when a new folder is created. Fixed a bug tied to menu permissions which caused a system error when viewing the languages of a node. Fixed handling exclusion/inclusion of templates in the new export. When a folder is exported that contains a template and templates are generally excluded, but the template is included, the template was show as being exported, but was marked as excluded in the export file. This has been fixed now, when an object is marked as included, it will always really be included in the export. This change fixes a JS error that sometimes occurred when replacing tags via Javascript in Internet Explorer 8, caused by missing HTML closing tags. GCN JS API Frontend editing: Fixed javascript error when frontend editing is done without loading a page. GCN JS API Frontend editing: Fixed “callback is undefined” javascript error. Multithreading: Fixed a rare issue in which concurrent access to a translation table could cause publish workers to get stuck. Fixed i18n translation not working when GCN throws a SGB error. Fixed possible DB locks during a publish process, when instant publishing and the feature contentfile_auto_offline were used together. File upload: Fixed the button in the fallback file uploader (JS-uploader) not being clickable in IE 7 and IE 8. When exporting a folder that contains a template, which is never used and templates were generally excluded, the template cause an unresolvable conflict on the target system, if it did not exist there. This is not necessary, since the template would only have been exported, because it is assigned to the exported folder, and not because it is used by a page. The behaviour of exlusion has been modified now: Excluded objects will only create unresolvable conflicts, if they are really used by objects and not only assigned to folders or nodes. When using the old minibrowser (that is still used when the feature multichannelling is not turned on) in the tag fill dialog, when doing a search, any modified entries in the form fields were lost. This has been fixed now, using the search in the minibrowser will preserve any changes in the form fields now. When creating, saving or publishing pages using the REST API using multiple threads or clients, a database deadlock could occur while creating page versions. When this happened, some of the REST API requests failed and the changes made by them were rolled back. This deadlock situations have been fixed now, so it is now possible to create, save and publish pages in a multithreaded manner without any database deadlock problems. Fixed problems when using instant publishing and multichannelling: When objects were localized, the localized copies were instantly written into the content repository, but the former inherited object was not instantly removed. When localized copies were deleted, they were also instantly removed from the content repository, but the inherited object was not instantly written into the content repository. The behaviour has been fixed now, so that always either the localized copy or the inherited object is present in the content repository (exclusively). Page languages: Fixed setting the language of a page using “Set page language“ added a language code to the filename, even when the feature “contentgroup3_pagefilename” was set to false. Export: Fixed SGB error occuring when selecting a object type in the Administration/Content.Admin and no objects of this type have been selected. Also fixed SGB occuring when viewing files in the administration, independent of if files have been selected or not. File upload: Fixed the file uploader not working when the flash version was too old. It now always correctly falls back to the Javascript uploader in this case. Fixed a possible NullPointerException during the publish run due to a rare threading problem. Fixed a bug that caused incorrect rendering of static URLs in projects, that publish only into a content repository, but not into the filesystem. Publishing of page variants together (with a single request) did not work and always resulted in an error message due to a database lock. This has been fixed now. Export: Added back missing images to the left assistent sidebar Page time management: Fixed SGB occuring when setting a date with a year above 2037. The highest year setable in GCN is 2037. SQL cursors were sometimes not closed properly after an exception in the database has occurred. This has been fixed now. With this fix there is no longer an error if a folder object property is applied to subfolders where duplicate properties exist. Instead, the inconsistency is cleaned up at this point. Multichannelling: Fixed multiple bugs when linking templates from channels to other folders. Fixed the template link function allowing linking templates to folders that shouldn‘t be linkable. Now it‘s not possible anymore to link templates to localized folders. In channels, templates can only be linked to local folders or folders of the master node. It‘s also not possible anymore to link local templates from channels to other nodes. Also fixed that linking localized templates to other node folders didn‘t work correctly. Now it correctly links the master template, and not the localized template. More information on the multichannelling feature can be found in the GCN guides. Mandatory tags: Fixed possible error occuring when publishing a page with a mandatory tag that has a missing value. Also fixed that tags appears multiple times in the error message. If an import references an object (like a URL or an image) that does not exist on the target system, this reference no longer points to another target on the system, but is set to be empty until the referred object is added. Fixed a bug that that caused the create folder dialog to be redisplayed after creating a new folder (instead of returning to the page list of the parent folder). Because of an issue in the GCN JS API, it was sometimes not possible to insert Javascript into a tag in live editing mode when using Firefox. This fix corrects this behaviour. Pages preview: Fixed broken menu when following a content link to another page in GCN. The menu now also works when going to a new page. Also going from this new page to the folder view works now correctly. File Upload Manipulator: Fixed the timeouts for accessing the FUM-URL being too short. Before the fix, accessing the FUM sometimes resulted in a socket-timeout. The timeout for establishing the connection has now been set to 5000ms and the timeout for reading the FUM response has been set to 15000ms. Additionally, the exception-logging on FUM errors has been improved. GCN JS API: Fixed the page property object “timeManagement” not being writeable. It is now writable, see the GCN JS API page documentation. When pages were moved between nodes, in some scenarios the page was not removed from the published filesystem of the source node. This has been fixed now. When pages are moved out of a node, that publishes into the filesystem, the page will no longer be written into the filesystem for that node. A performance issue with the overview part type was resolved. In some cases the part type would render multiple times slower than expected. Opening the tree to show a specific folder (e.g. because the preview of a page in a different than the current folder was shown) was done inefficiently and could take a long time. In extreme cases, this could lead to a blank frame shown instead of the tree. The performance of opening the tree has been improved now, so that blank frames should not happen any longer. An issue with navigation via history and quickjump was solved which caused node-information not to be passed. Sometimes this led to wrong tag-types being available when editing pages. Fixed closing database connections at the end of a multithreaded publish run. Under special circumstances, it could happen, that some database connections were left open for too long, which possibly could lead to too many open database connections. Fixed an incorrect title in the todo tool. Saving a page will now automatically strip all tags from it‘s name, e.g. ”Very important page“ will be changed to “Very important page” when saving. Removed a permissions check when using the ‘show usage‘ function since users are only shown results for objects they have permission to view anyway. This resolves an error that caused an SGB to be shown when results for the ‘show usage‘ search contained entries in folders the user did not have permission to view. Added missing guides documentation for appendBlock() Gentics Aloha Content.Node Intergration Plugin API method. After confirming the folder properties dialog the correct folder will be highlighted in the tree when using Multichannelling. Added indexes on the folder table to increase performance for multichannelling-enabled systems when looking up tree permissions. Fixed possible data inconsistencies with scheduler tasks. When a page is published and an error occurs while writing the page into the content repository (instant publishing), the user will now see an appropriate message. When using multithreaded publishing, it could happen that some database connections to the backend database were closed, because they were idle for too long (default setting is 8 hours). This could happen, if many pages were published into content repositories and writing the pages into the content repository took very long (actually more than 8 hours longer than rendering all the pages). This has been fixed now: All open database connections to the backend will regularly (every hour) be kept alive by issuing a dummy statement. Fixed a bug where a false-positive error message would occur when clicking “OK” in the folder properties dialog of a localized folder in a channel. Fixed reloading the tree too often, when opening the preview of pages in the backend. The display of remaining pages on the start screen did not change when multithreaded publishing was used. This has been fixed now. Fixed localize() function in GCN JS API, which was broken in a previous release. When scheduler tasks were running longer than the configured wait_timeout of the backend database (defaults to 8 hours), the scheduler lost the connection to the database and could not set the endtime, return value and output of the job. This resulted in incorrect display of the job runs in the scheduler UI. Tasks, that took longer than 8 hours to run were not shown in the UI. This has been fixed now, so that also very long running tasks will be correctly shown in the job run list. A javascript error within the scheduler task view was fixed. In some cases a javascript error occured when the user triggered the delete action for a scheduler task. The error only occured for tasks that were used by other tasks. Fixed an issue with scrollbars being hidden in IFrames in Firefox 20. Groups of translators in the todo-tool are now sorted alphabetically to match the view in the administration tree. Fixed removing objects that were deleted in the backend from the content repository. When an object is removed during a publish run and the content repository has instant publishing enabled, it could happen, that the object would not be removed from the content repository in the following publish run. Fixed a multithreading problem when rendering multiple page variants containing a tag with a part of type “Table ext“ at the same time. This rare case could happen, when page variants with a “Table ext” part type were republished and multithreaded publishing was enabled. Before this fix, the tables were possible rendered incomplete (some cells were missing). Fixed JavaScript error “Cannot read property ‘tagname‘ of undefined gcnjsapi.js:5905” that occured when saving a page after creating a new link. The gcn-plugin will now also insert leading and following paragraphs for Contenttags with an inline element (e.g. span) as it‘s root tag, to enable editors to add contents before or after this tag. A bug was fixed that caused errors when editing image-URLs in tagtypes, if no node was previously selected. Previously, if the user selected a language and then changed to a node in which this language was not activated, newly created pages would wrongly be created with this locale. After this fix, the first active language of the node is used instead. Fixed an inconsistency that occurred when creating and editing templates. When adding template tags, a check is now performed to ensure that the tag type being used is also linked with the template‘s node. Previously all template tags were automatically linked with a default construct, which on some systems had been deleted. This led to errors while exporting to other systems since the template had a dependency that could not be resolved if the default tag type was no longer available. GCN JS API, TagAPI.removeTag(): Fixed the callbacks not getting called correctly. Also fixed the documentation. You can only pass the keyword of a tag in here, not an Id. Added an automatic reset of old (and no longer necessary) FTP node settings that have been leftover from older systems (those that have been updated from a version prior to Gentics Content.Node 5.4.0). Fixed a problem with paging when skipping to the last page of a list of items that would cause a list of empty items to be displayed. Fixed possible DB Lock Timeout when using instant publishing and an object was published during a long running publish process. Removed unnecessary attributes “text“, “cls“, “iconCls“ and “leaf“ from the Template model class. Before this fix, loading templates with the Java REST API client failed with: org.codehaus.jackson.map.exc.UnrecognizedPropertyException: Unrecognized field “text” (Class com.gentics.contentnode.rest.model.Template), not marked as ignorable. Lists: Fixed a bug where the list filtering did not work anymore, introduced with GCN 5.12.0. This problem occured among others in the object property list, the scheduler, datasources and import/export. GCN JS API: Fixed the tag.part() (prop) function overwriting the part value with ‘undefined‘ and returning ‘undefined‘. It now correctly returns the value again when not passing a value to set as second argument. A caching-issue was fixed that prevented custom sort orders for overview-tags to be updated correctly. Uploading images via the multifileupload now works even if the image does not contain JFIF-information. In this case, default values for DPI are assumed. This fix solves a temporary issue in the image-manipulation-plugin, which made it impossible to save changes to the image. This fix allows HTML-formatted text (like abbreviations or text-decorations) to be stored inside the text-field of a link, when using the Aloha-Editor plugin. Node list: Fixed the creator and the last editor of a node not being shown in the black tooltip. The documentation for the Custom Form Part Type was corrected. The correct name for the variable that is used to retrieve the html entity of a form is nodevalue. Fixed a SQL statement of the update process, which possibly failed. Added further log output when an error is encountered when rending tags, specifically for the case when an endtag has no corresponding opening tag, the name of the tag in question will now also be logged. Fixed a problem with tags being sometimes duplicated when viewing template sourcecode. A warning notification will now be displayed next to the href field of the Aloha Link plugin when it is detected that the href value may unintentionally result in an potentially invalid internal link. Please note that this release contains strict database checks. The update may fail when existing database inconsistencies are detected. Manual Change The Gentics Update site was changed with this update in order to provide the new Feature Releases. The new update site is https://updates.gentics.com. Please whitelist this domain and the port 443 on your server. The previous update site was https://secure.gentics.com. Please refer to the Autoupdate Guides Page for more information on how to provide the update file manually. The new feature contentfileauto_offline_ allows to configure nodes, for which images and files, that are not used by other objects (pages, folders) will not be published into the filesystem or contentrepository. It is now possible to flag template tags as “mandatory” and thereby force editors to fill all their required parts before the page in which they are in can be published. It is now possible to configure separate node publish directories for pages and binaries (images and files). All existing nodes will initially have the same publish directories set, so existing implementations will not change. Added a MessageAPI interface to the GCN JS API. This interface contains the following new methods: MessageAPI.send(), MessageAPI.list(), MessageAPI.read() Improved part() method of tag objects in GCN JS API to be able to change select and multiselect parts values by receiving strings, arrays, as well as objects. A possible SQL Error was fixed within the publish process. Implemented the feature “live_urls”. The feature can be enabled in the configuration with $FEATURE[‘live_urls‘] = true; The Gentics Content.Node Autoupdate was updated. It is now possible to update to any newer released version. The testing update site was depreciated. Only releases will be shown within the drop down menu. Added ‘pageStatus‘ attribute to page objects requested via the REST API. A possible bottleneck in the internal communication between PHP and Java was removed. Tags that contain script tags will now have their scripts tags properly rendered onto the page when closing the TagFill dialog. Furthermore, the scripts will only be executed after the rest of the contents of the tag have been rendered and are present on the page, and not before. The Gentics Content.Node Autoupdate Scheduler Task was deprecated. After a change in the messaging-system, confirmation-alerts were displayed even after successful actions. This was reworked to suppress alerts on success in order to improve usability. A workaround for a Microsoft SQL JDBC Driver issue was applied. Previously the publish process would stall when publishing directly in a Content.Repository that needed column changes. (eg. new quick columns) Fixed the two-column-menu, which is shown if the list of menu entries would not fit inside the browser-window, to be moved to the left if it would exceed the width of the frame otherwise. Fixed the sorting of folder names requested over the Rest API to correctly handle German special characters, which is relevant for features such as the Repository Browser. Media archive image import: Fixed SGB occuring after selecting an image in the media archive and returning to the tagfill dialog. The included profiler webapp file was renamed from profiler.war to Profiler.war. This also fixes the access path for the profiler from /profiler to /Profiler. A small error in the todo-tool was fixed that occurred during mouse-over of lists because of missing tooltip functionality. Fixed possible timeout problems when publishing into a content repository in a very long running transaction. When publishing into a content repository without using “instant publishing“, a database connection is opened at the beginning, which will be used during the whole publish process. There may be situations, where specific connections are not used for a long time (e.g. when many objects have to be published into another content repository), which may cause the database server (or any networking component in between the client and the server) to close the connection. To fix this, the publish process will regularly issue “dummy” SQL statements to all connections to content repository databases, if they were not used for longer than the configured time span. The interval can be configured in the variable $CONTENTMAP_KEEPALIVE_INTERVAL (in seconds), the default value is 3600 (1 hour). Fixed a possible NullPointerException when using Multithreaded Publishing into ContentRepositories. Node languages: Fixed a rare case where the language could not be sorted anymore, when it had a sortorder of 0. Also enhanced the listing order. Activated language will be listed at the beginning now. An error in rendering the URLs of files published to content repositories was fixed so that whether or not the links are stored with or without the hostname is now done as configured with Linkway. A permission check within the node properties dialog was fixed. Previously some users experienced an SGB error when trying to edit the properties of a previously created channel. When a non-editable block-element is inserted into an Aloha editable, an empty helper-paragraph is inserted at the beginning and/or end of the editable. Previous to this hotfix, these helpers were not correctly removed / cleaned up if the page was saved while an active focus was still inside the editable element. Avoid checking and generation of global IDs for tables, that contain data, that is not exported. Especially checking for global IDs of table perm could take very long and could possibly interfer with normal CMS operations for some time after the Tomcat is restarted. Publishing pages in channels into the filesystem did not work correctly, when multithreaded publishing was used. This has been fixed now. Fixed a performance issue while editing or publishing pages containing many (several hundred or thousand) tags, or having many language variants. Due to inefficient sql statements while clearing the cache for modified pages, e.g. filling a page tag or publishing the page could take very long. Fixed instant publishing of objects, that were localized in channels. Before this fix, the objects were rendered in the scope of their master node, not the channel. This caused e.g. URLs to be wrong, because they contained the hostname of the master and not the channel. The incorrect data in the content repository of the channel was automatically corrected during the following publish run. A javascript error was fixed that occured when the folder upload tag part was shown in a tagfill dialog that was opened within the frontend edting mode. Page list sorting: Fixed SGB occuring when ordering the list by page variations. This could only happen when the feature “pageusage_variants” was enabled. The page list, template list and folder list will now always use the Rest-API for loading the data. Previously the Rest-API was only used when multichannelling was enabled. Images and files are now handled separately in the REST-API (and the corresponding GCN JS API), which means file load requests can only be made with file IDs. Previously, file load requests could be made with image IDs to return the file properties of images. Fixed the language selection in the Todo-Tool. It now correctly displays only the languages activated in the active node, and does so in the order specified in the node by the custom sort order. Additionally, synchronizing users, groups and languages now works with significantly increased performance. Fixed premature publishing of pages that were created and then moved (without being published before) in a node that published into a content repository with instant publishing enabled. When comparing the current page version with the last published version, the comparison now falls back to a previously published version if the current version is unchanged since it was last published, so that the page is not compared to itself. Fixed changing the publish directory of a folder by saving it using the REST API or the GCN JS API.Before this fix, the publish directory of the saved folder was not changed. Added missing i18n translations for ‘Keyword‘ property when editing Tagtype properties. Fixed the dependency calculation & dirting of objects not correctly working for overview-tags with recursive folders.In some cases it didn‘t dirt & re-publish the overview, when a new object in a subfolder that is listed in the overview was published. Creating multiple folders and pages in a batch run using the GCN JS API nolonger results in content objects having wrong names, properties, and tags. A possible NPE was fixed that could occur while rendering overviews over pages. Fixed possible NPE, that lead to empty rendered overviews over pages, when multichannelling is not activated. Fixed initialization of Aloha Editor for frontend editing Fixed a possible NullPointerException when using Multithreaded Publishing into ContentRepositories. Manual Change The login url for sso logins was changed within the Gentics Content.Node JavaScript API The JavaScript API method loginWithSSO now uses the rest API url /rest/auth/ssologin Previously the /rest/auth/login url was used.See Authentication methods for REST API for more information. Improved documentation for gtxalohapagelink (http://www.gentics.com/Content.Node/guides/aloha_gcn_alohapagelink.html) as suggested.Now the class attribute won‘t be added if empty. Added method /CNPortletapp/rest/auth/ssologin as alternative to /CNPortletapp/rest/auth/login, so that the SSO filters can be mapped to /CNPortletapp/rest/auth/ssologinand login by posting user credentials to /CNPortletapp/rest/auth/login is still possible. Refactored the global JavaScript object named GCN to GCNREST in tagfill and object tag dialogs. This internal object would provide the Repository Browser with access to the REST backend services,creating a naming conflict with the GCN JS API. The GCN JS API may now be used in tagfill andobject property dialogs using a custom form tag, as the naming conflict is resolved with this change. Fixed confirmation-alerts in the context-menu to be displayed for critical actions like delete or publish, and omitted otherwise. Fixed check for duplicate node names and hostname/publish directory settings when creating or updating nodes.Before this fix, the create/update operation was not done, but no error was shown either. Fixed a problem with menu-items being unreachable on small screens or in large lists. If a submenu has more content than can be shown inside the browser window, menu-items are now arranged in a two-column-design. When $FEATURE[“logout_page”] is set to a URL and multiple browser-windows are used at once, there was a problem when the user logged out of the system in one window and tried to continue browsing Fixed the “maximize tree”-icon in the GCN tree frame not being at a fixed position and therefore was probably not visible if the treewas not scrolled to top. When multiple pages were created in the same script using the GCN JS API, the PageAPI were indistinguishable and e.g. tags created in them could get mixed up.This has been fixed now, so that it is now possible to create multiple pages in the same script. Added missing german translation for “add elements” when selecting objects in a overview tag A permission check within the rest api login method was fixed. Previously it was possible to login when the maintenance mode was enabled. Now login is only allowed for users that can enable/disable the maintenance mode. A bug within the custom form tagpart node tag parsing was fixed. Previously the node tags within the source of a custom form tag were only parsed when a custom form tag was editied within a page. It is now also possible to use node tags within the context of object properties for folders, pages, templates, files and images. Please note that only a small subset of tags can be evaluated when viewing the tag type within the tag type edit dialog due to the missing context of a page, file, template, image, folder. Fixed an error that occurred when uploading files with special characters in the filename. When viewing the tooltip for the tagtype-part URL, two overlapping tooltips were sometimes shown. Furthermore, when more than one parts with the type URL were present, only the first showed a tooltip. This has been corrected, and only one tooltip is shown at any time. Ensure that content tags are created for external links as well as internal links. Inserting tags into editables using the Internet Explorer sometimes moved the selection into a non-editable area in the tag. As a result, when another tag was insertedwith the incorrect set selection, the new tag was inserted into the other tag, not into the editable area.This has been fixed now, when tags are inserted with an invalid selection, the selection will first be corrected to be in a proper place (after the non-editable area). When translating a page into another language (which was not created before), the translation split-screen view showed a diff instead of the current page to be translated (in the upper frame).This has been fixed now. The diff view will only be shown, if the translation was synchronized with an older version of the page and is continued now. The edit() method within the Gentics Content.Node JavaScript API was fixed to correctly render tags onto elements when a class name isspecified as the selector rather than an id. Previously the edit() method would not work when a css selector was used to select the dom element that should be edited. Fixed dirting of dependent objects when the filename of a file or image was changed using the backend properties dialog. Ensured that clicking on an internal link will result in the floating menuand/or sidebar to be shown appropriately — even if the editable inwhich the linkis rendered is inside an aloha block. Fixed rendering order of pages in page overviews, where the pages are selected and sorted manually. Under certain preconditions, fields of page properties stayed empty. This has been fixed now. Fixed user/profile form stating that the description must be not empty in the tooltip. When exporting objects, for which no global IDs have been generated, a NullPointerException was thrown (and the export failed). This has been fixed now to throw a more descriptive error message (including the object name and id).Additionally, every time the server is started, missing global IDs are generated in a background job. The cas login functionallity was enhanced. It is now possible to add a cas post login handler that allows the modification of the user and the assigned groups.See HTTP Auth SSO Configuration for more information. It is now possible to sync Gentics Content.Node user-groups with CAS-SSO. After creating the user, the groups will be syncronized between CAS-Server and Gentics Content.Node.See Authentication methods for REST API for more information. Adding validation of editables before saving. If validation is enabled, validation will be performed on all editable at the offset of the savingprocess. If any editable fails validation, the saving process will be aborted with an error message. An additional column was added to the page publish queue. The node name will now be listed within the publish queue. When using the new export mechanism to export a construct that used a datasource (in a part) with datasources generally excluded, but the single datasource included, the datasourcewas excluded from the export but should have been included. This has been fixed now, so that objects that are manually included are exported in all cases, even if the type has been excluded. When filtering pages using the REST API or using the page list in the Gentics Content.Node backend, it was not possible to filter pages with status “Publish At”(pages that are scheduled to be published at a specific point in time in the future). This has been fixed now. The new feature crfilesystem_attributes_ allows publishing specific tagmap entries into contentrepository attributes that are stored in the filesystem.The feature is disabled by default. When a user did not have create permission for pages in any of his groups, but had the create permission for all languages in at least one of his roles, copying pages failedwith a SGB. This is fixed now, so that the user will now be able to copy pages. Fixed pasting with LiveEditor to avoid JavaScript error, and to insert content into the editor when performing Rechtsklick > “Einfgen (ohne Formatierungen)”. An issue that caused an exception to be thrown in some cases when checking for quick column definitions was fixed by adding handling for the deprecated binary attribute type. Following an internal link will now cause the top menu to be updated so thatthe top menu links will operate on the newly opened page, and not therefererring page. At the start of every publish process, that SQL statements issued to detect, when a specific node was published the last time were very inefficient and slow, becausethey used the very large table logcmd.The implementation has now been changed to store the timestamp of the last publish run for a specific node in the table ‘node‘ instead, which will decrease thetime necessary to initialize the publish process with a large number of nodes and a big logcmd table. Fixed Aloha.ready() being fired too early (before frontend editing is finished initializing editables). Added missing error message when setting hostname and publish directory of a node to settings of another node.Before this fix, the changes were just not saved, but no error message was shown. Using publish handlers together with instant publishing did not work as expected: When triggering instant publishing (by publishing a page or creating/editing an image, file or folder) beforea regular publish run, the publish handlers were not triggered.Additionally, the destroy() method of the publish handler was called for every transaction commit (for every published object), and not only when the publish handler was taken out of service (as intended).The lifecycle of publish handler instances has been modified, in a way that instances of publish handlers will now stay in service until either the server is shut down, or the publish handler entry is eitherchanged or removed. A SGB error was fixed within the file upload dialog. Previously the SGB error was displayed when a user tried to upload a new file in frontend editing mode. Prevent “Object doesn‘t support this property or method…” error when openingPreview or Live Preview in IE8. The “maximize tree”-icon was fixed within the Gentics Content.Node tree frame. Previously the icon was not being shown at a fixed position and therefore was probably not visible if the treewas not scrolled to top. Fixed canceling of a published page over the REST API: When a page is published (and not changed afterwards) and then canceled, the page status is not changed. Removed unnecessary entry “Real Editor” in the folder context menu. A caching issue within the purge versions job was fixed. In some cases this issue could cause the creation of lower version numbers for pages when a page was edited. When saving a page where only the case of some letters changed, it didn‘t create a new page version.This has been fixed now and new page versions are created now when the case of letters change.This is important when versioned publishing is enabled. The permission check on root folders of nodes/channels worked differently in Java and PHP, which could cause some nodes/channels to appear in the Repository Browser althoughthe user should not have permissions, when the permission entries in the database were inconsistent. Fixed SGB error occuring when applying an object property to sub folders. This is caused by duplicate object properties in the database. This update deletes those duplicate entries. The creation of page versions has been improved to be much faster, even if the page already has many versions. This increases the performance of saving and publishing the page via Java (REST API). The paging functionality within the page list was fixed. Previously the page list would only display 5/10/20/50 items depending on the configured paging setting. A SGB error was fixed within the Gentics Content.Node Image Import. Previously an error occured when a user tried to import a image into the system. This bug was introduced within version 5.9.4. A SGB error was fixed within the imageurl part type. This bug was introduced within version 5.9.4. Fixed the construct list method response for channel nodes. Previously a construct list call for a channel would reveal an empty list. Now the constructs for the master node will returned when a channel node_id was specified for the list request. The ribbon will no longer be shown when the setting Aloha.setting.ribbon has been set to false. A SGB error within the construct tagfill view was fixed. Previously the value of an image url part type could not be set. This issue was introduced in 5.9.0. The formatless paste plugin default configuration was fixed. Previously the formatless paste plugin did not work and no formatting was removed when content was pasted. The formatless paste handler was added to the list of default contenthandlers for insertHtml. The preview thumbnails in the repository browser were fixed when using frontend editing mode. Previously the proxyprefix parameter was not added to the thumbnail imageurls. Fixed folder highlighting within the main Gentics Content.Node folder tree within channels. Previously the master node folder was highlighted when a channel page was opened. Fixed rendering of tags to no cause a JavaScript exception. Also ensures thatids in template strings are correctly extracted and listed in the REST-APIrenderer response. A bug within the tagfill dialog imageurl and fileurl part handling was fixed. Previously the tagfill dialog views that contained imageurl or fileurl parts caused SGB errors when opening. This issue was introduced within 5.9.0 and did only occure when using the frontend editing mode. Some imageurls for the repository browser that can be opened within the tagfill dialog were fixed. Previously a css and some images could not be loaded when the tagfill dialog was opened within the frontend editing mode. The Gentics Content.Node JavaScript API will remove all “aloha-*” classes from links before saving them. The quickjump permission check was fixed. Now only the pages that can be viewed by the current user will be shown within the autocompletion.Previously all pages that matched the given query would show up.The pages could be clicked but they would not open because of the insuffient permissions. A bug was fixed that occured when creating new task events. Previously the new task events dialog would not open correctly. A constraint check for the name property of a page was added to the Gentics Conent.Node JS API. It will now no longer be possible to invoke a save call for a name that exceeds 255 characters in length. Additionally a error callback was added to the prop() method. The Gentics Content.Node Integration Plugin will now handle this situation as well. Saving pages that use an editable content to specifiy the page name will now no longer be possible. The user will be informed that the save action could no be performed due to the constraint violation. Fixed multiple methods in the RestAPI folder ressource, where a general exception would not be logged with a stacktrace. Fixed the search for objects (pages, ...) in the GCN folder advanced search page and in the RestAPI not workingcorrectly when a date like the creation date or last modification date was set. The cancel button within the new scheduler task view was fixed. Previously the cancel button did not return the user to the scheduler list. The order of buttons was changes so that the cancel button is right side of the view. The page list will now skip pages that have a detectable data inconsistency. Previously all pages for a folder would not show when at least one data inconsistency was detected. This also affects the getPages rest method. The Gentics Content.Node JavaScript API edit() method fixed to correctly render tags onto elements when a class name is specified as the selector rather than an id. Prevented circular references in object chains in GCN JS API from resulting in infinit recursion. The Gentics Content.Node JavaScript API will now save file urls correctly. Previously file urls would not be saved to the correct file url part type. The url will now be saved to the part with the keyword ‘fileurl‘. The REST API has a new option to not create a new page version when saving a page. See the REST API Documentation for details. Added more descriptive information to logged errors that may occur when publishing to content repositories. create of page versions and cancel editing the page has been improved.Page versions will only be created for save requests that were manually triggered by users.When a user cancels editing a page, the last page version will be restored.The REST request /rest/page/save/{id} has a new option to omit creation of page versions.Creation of new page versions is now logged (together with the version number). The gcn fileupload plugin will now use the Gentics Content.Node JavaScript API for handling uploads.The default upload folder for images and files will be used when one was specified for the current node.When no default upload folder was selected the parent folder of the page will be used. The Repository Browser will now adapt the pagesize to the available space. The GenticsImageStore will now also be able resize images in foreign nodes. A page in node A may now contain the following image url: Such an url will be identified by the GenticsImageStore during the publish process. The imagestore identifies the referenced node by examing the hostname within the found url. Added more descriptive information to logged errors that may occur when publishing to content repositories. The REST API call FolderResource.getFolders() has new options to get folders as trees and to do the recursion only for specified folders. The styling of the Repository Browser has been modified to better fit into the general UI style. The Repository Browser will now remember the last open state and the last selected folder, even when the page is refreshed. The REST API has a new resource to fetch node information (from /CNPortletapp/rest/node/...). See the REST API Documentation for details. It‘s now possible to search for folders by their ID and their description additionally to the name.Also a change was made for all kind of objects that the object ID will not be matched partially anymore. It is now possible to load various properties of a node using the Gentics Content.Node JavaScript API. Pages returned from the REST API will now also contain the languageName, if they have a language set. Reduced left padding of the tree from 30px to 10px to be able to display more information The Gentics Content.Node JavaScript API was enhanced. The folder method multipartUploadURL was added to the folder API. The GCN Intergration plugin will now preselet the node in which the use is working in. REST-API now fully supports multichannelling methods for File and Image content objects. It is now possible to configure the list of available tagtypes for adding new tags into pages using the Live Editor, the Tagfill Dialog or Aloha Editor, by setting the “View Permission“ flag on Construct Categories for specific Groups.It has to be noted, that although the flag is presented as “Permission Flag” it only modifies the Ui components, but does not prevent users with advanced knowledge of the REST API to add tags of other tagtypes using the REST API. Instead of just a generic image icon, the minibrowser will now show a thumbnailin each image result row in the list pane. Inherited content objects will havewhite-washed thumbnails with a small arrow to indicate multi-channelling. The file fetch feature will now store imported images into the default image folder of the current node. The default behaviour will take place when no default image folder was specified. Corrected the standard error message displayed to users when page loading is halted. Modified the exception handling for starting publishing transactions. Added the disable_version_diff_choice feature, which disables the selection of a version when creating new language translations of a Page and automatically selects the most recent version to be shown in the split view for translation. This feature is disabled by default. Changed the Runtimeprofiler to initialize the timer dynamically, this allows the timer to be deleted. Fixed the default gravatar picture not working anymore due to changes from gravatar.com. Also disabled loading images from gravatar when using https://. Fixed a bug in tagfill which would cause an error when switching text parts of a tagtype to tag (page) parts. Fixed importing of tagtypes that already exist on the target system, but have less parts in the export file. Due to a bug, the superfluous parts where not removed during the import. Fixed reading permissions for users. The database is now forced to use specific indices, because it sometimes decides against them (and doing a full table scan on the perm table instead),which drastically decreases the request performance. Fixed releasing a semaphore when the publish process fails while starting a transaction for publishing into a contentrepository. If the semaphore was not released, the following publish process could hang indefinitely. When a page was requested to be opened in edit mode (using Aloha Editor), but was instead opened in readonly mode,because the user had insufficient privileges to edit the page or the page was locked by another user, the settings for$cms.rendermode still pretended, that the page was opened in edit mode. This caused specific edit mode implementationsto fail in such cases. This has been fixed now, so that the setting for $cms.rendermode will always be correct. Fixes bug in GCN/Aloha Blocks implementation which required the editor to clicktwice into an editable in order to bring up the floating toolbar after closingthe TagFill dialog. Fixes tag copying. Copied tags are no longer lost. The copy placholder willnot inadvertently change markup around the copied block. REST API call /CNPortletapp/rest/page/render is fixed to be able to detect rootelements with uppercase tag names. Therefore, given: fixes #51971 with workaround for when ie7 sometimes results in dom elementshaving corrupted attributes references. The repository browser and minibrowser will now use localized translations for various messges and texts. Copied link tags will no longer be blockified. The File (Upload) part type was fixed. Previously the upload button was not visible and the i18n string was not translated properly. Fixed releasing a semaphore when the publish process fails while starting a transaction for publishing into a contentrepository. If the semaphore was not released, the following publish process could hang indefinitely. Fixed bug that the page was locked twice in the top menu of a page.This also caused the page to not get unlocked when doing this the first time. Fixed a bug that caused image data to be set incorrectly when uploading a new image while editing a page when the target folder of the image was set outside of the current node. solved issue #51486, where closing a TagFill in IE7 for a block which is notrendered inside an editable would result in the user no longer being able tomake any selections on the page. The file fetch feature will now correctly check the needed permissions for the used import folder. Previously create permissions were not checked correctly. REST API call /CNPortletapp/rest/page/render is fixed to be able to detect idsof root elements even if they are not wrapped in quotes (as is the case withIE). Fixed how links are saved to ensure that all link parts are saved as well. Fixed a bug that caused image data to be set incorrectly when uploading a new image while editing a page when the target folder of the image was set outside of the current node. Fixed timeout problems when publishing multiple pages from the queue or the page list which could result in an error message. When inserting a constuct using Aloha Editor the list of constructs to choose from was unsorted. The REST API will now sort the list of constructs by default. Fixed the Repository Browser to correctly show multichannelling icons. Fixed premature evaluation of script tags that occurred in IE when renderingtags for editing that contained script tags. The feature Versioned Publishing, which has been disabled is now enabled by default. Fixed the Repository Browser to not show any objects in the list, when the Root Node (“Content.Node”) is selected. Fixed possible performance problem when editing a tagtype that has many parts and is used by many tags. Fixed the feature logout_page not showing the text “Logout successful” because of a broken translation.Also added the ability to set an actual URL instead of just true to this feature. Fixed SGB error when the tagfill dialog (when a tag in a page is edited) was saved,while the original page Added the feature advanced_parallel, which makes sure that a scheduler task is not started as long as any of its following tasks is stillrunning, even if they are set to run parallel. The feature is turned on by default. Fixed PHP Fatal error: Class ‘CNFolderObject‘ when executing a workflow timer trigger that moves a page. Fixed multithreaded publishing in conjunction with instant publishing into content repositories, which lead to longer publishing times, without using CPU time. Manual Change Change to GCN JS API The function descriptor of the function PageAPI.createTag() in the GCN JS API has changed. It will no longer support calls like Manual Change Aloha Editor 0.20.x was removed from GCN Aloha Editor 0.20.x was removed from Gentics Content.Node. Now only the latest version of Aloha Editor will be included.The features aloha , aloha_010 and aloha_jqueryui are no longer being used and should be removed from the node.conf configuration file. Modified the Gentics Content.Node Javascript API to load also folders, images andfiles for updating them. This will ensure that the API objects will have allpossible object tags set (even if they are not yet filled in the backend). The new feature copytags_ allows Copy & Paste of tags between pages.Please read the documentation of this feature in the Gentics Content.Node Guides (section “Features”). Added option “update“ to REST API calls for loading folders, images or filesto load them for the purpose of updating. Currently, folders, iamges and filesare not locked in the backend, but it is still recommended to set the “update”parameter to true, when the returned object shall be modified. This will ensurethat the object contains all possible object tags, even if they are not yet filled. The REST-API method Fixed behaviour of assistant history to be consistent with multichannelling. Thisalso fixes creation of “hidden” pages if creating new pages directly after switchinginto a folder of another node using the assistant history. A image include within the page property view was fixed. The image manipulation ‘Ok‘ button behaviour was fixed. Previously the button click would not work within Internet Explorer 7 due to missing json extensions of that browser. The folder versions menu entry was removed because the folder versions feature was removed. The removal of the feature itself happend within a previous release of Gentics Content.Node. Some messages for the file uploader will now be displayed in the correct langauge. The flash uploader button will now also work in nativ Internet Explorer 9 mode. Previously the flash uploader was not working due to Internet Explorer 9 security options regarding flash applications. Fixed a bug that caused folders created in a derived node over the Rest API to be added to the wrong node. When creating new files using the REST API, the returned file will now contain all possible object tags. A missing image was added to the imagemanipulation2. Previously the image resize handle image was not loaded. Changed the status message displayed when running a data check of a contentrepository that is not linked with any nodes. Fixed javascript error that occured when leaving the tagtype/node assignment dialog. Previously jquery was loaded twice and that caused a javascript error while initialising the tipsy tooltips in the tagtype list. Adds addDeleteButton() to Aloha Blocks to allow implementors to dynamically adda delete button to a GCN Aloha Block even if the block had originally beendetermined to be un-deletable. Multiple javascript errors within the adminstrativ interface were fixed. Previously the tooltip plugin caused javascript errors within the tagfill dialog when a new tagtype was created. jQuery 1.4.2 was replaced with jQuery 1.6.1 in various places. Live editor page editing will still use jQuery 1.4.2 due to compatibility reasons. Manual Change Manual change for Aloha Editor Gentics Content.Node will use Aloha Editor Blocks to render tag iconsin your page. Aloha Blocks currently only support div and span as validroot tags.If your tagtype implementation uses other root tags than a div or a spanor if you do not have a single root tag at all your html code willwill be wrapped by a div tag to make them editable for the user.You can however configure your own root tags for the Aloha Editor BlockPlugin: http://www.aloha-editor.org/guides/plugin_block.html#changing-the-root-tagsNOTE: Drag/Drop functionality for Aloha Blocks is only supported when using div and span as root tags. If you configure other root tags anduse them along with Drag/Drop functionality you may encounter problems The tooltips within the node properties view were extended. Fixed opening a page in edit mode, that was already locked by another user. The check for locks failed and the page was opened in edit mode. However when trying to save changes,the check for locks succeeded, the user could not save the changes but got a message instead. Fixed setting properties for objects in the GCN JS API to empty string (or 0), which did not work before. Fixed Gentics Content Node Intergration Plugin to not through an error ifwebappPrefix is not provided via an external settings. Fixed a bug which caused tag types to become unlinked from all nodes if users cancelled editing a tag type after deselecting all nodes from it. When switching from preview mode to edit mode for an inherited page (when using multichannelling), the user will now be asked whether to editthe inherited page or to first localize the page in the channel. This is now the same behaviour as if the user had edited the inherited pagefrom within the page list. Fixed display of pages, that have a language set, but are not part of a contentset (have contentset_id = 0 in the database). Before this fix, such pages would hide each other and only one of that pages would be shown. Exports (using the new mechanism) are no longer done in single, long running transactions, as this is not necessary (exports don‘t modify object data) and could possibly lead to DB locks. As a result, before this fix, starting an export build,while another build was still running could cause an SGB. Fixed SGB and generation of corrupted page (having no content) when copying pages that have duplicate tags. Now, when a page with duplicate tags is copied, the first occurrance of each tagname is copied, all duplicates are just ignored. The output of an i18n translation string was corrected within the template creation dialog. Fixed the buttonimage of the gcnfileupload plugin. The image was not visible when the aloha_jqueryui feature was enabled. Fixed canceling the edit process when using aloha_jqueryui feature. The liveeditor will no longer insert Fixed encoding problem in rendering UTF-8 values in custom form parts, if the feature customform_resolve_nodetags was activated. Fixed the listing of pages (using the REST API or in the backend) in folders where a corrupt page exists. Before this fix, an error occurred and the page list was empty, now an error is logged but the call succeeds with the corrupt pages just ignored. Fixed an issue that caused an uncaught exception to be thrown when using a tagpart for selecting a folder upload when the folder was not yet selected. The dababase table mappedglobalidsequence, which is used to generate unique global id‘s for object is changed from engine InnoDB to MyISAM.This will avoid DB locks caused by long running transactions, that insert new objects (like the Import). Added folder information to the object lists in the repository browser so that search results can better be identified. Fixed a bug that caused some settings selected when filling tag values in a page to be applied even after the user pressed the cancel button in the tag fill dialog. When a timeout occures during querying the backend in the repository browser, the user will now see a message. Fixed possible problem when deleting a tagtype that is used in object properties. Fixed problem with the tag.edit() method in the GCN JS API wich would only add the first DOM node of tagtype implementations containing multiple DOM nodes to the desired editing location. Fixes the tag.edit() method to correctly insert content into the target DOM element.Script tags contained in incoming content will be evaluated, and inserted into the DOM as well. The Repository Browser will now hide the search field and search button unless a node or folder is selected (and the search is possible). Fixed an issue which caused page filenames containing invalid characters to be allowed. Fixed triggering workflows when a page was published using the the UI. Fixed the height of the repository browser in the tagfill dialog to better match the height needed to display 10 elements, so that vertical scrolling is not needed. Added ID to the row help (tipsy) of objects listed in the export selection dialog to help identifying them (if the name is ambigous). Fixed dirting of navigation pages, when pages are created in localized copies of folders that are listed in the navigation. Make sure, the cache of a folder is cleared, when creating files or images in it. This fixes the problem, that after a page import, created images or files are not shown in the target folder (although they exist), until the cache of the folder is cleared because of other reasons. Fixed getting a sorted and paged list of folders via the REST API. Before this fix, the sorting was not correct. Fixed the permission check for editing templates in localized folders. The menu entries to edit templates were shown (if the user had edit permission), but when trying to edit the template a SGB occurred. Paging through templates in the repository browser was previously not possiblebecause the REST API method “/getTemplates” did not handle the `maxItems‘ and`skipCount‘ query parameters. With these now implemented, paging works. Fixed paging in the Repository Browser of the Tagfill dialog. Fixed sending messages that contain folder paths of pages in multichannelling: Always show the channel specific folder paths (instead of the folder paths of the master node). Fixed the GCN JS API so that the element that is passed into the edit() methods the container for the rendered tag contents is also appropriated as the rootelement of the rendered tag. Beforehand, an new root element would be generated during the render call towrap the contents of the tag, and this would result in unwanted nestedcontainers wrapping the contents of the tag.*ie*: Given: Fixes the GCN mini browser to correctly fetch tags when clicking on asearch result in the browser list pane.The fix involves resetting the search parameters before proceeding toquery the GCN repository for resources so that tags are not filteragainst the last search criteria.Fixed getting a sorted and paged list of folders via the REST API. Before this fix, the sorting was not correct. Fixed a JavaScript error that occurred when closing tag field dialog after a tag was inserted into another tag. Fixed a bug in the handling of escape characters in i18n strings. An SGB that occured when opening the usage view for images was fixed. A bug that occured when handling the ALOHA_PLUGINS_NODE setting was fixed. Previously some alohaeditor jqueryui specific plugins were not added to the final list of plugins. This issue only affected systems where the aloha_jqueryui feature was enabled. Missing i18n entries were added. Added support to the GCN JS API for dealing with property names that have dots in them. Suchsupport is especially needed in order to deal with object property tags whichhave names like “object.myprop”. The GCN JS API api methods have been made more error resilient. It waspreviously the case the exceptions that occurred during the invocation ofcallback functions that were passed to the GCN JS API by the user of thelibrary would prevent the library from completing any further calls that it hasin is call queue; content objects would be left in unusable state from thereon. The enhancement provides and internal means to allow the library to catchexceptions that occur in user-given callbacks so that the library is able tocontinue processing its queued invocations. The REST-API has been extended to support creation of local pages and folders by adding the property nodeId to the create request objects.Additionally, the new REST-API calls /CNPortletapp/rest/page/localize/{id}, /CNPortletapp/rest/file/localize/{id}, /CNPortletapp/rest/image/localize/{id} and /CNPortletapp/rest/folder/localize/{id} allow localization of pages, files, images and folders. The context path of Gentics Content.Node can now be configured.Please take a look at the context feature within the guides. A group mapping was added to the HTTP_AUTH_LOGIN feature. The i18n translation implementation within the Gentics Content.Node interface was changed. Fixes a bug in the GCN Intergration Plugin where after closing the tagfilldialogue, the tag date of the edited tag would no longer be consistent. Fixed detection of image dimensions for .ico files, when they are uploadedusing the REST API or imported. When .ico files were imported, the importfailed with an “Internal Error”. Fixed clicking tag edit icons activates the image plugin Fixes the Rest API to respond with object data that has object tagsmapped in the correct way. They keys will now be ‘object.[name]‘ instead of just ‘[name]‘. Fixed issue in gcn-repository.js, console.warn() made RepositoryManager unfunctional in IE Fixed a problem where jQuery would not be properly declared when working withthe GCN JS API in NodeJS environment. Fixed Aloha-Editor block/tag initialization.Sometimes, after returning from a Tagfill-Dialog, duplicate tagiconswere either displayed doubled, or were missing. Fixed an issue when attempting to edit and view tagtypes fill without the necessary permissions. Fixed possible NPE in new Import, when importing tags based on tagtypes that have a part with keyword “name”. Fixed resolving issue when rendering tags of “foreign” objects in velocity tags. E.g. when rendering the object tag of a folder in a page‘s velocity tag, where the folder is different from the page‘s folder, the object tag will now be able to resolve its containers name via Fixed an issue when using tagtype names containing curly braces. Fixed a bug that allowed inadmissible characters in forms if the corresponding error message was not available in the current language. A bug that occurred during the building of 5.6.2 was fixed. Manual Change Disabled Aloha Editor block-plugin drag and drop feature The block-plugin drag and drop feature is now disabled by default. Thefeature may be re-enabled with the following setting in the node.confconfiguration file: $ALOHA_SETTINGS[‘plugins‘][‘block‘][‘dragdrop‘] = ‘true‘;Changing this setting requires a tomcat restart.Please note that the block drag and drop functionality is experimentaland still in development. Manual Change Tagtypes implementation and Aloha Editor block-plugin In order for tagtype implementations to be compatible with the block-pluginof Aloha-Editor (not loaded by default), they must either have a div or spanroot element.If a tagtype implementation does not have a div or span root element, itwill be automatically wrapped with a div, and an error will be logged inthe browser console.Due to the automatic wrapping, tagtypes may still work, even if they donot have a div or span root element, however, it is still an error, andtagtype implementations must be updated accordingly. Fixed evaluation of $tag.empty for tags in a velocity tag, which always returned 1 (pretending that the tag was empty). Fixed clicking on a folder in the tree frame after saving the page,which would open in a new window instead of inside the correct frame.This error was only caused it the Aloha Editor undo-plugin was active. Fixed problems when translating pages that have localized copies using the REST API. Before this fix, not all of the language variants were shown in the page list. Fixed appearance of unwanted empty paragraphs with the class “aloha-editing-p”, when using drag & drop to drag tags at the very beginning or end of an editable. This issue only affected systems with the aloha_jqueryui feature enabled. A caching issue within the Gentics Content.Node Aloha Integeration Plugin was fixed. Previously newly inserted tags could not be found when a tag was edited using the tagfill dialog. A error was shown when the aloha block was beeing reloaded. This issue that only affected system with the aloha_jqueryui feature enabled is now resolved. Fixed issue with opening the tagfill dialog in nested form elements. Previously the edit and delete icons for tags within form elements could not be used due to a issue with the click event handling. This issue only affected systems with the aloha_jqueryui feature enabled. Removed the delete icon for tags, that should not be deleted, because they are included in the template. This issue only affected systems with the aloha_jqueryui feature enabled. Added more detailed label descriptions to the form for creating overview Tag Types. Fixed sorting pages by last edit time, which did not work anymore. Fixed rendering a part from another tag in a velocity tag. The part will now be rendered in the scope of its container tag, so that resolving other parts via the Fixed saving pages after a tag was modified using the tagfill dialog. Before this fix, a page could not be properly saved after the tagfill dialog was used. When publishing the page, the user was notified about unsaved changes (even though the page should have been saved before). This issue only affected systems with the aloha_jqueryui feature enabled. When the same live editable tag (which is a tag, that only contains a single part, which is live editable) is inserted more than once into the page‘s template, only the first occurrance of the tag will be made editable. Before this fix, some occurrances were also turned into blocks, which lead to unexpected behaviour. This fix only affects systems with the aloha_jqueryui feature enabled. Fixed possible Internal Error due to a DB lock wait timeout when importing Templates with the new Import Mechanism. Fixed vanishing object properties of master object when localizing pages. Fixes bug in GCN Integration Plugin allowed contain-in rules to be broken wheninserting GCN Tag blocks into editables. A bug in the image file upload was fixed. Previously the uploader did not use the custom filename. Additionally some special characters within the filename resulted in a SGB error. Fixed concurrent creation of multiple tags. For example, creating two links and saving would break at least one of the links. Fixed an issue when leaving a page using the Aloha Editor. Previously, informing the user about unsaved changes did not display correctly in Chrome and Safari. Corrected syntax error in generated response XML file for the Scheduler Control API. Omit saving the currently edited page twice, when it is published from within the edit mode. This issue only affected systems with the aloha_jqueryui feature enabled. Manual Change (when updating to Aloha Editor with jQuery UI) The GCN Intergration Plugin now supports the use of page object handlers as thelegacy version of this plugin did. The API has remained the same except forone significant change: Registered page object handler callbacks will receive aGCN.PageAPI page object rather than a plain-old-object.It might also be helpful to note that the page object you receive in thehandler function allows you to inspect exactly what data of the page objectwill be sent to the server in the save process (since for efficiency, onlychanges are send to the server during saving, and not the entire page data asin the legacy plugin). This introspection can be done using page.json().Beware however that the returned object is only useful for introspection andnot reflection. IE: Changing properties of the object returned by page.json()will not mutate the page object itself, this must done via the page object‘sAPI. Manual Change Possible Root elements of tagtypes changed. The tags ‘p‘ and ‘h1‘ – ‘h6‘ are now recognized as valid root elements of tagtypes.When using tagtypes with such root elements before, the tags where wrapped into a ‘div‘ tag, which no longer will happen after this change. Fixed dom-to-xhtml serialization.This fix applies to any serialization function set withAloha.Editable.setContentSerializer(). Fixed a bug in the GCN JS API in which block tags which only contained aneditable would not be properly converted into Clicking publish from the page preview would result in an JavaScript error. Fixed. A javascript error was fixed that occured when editing a page that contained template tags that contained references to page tags. This fix only applies when the feature aloha_jqueryui was enabled. A javascript error was fixed that occured when clicking on the taglist menuentry while editing a page in aloha. This fix only applies when the feature aloha_jqueryui was enabled. Fixed inserting tags when using Aloha Editor: The tags will now be inserted at the correct position in the DOM (if possible), respecting the html5 specification. Fixed the Cannot determine construct messages. Previously a bug caused the activation of this alert message box. This fix only applies when the feature aloha_jqueryui was enabled. The aloha-block classes will now be removed by the Gentics Content.Node Aloha Integeration Plugin. Previously the classes were saved. Fixed possible Internal Error due to a database lock when importing page variants that all link to other objects (in content tags or in object properties). The vertical scrollbar within the page editing view will now be shown. Previously the scrollbar was hidden when using Mozilla Firefox. This error was only caused it the Aloha Editor undo-plugin was active.Fixes GenticsContentPortlet in frontend editing szenarioThe backend path can differ between backend andfrontend mode. There was no way to configure thisin the implementation, since the gcn library isloaded dynamically by the gcn-plugin, and thegcn-plugin loads the page when it is initialized. Fixed a bug in the GCN Integration Plugin that resulted in editables that wereinside block elements from being Alohafied when a page is loaded for editing. A bug in the Gentics Content.Node JavaScript API was fixed. Previously saving an external link resulted in a javascript error although the link was saved successfully. The additional aloha-block classes will no longer be generated by Content.Node. Previously block elements that saved the classes in a tagpart would receive additional block classes for each editing process. Fixed opening a page in preview mode locks page and saving a page doesn‘t unlock it. The gcn linkbrowser button was not visible by default when the aloha_jqueryui feature was enabled. Manual Change Aloha‘s ecma5.js was removed. The ecma5.js added the following functions to the environment if they didn‘t exist already.* Function.prototype.bind* String.prototype.trim* Array.prototype.indexOf* Array.prototype.lastIndexOf* Array.prototype.forEach* Array.prototype.map* Array.prototype.filter* Array.prototype.every* Array.prototype.some* window.compareDocumentPosition* window.getComputedStyleAlso, the window.Node object was added to the environment containingDOM-Node type properties.Please make sure that custom javascript implementations don‘t rely onany of these properties being defined.Some of them are still provided by some browsers, but not by others.For example, String.prototype.trim and Array.prototype.indexOf will workon Chrome but not on older versions of IE.String.prototype.trim and Array.prototype.indexOf methods are the mostoften used functions, and, if custom implementations rely on some ofthese methods to be defined, it is most likely one those two. Manual Change Aloha Editor 0.9.3 was removed The legacy version of aloha editor was removed. Manual Change Additional default plugins for new aloha editor version were added. The following plugins were added to the default plugin list for the jqueryui version of aloha.* common/ui* common/block* extra/ribbonNOTE: This only applies when the feature aloha_jqueryui was enabled. Manual Change The policy-map schema used for the validation feature has been changed. If you have configured a custom policy map by following these instructions please verify that your policy-map.custom.xml is still valid according to the schema .The custom policy map will automatically be validated during the restart of the tomcat while performing a GCN update. If the schema fails to validate, the update will likewise fail. If the update fails due to schema validation errors, it is sufficient to fix the validation erros and restart the tomcat afterwards.To validate the policy-map.custom.xml manually, you can download the current schema and perform the validation using a XML Schema validation tool. For example, using xmllint The aloha_jqueryui feature was added. You can enable the jqueryui version of aloha by enabling this feature. Please note that the plugin API was modified thus manual changes to existing plugins are required. Please refer to the aloha editor changelog for additional information.NOTE: The older version of aloha editor (0.20.x) will be discontinued as for 30.09.2012 The upcoming October release will replace the 0.20.x version of aloha editor with the 0.21.x version. The Black Panther login screen has been tweaked to fit better with resolutions of 1024×768 and below. Some additional features were added to the file_fetch feature. The feature is now called image import. See image import feature Validation is now turned off when filling in tag-type defaultsIt was too awkward for implementers to work with automatic sanitation ofinputs when creating and filling in the default values of tag-types inthe Content.Admin area.Since only implementers have access to the Content.Admin area, andimplementers are inherently trusted to only input valid content into thesystem, validation is now disabled when filling in tag-type defaults. Discontinued old folder versions dialog. The flashuploader was updated to a newer version. The uploader will now also keep the displayed upload queue. The upload button will now display without time delay when loading the page. Clicking publish from the page preview would result in an JavaScript error. This error was now fixed. Fixed missing translated names while exporting constructs (or other objects that have translatable names). Export files with missing translated names caused an Internal Error while importing.The translated names were missing in very special situations: if e.g. a construct part was exported and the reference id of the translatable names happened to be exactly the same id of another construct part that was exported before, the translatable names were not exported. Potential Issue: A memory leak in the jQuery 1.7 feature detection that affects Internet Explorer 8 was detected. The CRSync will now log the number of removed obsolete objects per type. Fixed listing of pages, that use another page (either by being a page variant, or by containing a pagetag to the other page): Correctly show language icons, template and folder information. Fixed a bug in the experimental version of the gcn integration plugin. Previously a javascript error occured when no tagtype with no assigned category existed. While a page is imported using the page import, the page will be locked now. Additionally, the md5sum of the imported page source will be written when the page was successfully imported (not earlier).This will help in cases, where importing the page does not succeed (e.g. due to a timeout), because the page will be imported again, when tried again with the same source. The aloha editor basic contenthandler was activated by default. The contenthandler sanitizes the html that is fetched though the Aloha Editor getContents method. For more information please refer to the Aloha Editor Changelog. Fixed permission checks when trying to create a folder in the root folder of a channel that is derived directly from a master, the user is not allowed to see. Fixed incorrect disabling of the button for pushing objects into the master in the channel synchronization dialog, when switching to another tab. Added styles to pre tag around source code diff between page versions, to have line breaks. Modified the tooltip position of the source code textarea for templates, so that the tooltip is now visible. Fixed a bug in the experimental version of the Gentics Content.Node Javascript API that caused on construct category to be left out the sortorder array. Some CSS definitions that might interfere with project specific styles have been prefixed with “gentics_” or removed. It is now possible to configure Aloha Editor settings in the node.conf, that contain array with keys containing , (comma) and spaces. A misplaced call to javascript alert was removed. Previously this alert was displayed when previewing a page in the liveeditor. Fixed unnecessarily high memory consumption (possibly leading to OutOfMemory Exceptions) when rendering a page containing (many) editables for Aloha Editor. The links to load Aloha Editor files for editing pages will now contain the current build timestamp (and not the path /latest/ any more). This avoids unnecessary redirects (additional browser requests), if the correct paths to Aloha Editor files are known anyway.The path containing /latest/ will still work (and redirect to the path containing the current build timestamp) for applications that need to load Aloha Editor files without knowledge of the current build timestamp. Fixed the “Download URL“ and “Password“ fields in the “New Import” dialog losing focus when being clicked into using Firefox. When pages in the publish queue are assigned to users (i.e. the publish request is denied), the pages are no longer marked as last being edited by the assigning user.This behaviour possibly also caused creation of new page versions (with the assigning user), although the assigning user never edited the page. The scrollbars within the edit view of a page were fixed. Previously the vertical scrollbar was displayed with an offset. In rare cases even two scrollbars were displayed next to eachother. Fixed a bug that prevented automatic republishing of overview pages, when the objects were taken from the current or from selected folders and multichannelling was used. This fix will automatically re-publish all currently published overview pages that might be affected by this bug. Therefore, the first publish run after the update might take longer than expected. Fixed encoding and translation of error message in Scheduler, when trying to delete a Task Event, that cannot be deleted because another Task Event depends on it. When a template cannot be deleted, because it is still used by some pages, the user will now be informed with a message. Fixed deleting of folders during a differential page import: If deleting a folder takes long (because it contains a lot of subobjects), the deletion is not sent to the background, which caused strange behaviour in the page import (e.g. that the folders could not be deleted). If AJAX requests fail during editing with Aloha Editor, because the CMS backend is no longer accessible (due to network problems, session timeouts, etc. ...), the shown error message will now be displayed properly. A Javascript error within the scheduler task creation dialog was fixed. The gcnfileupload aloha plugin design was modified so that it matches the Gentics Content.Node UI. The plugin css can be customized in frontend applications to change the ui style. Fixed exclusion mechanism for objects while exporting with the new export: If e.g. constructs were generally excluded, but a single construct was included, the construct was incorrectly excluded from the export, if it was found as dependency in a template tag (meaning: if a template was exported that contained a tag based on the construct). Fixed javascript errors occuring when using regex characters in the repository browser search field. Some typos within a javascript warnings have been fixed. Added error message to import log of differential pageimport, when objects cannot be removed (e.g. due to insufficient permissions). Fixed some style issues with the repository browser. Previously the tree icons were not correctly displayed within Internet Explorer 7 and 8. The searchfield size was slightly increased. Added new feature “liveeditorsavelog” for detection of possible data loss when saving page contents with the live editor. If turned on, and the new saved tag value is less than the old one (by a configurable percentage – $LIVEEDITORSAVELOG_PERC, default is 10%),the contents in the different stages of transformation is logged in the DB. By default, this feature is off.Configuration example: The group permission view was fixed. Previously permission settings were also displayed for localized folders. Those folders will now be handled like inherited folders within a channel. No permission information will be displayed for those folders. When using Aloha Editor, handling of empty block elements (like paragraphs) has been fixed now. All block elements will contain a single The quickjump will now also update the tree menu for pages in nodes that use the liveeditor for editing. The Rest API construct/list method will now be used by the Gentics Content.Node JavaScript API. Previously the construct/load method was used. The json format for the success handler of getConstructs and getConstructCategories was changed. The Gentics Content.Node Guides are now available. Fixed clearing caches, when the name of a node was changed. This fixes display of the breadcrumb after changing the node name. When pages from the publish queue were published, the inbox messages were always sent in english. This has been fixed now, the inbox messages will now be sent in the correct language. A NullPointerException within the RestAPI is now handled. Previously a NPE occured when trying to save a page using a request object that contained tags without specifying the name attribute of the tag. We now throw an exception in those cases. Fixed exporting and importing assignment between Object Tag Definitions and Nodes.Export bundles, that were created on systems using the new Export mechanism before this bugfix might be incompatible with Systems still using the old Import mechanism:Importing might fail with an “Internal Error”. In such cases, the Export bundle should be recreated with this fix applied. Fixed restricting overviews with the configured maximum, when using multichannelling. Hide master nodes from the channel synchronization dialog, if the user has no permission to see it. Manual Change Handling of enabled aloha plugin setting was changed. Previously loading of some plugins was omitted when the generated php array of the node.conf CUSTOM_ALOHA_PLUGINS array already contained entries that were included in the ALOHA_PLUGINS_GLOBAL. It is now no longer needed to touch the ALOHA_PLUGINS_GLOBAL variable. The array_unique and array_merge invocation can now be omitted. The CUSTOM_ALOHA_PLUGINS array will now automatically be merged with the ALOHA_PLUGINS_GLOBAL array. See this guides page for more information. The new feature “aloha_annotate_editables” enables annotation of DOM elements, that are root tags of editables in Aloha. They will get the following classes: GENTICS_construct_[constructkeyword] GENTICS_tagname_[tagname] GENTICS_tagpart_[partkeyword] GENTICS_parttype_[parttype]. The selfupdate logout link will now open in the correct frame. The page delete action will now no longer take multiple minutes for completion on large systems. Previously a check for page variations caused the deletion action to stall while the check was in progress. The check is now optimized. Searches in the MiniBrowser will now be done recursively. The details lists for pages, images, files, templates and folders in the channelsync dialog now shows more information. The construct load method will now return an ordered set of construct categories and constructs. Previously those entries were not ordered. Constructs (Tagtypes) will be ordered alphabetically and construct categories will be ordered by the specified sortorder. Additionally this method will now only return constructs that can be inserted into other tags. Please use the list method if you want to list all tagtypes/constructs. Please note that the functionality of the load method will be moved into the list method at some time in the future. Fixed layout for page timemanagement in Internet Explorer where weekdays would not always have the checkboxes right next to them. The timeout for queries in the repository browser of the tagfill dialog has been raised to 60 seconds. Fixed file opening behaviour for non-image filetypes. Previously videos and other non-image filetypes were automatically opened in external programs. Those files could not be loaded in external programms since the session cookie is not beeing shared between the browser and the external programs. Non-image files will now be downloaded by the browser. They can be used by external programs once the download is completed. Fixed SGB that sometimes occurred when trying to push local objects into a master node. Fixed instant publishing in connection with multichannelling. When instant publishing was activated for the ContentRepository of a master node and an object was published in a channel, the object was instantly published into the master node‘s ContentRepository.Additionally, there are two new maintenance actions in the list of ContentRepositories to check CR‘s for incorrectly published data and to remove this data. Assistant frame will now be properly shown after being hidden by the tagfill dialog. The tree will now be updated correctly when switching pages using quickjump. Split translation view will now have appropriate window size in Internet Explorer Fixed resolving problem when rendering nested velocity tags in a special way: When e.g. resolving $cms.folder.startpage.url.tags.[tagname] in a Velocity Tag of a page, where the folder startpageresolves to another page, the resolved tag [tagname] was rendered in the scope of the first page, not of the page really containing the tag. As a result, resolving of $cms.page in the tag [tagname]returned the outer page, not the page containing the tag [tagname], like expected. Fixed uploading files via the gcnfileupload Plugin in Aloha Editor, via the PHP uploader or via WebDAV in local channel folders. The uploaded files will now always belong to the correct channel. Added new configuration setting $MAILRETURNPATH, that should be set to a valid eMail address, so that mails sent from Java processes are not blocked by the receiving mail server. Fixed display of pages that have language variants in nodes that have no languages, when multichannelling is used. Instead of showing all language variants as separate pages, only one language variant is shown (like when no multichannelling is used). Fixed the datasource usage overview listing sometimes not showing results when a filter was set in the main datasource list.It now doesn‘t use that filter anymore and shows all results in the usage list. When using the Channel Synchronization to push objects into a master node, check for objects that are contained in folders that do not exist in the master (local folders in the channel). Those objects are no longer pushedto the master, but the user is informed about the inability to push them. Fixed Inbox Messages for pages sent to the publish queue, where the page link was missing for pages with IDs greater than 999. Fixed redirecting requests to /CNPortletapp/latest/alohaeditor… to URLs containing the timestamp of the latest Aloha Editor Build to support probably existing proxyprefix, that is used when accessing Aloha Editor via a ProxyServlet for use in frontend editing.Since frontend editing only works, if the new Feature “redirect_check_referer” is turned on, this feature is now activated by default. This update will start a background job (when the tomcat is started), that fixes the page versions (where possible) to be compatible with versioned publishing.It may, however, occur that pages that have not been modified for a very long time do not provide enough data to fix the page version accordingly. For those pages, re-publishing willstill behave like before the feature “versioned publishing” until they are manually republished once. Fixed clearing caches, when a page‘s content is locked/unlocked (when editing a page without using Aloha Editor). Before this fix, it sometimes occurred, that after saving (and unlocking) a page, it was incorrectly still shown as being locked in the pages list. Fixed incorrect assignment of folders to channels, when pushing localized/local folders from a channel to a higher channel (which is not the master node). As a result, it was e.g. impossible to set a startpage of such folders.This fix includes repairing of the incorrect data in the database. When multiple pages are published in a single action, they will not be written into the contentrepositories, even if instant publishing is activated. This will avoid possible browser timeouts, when writing many pagesinto their contentrepositories takes a long time. Only if a single page is published, instant publishing will be done (if activated). Fixed the failure handling when editing Pages with Aloha Editor. If an AJAX Request get‘s an error, the default error handling will show a message to the user now. Removed debug output line left in the file uploader by mistake. Fixed the table plugin in live editor not taking the resized width & height of tables into account when editing a table again. Fixed rendering of page URLs when rendering pages in edit or preview mode. Links to CSS or JS pages will always be for the live preview. Otherwise, when rendering in real preview or real edit mode, the links will go to real preview. When rendering preview or edit mode (with or without Aloha Editor), the links will go to preview mode.This fixes problems with the main menu, when following a link to another page (main menu was not working any more). Fixed clearing caches when deleting tagtypes that were used in pages, templates or object properties. When a page is modified and then placed into the publish queue Manual Change When using Aloha Editor the AlohaRenderer will now also accept span-tags as valid root-tags Prior to this change span-tags where not considered to be valid root tags thus the tags contents where automatically wrapped in a div. If you rely on this functionality this might now result in multiple tags being listed on the same line and lead to overlapping tag icons. Add wrapping div-tag to your tag implementationsto solve this issue. Changed the single file uploader (and the file properties) to not print an error anymore when the filename length exceeds the limit of 64 characters.The filename will be cut automatically now. Also over-worked the character handling to be consistent with the character handling of the Rest-API file uploader (see the GCN 5.4.19 changelog). The tag insert buttons within the gcn plugin can now be configured per editable. A whitelist configuration is used to show/hide specific tag insert options. The whitelist uses the tagtype keyword to filter the buttons/menu. Set the feature force_javaparser_post to true in node.conf.This features forces PHP-requests to the javaparser to be sent as POST because there can beproblems (for example really long custom form tagtype part templates not being rendered) when this is not enabled. Added functional description for the Gentics Content.Node Integration Plugin. The Media Library Integration ($FEATURE[‘file_fetch‘]) has been enhanced: By setting $FILE_FETCH_EVAL = true; it is now possible to add dynamic part specific data to the FILE_FETCH_URL, like e.g. $FILE_FETCH_URL=“http://mediaserver/medialibrary.php?postback=“.urlencode($FILE_FETCH_POSTBACK_URL).“&keyword={\$part[‘keyword‘]}”; Enhanced the conflict message in the import when an object was excluded in the export and could not be foundon the target system. It now includes the globalid of the object. Fixed exporting of channels with local templates that are only assigned to inherited folders. Such export bundles could not be imported, because there was always a conflict “Object does not have a target folder”. Fixed language icon being broken when translating a page and Gentics Content.Node doesn‘t use the default .Node/ URL prefix. Fixed a possible database deadlock, when pages were published (or put into the publish queue), while a publish process was running at the same time. Fixed menu in the channel synchronization (Details) being wrapped at the folder menu item. Re-added the user and date, when a page was locked to the list of pages, when multichannlling is used. Fixed SGB when trying to create new nodes after having selected a (non-root) folder of another node. Fixed exporting of constructs in channels: The constructs were incorrectly assigned to the channels, not the master nodes. This caused permission checking problems, after the construct was imported into another system. This fix also corrects the incorrectly set assignements. Fixed rendering of page versions that contain tags that have been deleted after the version was created.Rendering of page versions with deleted tags resulted in an empty pageto be displayed and an exception similar to the following to be thrown:com.gentics.api.lib.exception.InconsistentDataException: Data inconsistent: Container {xxx} of Value {xxx, xxx} does not exist! Fixed importing of localized language variants, which were incorrectly always detected as conflict (conflicting with their master). Fixed bug in the Gentics Content.Node nodectl start/stop script to not stop the mysql server when ENABLE_MYSQL is set to 0. Fixed a but in Multichannelling, that caused data inconsistencies for folders, when they were created in localized folders and pushed into master folders.As a result of this data inconsistency, affected folders were no longer shown in the tree. This bugfix also repairs the data inconsistencies and will make the folders reappear. Fixed Media Library Integration in the Tagfill dialog, when more than one Image URL Part exists. Fixed invalid channel_id for objects (pages/templates/files) that were copied in a master node, that caused some objects to not show in the export selection dialog. Fixed display of pages, images and files that exist locally in channels and are exported. Fixed the style of the special characters menu in the live editor menu not showing the special characters. After channel synchronization is done, the tree is reloaded to reflect possible changes in the folder structure. Fixed moving of pages,images and files into localized/local folders in channels. Fixed cancelling a running export: During a long running calculation of dependencies, cancelling the export process did not work reliably. This has been fixed now, so that cancelling a long running export is possible at any time without much delay. Fixed duplicate globalid entries in the database that came with the release-package and can cause conflicts when importing exports.This bugfix removes the duplicate globalid entries Fixed many of the administration pages in the Portal.Node module throwing a SGB-error (pages including form elements). Fixed some of the page menu functions (like editing) not referencing to the right page when the page was opened via the history. The scheduler autoupdate task will now fail when a manual change was detected. Fixed the RestAPI Resource /rest/folder/getTemplates/ not having default values for the values sortby and sortorder.The default value for sortby is now “name“ and for sortorder it‘s “asc”.This also fixes the template ordering when creating a new page in Content.Node (alphabetical). The workflow event “on page publish“ and the event reaction “cn_page_proof“have been discontinued.Existing workflows will be unaffected by this change. However, it is notpossible to create new “on page publish“ events or “cn_page_proof”reactions. Fixed a javascript error that occured in some portal implementations within the frontend editing mode due to existing frameset layouts. Fixed problems when uploading files using the File Upload Plugin in Aloha Editor with Internet Explorer (any version) and a certain security level. Internet Explorer sometimes sends the full local path as filename when posting file uploads. Additionally, the path is not sent standard conformant, so that the receiving component is unable to determine the filename and will respond with an error. Fixed display of pages when creating a new page variant, if multichannelling is used: The icons for the language variants of the pages did not have the language icons, which were now added. Fixed uploading images or files via WebDAV: If another image/file with the same name already exists in another folder with the same publish directory, an SGB occurred and the upload failed. This has been fixed now. In cases of naming conflicts, the new images/files will be renamed by appending numbers (before the extension). Fixed permission check for WebDAV: The command “Open” (for opening a folder in WebDAV) will only be shown for folders, where the user has permission to view, create, update and delete pages/files/images. This also fixes SGBs when users with insufficient permissions could open the folder in WebDAV. The changelog which will be displayed in the autoupdate dialog will now again show all changelog entries. Fixed exporting of the “inline editable“ flag of construct parts, which always was exported as “false”. Fixed creation of unnecessary big statements during processing of dependencies that could possibly generate high load on the db server. Fixed the permission check on constructs while doing an import, which incorrectly denied permission on constructs. The performance of getting the list of constructs has been improved if a large number of constructs exist in the system. Fixed follow on success checkbox didn‘t show up as checked.A follow-up scheduler task can be set to only run if the preceding taskwas a success. The checkbox for this setting is called “Follow onsuccess”. Submitting the properties form for a scheduler task with thecheckbox set (or unset) did update the internal setting, but when theproperties form was opened again, the checkbox wasn‘t checked. It wastherefore not possible to determine whether the setting was enabled ornot. When localizing object takes too long and is continued in the background, the user is now notified with an alert box. Fixed importing of construct part names, which were missing. Fixed message dialog overlay in the tree navigation (instant messaging, system messages) always being ontop of the frame instead on top of the current scrolling position. Fixed importing of local channel pages that use an inherited template that is not present on the target system. This will be detected as conflict now. This feature is considered stable even though the full testcycle has been omitted to be able to add it to release 5.5.2. Changed the flash & Aloha Editor file uploaders (Rest-API) to automatically replace not allowed characters with _.The following characters are allowed in a filename and will not be replaced: a-z A-Z 0–9 ,.-()[]{}$The umlauts ä ö ü Ä Ö Ü ß are replaced with ae oe ue Ae Oe Ue ss.Filenames are now also cut automatically (silent) to not exceed the limit of 64 characters. Fixed setting of the folder startpage in folders that have been localized in channels. Fixed quickjump. Previously pages that were opened using the quickjump did not update the internal folder id reference. This caused multiple issues. The page settings did not contain the correct list of templates within the templates dropdown. Fixed the handling of filenames within the gcn-fileupload plugin. Previously the filename was not determined correctly. A small padding was added to the bottom area of the main tree. Some browsers show a info bar within that area. The link browser window will now open centered. The lightbox color of the link browser was also changed to a more consistant white. Fixed exporting datasource with the new export mechanism, so that the export bundle can be imported on systems using the old import without errors. Fixed publishing of page variants, when versioned publishing is used. Before this fix, it was possible that published page variants still rendered the old content, although another page variant was modified and published. Fixed differential page import to remove folders that are no longer present in the filesystem. Fixed handling of requests to the REST API with an invalid nodeId: If 0 is given, this is handled like if no nodeId was given. If an invalid nodeId is given, the client will get an error response. Fixed quickjump. Previously the assistant area between the free and the page was not shown. Now the assistant frame will be opened once a page is loaded. The folder rest method create will now no longer throw a null pointer exception when no folderId parameter was specified. Fixed exceptions like “com.gentics.api.lib.exception.NodeException: languageid not set” while publishing. Those exception had no functional consequences other than filling the publish logs. Fixed a bug with the Repository Browser which would not allow to fill URL Parttypes of object properties. A bug within the object list was fixed. Previously the language of the last visited folder was displayed within the assistant when opening a folder in a node with no assigned languages. Fixed possible rendering error when rendering a templatetag, that links to an overview over pages if multichannelling is used. Fixed possible NullPointerException while publishing when using versioned publishing and multichannelling in combination. Some javascript guards were added to prevent javascript errors that could occure when a cached javascript file was not directly updated after the system update. Fixed error while exporting a contentrepository with a tagmap entry of type 4 (which is deprecated), when the new export mechanism was used. Fixed applying of folder object properties to subfolders, which did not work. Manual Change Enable the hardlink feature The ‘hardlink_files‘ feature only works on 64-bit systems when the correct libgtx_fileutils library is enabled. We have noticed that some systems have this feature activated but the wrong library is enabled. Please check your ‘libgtx_fileutils‘ file within ‘/Node/lib‘. Enabling the 64-bit library will increase the publishing performance and reduce load on most systems. Please note that enabling hardlinks may result in changed permissions of files that are being created within the /Node/node/content/publish/pub directory. An FAQ that describes how to enable the fileutils can be found here: 64 Bit FAQ Manual Change Adapt multilevel publish workflow implementations It is now possible to import and export Channel specific data. The gcn context menu css was slightly modified. Previously the first context menu entry did not have a border at the top. The page name and page language (if existing) will now be displayed within the assistant when viewing a page. The tagfill lightbox size was extended. It will now be wider and higher. Previously the lightbox had a larger border space which made it hard to read the lightbox tagfill content due to the implied size limitation. The restapi can now be used to retrieve objects by using either the localid or the globalid.This affects the loading of pages, folders, file, images and templates Modified handling of REST API requests without sid or with invalid sid. The response to such requests will now have http status 200 (OK), but will contain a responseInfo with responseCode AUTHREQUIRED. The folder name and content language will now be displayed within the assistant when viewing a folder page list. The gcn fileupload will now correctly encode the ‘filter-contenttype‘ parameter. Previously this parameter was not encoded. Without encoding fileupload would not work when using the plugin through a Portal.Node bea weblogic application server. The assistant will now be hidden once the tagfill lightbox opens. The assistant will restored once the tagfill lightbox closes. The tooltip show timeout was increased. The tooltips will now display when 900ms of time have passed. The file, folder, image, page and template filelist search will now also update the displayed count in the assistant. Please note that the search is only affecting the current list type. This means searching within the page list will not update the count for images in the assistant. The gravatar images can now be switched off by enabling the feature ‘no_gravatar‘ The item lists styles were slightly adjusted to allow the tooltip to be read when examing the last item within the itemlist. Previously the tooltip could not be read because it was shown outside of the visible area. The way the changelog is structured was changed. We‘ll now only include the latest changelog in the update view all other changelog entries can be viewed here Besides the already existing quicksearch for folders, it is now also possible to use the extended folder search, that can be found in the main menu (Search|Folders). The restapi fileupload parameters for methods /rest/file/createSimple and /rest/file/create were unified. The folderID parameter is now called folderId, nodeID is now called nodeId. Additionally you may now specifify a ‘databodypart‘ parameter to tell the upload backend logic in which bodypart contains the upload data. The upload backend logic now also supports the blueimp jquery file uploader. The menu transparency was decreased. Previously the background content was visible through the menu entries. Fixed rendering of navigation or breadcrumb in an editable page: like rendering velocity parts, navigation and breadcrumb parts are rendered in a “non-editable” state. When localizing object takes too long and is continued in the background, the user is now notified with an alert box. Fixed javascript error that occured within the new page dialog field. A resizing issue with the tree was fixed. Previously the tree collapsed when editing some pages. This bug only occrred when the aloha010 feature was disabled. A special Internet Explorer behaviour was workarounded in the multipart fileupload fallback. Previously the Internet Explorer 7 was posting the full path to the uploaded file instead of just the filename. The full path that contained special characters triggered the character filter on filenames and the upload was aborted. Fixed a but in Multichannelling, that caused data inconsistencies for folders, when they were created in localized folders and pushed into master folders.As a result of this data inconsistency, affected folders were no longer shown in the tree. This bugfix also repairs the data inconsistencies and will make the folders reappear. Fixed duplicate globalid entries in the database that came with the release-package and can cause conflicts when importing exports.This bugfix removes the duplicate globalid entries Fixed creation of page variants when multichannelling is used. It is now possible to select pages from channels or inherited folders in channels. Fixed resolving of other parts in the get() method of an ExtensiblePartType Implementation when this is done in velocity (like $cms.page.tags.[tagname].parts.[partname].[property]). Fixed creation of unnecessary big statements during processing of dependencies that could possibly generate high load on the db server. Fixed permission check for editing images within file list and tagfill dialog. The image manipulation button will only be displayed when the user has edit permissions on the folder in which the current image resides. Fixed rendering of page versions that contain tags that have been deleted after the version was created.Rendering of page versions with deleted tags resulted in an empty pageto be displayed and an exception similar to the following to be thrown:com.gentics.api.lib.exception.InconsistentDataException: Data inconsistent: Container {xxx} of Value {xxx, xxx} does not exist! Fixed a javascript error that ocurred when changing the language of a content page. Fixed many of the administration pages in the Portal.Node module throwing a SGB-error (pages including form elements). Fixed problems when uploading files using the File Upload Plugin in Aloha Editor with Internet Explorer (any version) and a certain security level. Internet Explorer sometimes sends the full local path as filename when posting file uploads. Additionally, the path is not sent standard conformant, so that the receiving component is unable to determine the filename and will respond with an error. Fixed possible SGB when opening a page out of an inbox message and then starting to edit it. The itemlist (e.g scheduler task list) now displays correctly in firefox. A firefox bug caused some rendering error when the item rows were highlighted. This bug was now workarounded. Some i18n messages were corrected within the Gentics Content.Node UI. Fixed display of channels in the repository browser: Sometimes channels were shown in the repository browser (but not in the tree), although the user did not have sufficient permissions on that channel. Fixed the RestAPI Resource /rest/folder/getTemplates/ not having default values for the values sortby and sortorder.The default value for sortby is now “name“ and for sortorder it‘s “asc”.This also fixes the template ordering when creating a new page in Content.Node (alphabetical). Fixed menu in the channel synchronization (Details) being wrapped at the folder menu item. Fixed display of new uploaded files, when using the multifileupload: Uploaded files will now be immediately visible in the file list, after clicking OK in the file upload dialog. Fixed message dialog overlay in the tree navigation (instant messaging, system messages) always being ontop of the frame instead on top of the current scrolling position. The workflow event “on page publish“ and the event reaction “cn_page_proof“have been discontinued.Existing workflows will be unaffected by this change. However, it is notpossible to create new “on page publish“ events or “cn_page_proof”reactions. After channel synchronization is done, the tree is reloaded to reflect possible changes in the folder structure. Manual Change In version 5.4.19 the template mimetype was changed from text/js to text/javascript. This change was reverted due to an incompatibility with Gentics Portal.Node. This incompatibility was resolved for Gentics Portal.Node releases that were made after Update 11927 2012-03-02. Once you have updated your Gentics Portal.Node installations you can execute the following sql statement within your node database to apply the change. A security issue with the Gentics Content.Node session has been resolved. Fixed imagemanipulation window doesn‘t close automatically and causes an SGB in the main window when opened from the tagfill dialog. Fixed a bug that cuased the Aloha page not to be rendered in Aloha mode (page can‘t be edited) if an extensible part type is used in the page to resolve properties. Revived the “edit in language” option in the menu of a page in the page view and also moved the object properties back to the main menu. Fixed tags inserted via the tag-fill-dialog and rendered via a Velocity part can‘t be edited after the tag-fill-dialog closes. Changed the ETA displayed for the publish duration time in the Gentics Content.Node startpage to be more human readable. Fixed a bug in multichannelling, that prevented assigning of channels to contentrepositories. Fixed StackOverflowException during publishrun. Made the Content.Node file uploader (including Rest-API) checks more consistent.They now all check if the filename length does not exceed 64 characters andif the characters in the filename are all valid (no whitespace, ...)Allowed characters in the filename are: a-z A-Z 0–9 – _ . Fixed NullPointerException that occurred when pages were created through the REST API. Fixed current content is displayed in older page versions. Changed the outdated mimetype text/js (not used anymore) to text/javascript when creating new pages. Fixed html linebreaks being removed when opening a tag with a part of a HTML type which is inline editable and the feature “live-br2nl“ is turned on.The feature “live-br2nl” is now only used for none-HTML tagtype-parts. Tag icons are now directly visible. Previously tag icons were only visible once the mouse was moved. Fixed changing the template of multiple pages in the background only changed the first template of the first selected page. Fixed page versioning creating a new version of a page when the page is moved to the publication queue (for users without publication rights)and the page wasn‘t modified. Removed double ; at the end of the SQL query when checking an empty content repository (CR creation). Fixed a bug within the multifile uploader which caused all uploads to be created with the default mime type application/octet-stream. The uploader will no determine the mimetype by examing the file extension and other information when no mimetype was specified by the browser. Fixed Javascript error that occurred in the Live-Editor Wiki mode with IE7. Fixed possible deadlock when (long running) job to change template of pages was running parallel to the publish process. Fixed out of memory error that occured when resizing image with the image store that exceeded a width or height of 20000 pixel and more. The genticsimagestore will now only allow resizing of images with a width and height of 10000 pixels max. Fixed a bug that sometimes occurred when images were published into the content repository.The bug was caused by the wrong object type (10011 instead of 10008)being used when images were published into a content repository. The tag fill lightbox will now no longer close once ESC key is pressed. Clicking in the shadow area of the lightbox will also no longer close the box. Previously the lightbox could be closed accedentialy by clicking in the wrong place. All changes were lost. Fixed a bug in multichannelling, that caused an SGB when deleting a channel and left inconsistent data in the database, that possibly caused other problems. Fixed edit page link in the Assistant of the Aloha-Editor mode broke the page layout. Fixed an error that prevented restoration of page versions. Fixed NullPointerException that occurred when pages were created through the REST API. Manual Change The Apache HTTPD package has to be updated to the latest version. The REST API page/restore restore versions was optimized to be more consistant. Inserted an input validation for HTML for the tagtype properties when the “validation” feature is turned on. See: Validation The page copy action performance was enhanced. Fixed errors that were caused by missing folder or template objects duringa publishrun with versioned publishing enabled.Versioned publishing will render and publish the published content ofpages that are included in other pages, for example via an Overview, ora Tag (page), or similar TagTypes that can include content from otherpages, or via a Page variant. Additionally, there were some changes concerning the versioning of pages. First, the folder of a page has ben excluded from versioning. This meansthat the page will always be rendered in its current folder. Forexample, Changelog will render the name of the current foldereven in an older version of the page. Before this change, the name ofthe folder where the page was when the version was created was renderd. Second, the template of a page is still versioned, but should thetemplate of an older version of the page have been deleted, the currenttemplate will be used as a fallback and a warning will be logged. Toavoid this, never delete a template that may be used by older versionsof a page. These changes apply even when the versioned publishing feature is turnedoff. Fixed the old file/image uploader default filename containing a space which causes the validation to print an error.Seperated the headline and the filename translations. Fixed the action icons (for multiple item actions) not being shown anymore in some folder views (images, templates, ...) Fixed setting of filetype when uploading Files via the REST API. If the filetype is sent from the client, there is no auto-detection done on server side. Fixed internationalization in Aloha-Editor assistant frame. Manual Change The tagfill dialog will now only contain jquery version 1.6.1. Previously two different jquery versions were loaded. This change may affect existing custom form tagtype implementations. Please note that loading a second jquery version by means of a custom form tag may cause unexpected issues with existing javascript features of Gentics Content.Node. We suggest using the new jquery version 1.6.1. Removed most of the action icons from the page list view again (at the right side of the actionlist) A logout link was added to the selfupdate dialog. It is now advised to logout and login again after the update was completed. This step ensures that the interface of the update user will be loaded correctly after the system was updated. Added a search field and button to the repository browser for linking pages and files in Aloha Editor. When adding links to internal pages or files using Aloha, the path information of the pages in the search dropdown will no longer start with the Node name, because this is redundant information. Added name ‘inserttag‘ for insert tag button for Aloha Editor‘s gcn plugin to make it configureable. Fixed possible errors (EmptyStackException) during publish process when using multithreaded publishing together with multichannelling. Fixed filling of tags with the new Minibrowser in the tagfill dialog when multichannelling is used: When an item is selected in the Minibrowser, the form will be posted and the tagfill dialog re-rendered.This is necessary for custom form tag implementations that need to be re-rendered whenever some other parts change. Fixed SGB that occured when accessing the node creation dialog directly after login. Fixed the tooltip speech bubbles in dialogs sometimes messing up the page by adding whitespace at the top (resulted in annoying jittering)This mostly happened in Firefox 10. Fixed Gentics Content.Node redirecting to the login page when pressing the enter button in the Imagemanipulation properties sidebar. When using firefox 10: The construct properties view will require Firefox 10.0.0.2 or later to display correctly. Older Firefox version (>10) contain a bug that prevents correct display of that particular view. Fixed two SGB‘s within the tagfill dialog. The first one occured when accessing the overview tagfill dialog. The second one occured when trying to upload file using the old file uploader dialog. These errors only occred while editing in frontend mode. Fixed the old singlefile Content.Node 4 Uploader not taking file extensions with numbers in account.For example: sound.mp3, it didn‘t add and check the file extension of the file automatically. Fixed resolving of tag parts in custom part types, when the custom part type is not editable. Fixed performing an import or deleting a part of a TagType hangs because of a missing index on the value_nodeversion.part_id column. Fixed links in the assistant frame open in the lower frame of the translation split-view when a page is translated. Added FileUploadManipulator for files that are being created via REST API. Fixed possible NPE when no transaction is available. Added some missing icons in the Content.Node menu. It is now possible to recursively search for folders containing a given search string in the name. Fixed permission error when translating pages without create permission.When a role only had the translate permission, but no the create permission, a fatal error was reported. Fixed possible SGB when listing templates in channels, were one of the templates was initially created in a folder, that no longer exists. Changed the publication links to be more consistent across pages.The “publish approve“ link will now be always shown in the menu and the assistant when the user has the rights for it.The “publish“ and “publish at” links are also also always shown, no matter if the user has the rights or not. Fixed missing buttons for Repository Browser and Fileupload in Aloha Editor. Fixed quick recursive translation feature.The quick recursive translation feature allows the fast creation of language variants (“Create translations” menu item in the page list). The feature is not enabled by default. The feature stopped working because of a recursive dependency being declared resulting in a page load error. Fixed authentication error in fileuploader when the session secret was provided via cookie instead of placing it in the multipart payload. Fixed display of node list for users with restricted permissions. Fixed the fileuploader fallback not working in Internet Explorer.There has been a problem with the mimetype which has been fixed. We have also removed a Quicktime plugin check which wasn‘t necessary. Fixed another situation, where the display of conflicting pages was wrong in a multichannel environment. Fixed javascript error in tagfill dialog. Fixed progressbar not disappearing when saving or editing an aloha page. Enhanced the Content.Node menu on dark/black backgrounds (pages, templates). It now has a light border around it.Also made the main menu highlighting stay when the submenu is currently open. Fixed SGB error appearing when viewing the taglist of a template with tags that don‘t have a tagtype. Fixed SGB error when setting a page language. Fixed menubar not being in 100% width in the new chrome beta. Fixed tag buttons sometimes jumping when clicking on it when editing pages with Aloha editor.This has been the case when there has been no content in the editable and the tag button was inside another editable. Copying or moving pages, creating page variants and copying or linking templates in multichannelling environments will now allow also inherited folders in channels as target folders. With multichannelling feature activated lists of pages, files, template, images and folders will now contain a “Master” column which displays the name of the node the object has been inherited from. Only available in Channels. Quickjump will now assign pages to correct channels when multichannelling is enabled. Added “inheritedFrom” attribute to pages, files, templates, images and folders delivered via REST API. Contains string with the name of the Node the object was inherited from. Removed option to en/disable specific language assignments for channel nodes. Language options are now read-only for channels. Fixed copying of inherited or localized pages in localized folders: the page will now be created in the folder as local channel page. Fixed broken Repository Browser in Tagfill lightbox. Previously the ui of the component was broken when displayed in Internet Explorer. Fixed special case where the menu became hidden when opening the tagfill dialog.This was the case when opening the page via the startpage or the quickjump search and going to the page edit mode. Fixed display of conflicting page when creating/modifying a page in a way that would produce a filename conflict in a multichannelling environment. Fixed display of folders in search result lists when multichannelling is used. Fixed display of pages that are scheduled to be published in the future to display the time when multichannelling is used. Fixed duplicate slashes when loading minibrowser libraries with multichannelling feature enabled. Fixed issues with too small edit frame when using Aloha Editor with IE7 Fixed display of page icon when pages are scheduled to be published in the future, when multichannelling is used. Fixed missing top menu for node properties dialog. Fixed problem when removing localization from a subchannel, where localization was removed from the channel also. Fixed missing related links in the assistant frame for Aloha edit and previde modes. Fixed maintenance stream not being reset after all user session are cleared (can happen during the new BlackPanther update). Fixed searching of objects for creating links in Aloha when multichannelling is used: Always search objects in the correct channel now. Fixed IllegalAnnotationException when using the REST API to get XML data. Fixed bug that occured when uploading a file with the flash uploader. Internet Explorer 7 in combination with some versions of flash (incl. 11.1) previously passed cookie values to flash. The uploader will now no longer fail when a session secret previously was set using the passed cookie. Newer browsers won‘t pass the cookie because it was set to httponly uppon creation. Manual Change The permission check for the start-page setting for a folder was changed Previously, the user only needed permission to modify the object property (object.startpage) to be able to set the startpage.Now, a user needs to have edit permission on the object property as well as edit permissions on the folder. Aloha Editor‘s gcn-plugin will now compare the construct id instead of the tagname when searching for magic link constructs. Fixed english translation of warning message.The previously untranslated message was “aloha_msg_no_write_perm_opened_readonly”.Additionally, this message will now only be displayed if the page is opened in edit mode when the user has no permission to edit the page. Previously the message was also displayed when a page was opened in preview mode. Removed old newsurl from the gentics login that caused a https security warning in Internet Explorer. Fixed quickjump sometimes not loading pages correctly and stating that the searched page could not be found. Fixed changing the stream in the user settings not updating the top left logo frame. Fixed connection pool limit for the urlincludeimp. Previously the url include imp did only allow two connections per host. We increased that limit to 20 by default.The default connection limit can be changed by the following java system properties: Fixed the positions of the Content.Node buttons. Previously some buttons were not aligned correctly. Fixed null pointer exception in REST APIWhen a page was retrieved with the REST API (or displayed with Aloha)Overview Tags that were inserted but never modified caused a nullpointer exception. Changed the right top gravatar user logo to be loaded from the local system instead of gentics.com,and also made it working via https. Fixed the time management returning an error page when editing a page. Fixed javascript error within the file upload dialog. Removed stars from Content.Node title because they are sometimes corrupted for unknown reasons. Fixed the top left logo and the blackpanther stream position. Extended LDAP functionality so LDAP groups with unique users as attributes can be used. Added PPTX mimetype mapping to page import.Also, custom mime-type mappings can now be configured through thenode.conf $CN_MIME_TYPES variable. For example, to add a mapping forfiles with the .pptx extension: The new Feature “Channel Synchronization” allows easy synchronziation of channels with their master node (in Multichannelling). The new Feature “Multichannelling” allows creation of Channels, that inherit Folders, Pages, Images, Files and Templates from another Node. Improved error handling if user is not assigned to any usergroup. Fixed: Problem with extended LDAP functionality. Fixed output textboxes being too small in the scheduler Fixed: Live preview for pages in multichannelling will now render page in the correct scope (channel) Fixed tipsy balloons sometimes not getting hidden again in forms. Fixed scrolling position in the tree navigation not being remembered. Fixed a bug in the image manipulator which resulted in broken images when resizing or cropping images with uppercase file extensions. Fixed a bug that could cause publishing errors when the java cache was empty. The publisher error was caused by issuing multiple streaming resltsets for one connection. Fixed alignment of multiple form buttons for Internet Explorer. Fixed javascript error when viewing the properties (name, description) of an image file. The multipart flash upload got a security fix. Made the frame resizing borders of the tree more pretty Replaced the stars in the CMS title (Enterprise CMS) to their none-encodede version to fix them sometimes getting broken. Added “Black Panther” highlighting style to the breadcrumb navigation when hovering the links Removed not very commonly used feature to move the assistant frame to the bottom Fixed frame flickering bug when resizing the tree in Internet Explorer Fixed the left top logo frame getting messed up when minimizing the tree Fixed stream images not being displayed in Internet Explorer in the user settings Fixed the position of the submenu sometimes not being calculated correctly when resizing the tree frame very small Fixed an user-error when creating a new tagtype, trying to view the tagtype properties and trying to create a new template Fixed frame resizing bug in chrome when tree was being collapsed Fixed issue with the generation of the Folder (Upload) tag part that caused the following tag part form elments to be hidden when no folder was selected. Removed the minimize button in the tree because it has no use anymore. The width of the left navigation tree will be saved from now on after resizing. NOTE: The current update resets all user sessions.This is being done because the ability to minimize stream was removed because of incompatibility with the new Black Panther UI. Removed the ability to hide the top stream because it is not compatible with the new Blackpanther UI Follow-up tasks have a new checkbox called “Follow on success”. If checked, the task will only run if the preceding task exits successfully. If not checked, the task will run regardless of the exit status of the preceding task. The left assistent won‘t be hidden anymore when viewing/editing a page and Alohaeditor is enabled Fixed inconsistent display, on the start page, of pages to be published / remaining to be published Fixed the quickjump autocompletion not working on the start page. Fixed linking and unlinking of nodes from content repositories.The nodeobject cache was not cleared when a node was linked to or unlinked from a contentrepository. Fixed tables not being placed under the paging navigation under certain cirumstances in firefox. Fixed the quickjump autocompletion not working on the start page. Fixed loading and saving of images with the imagemanipulation2 feature.The URL for loading and saving images had one slash too much which resulted in a 404 Not Found HTTP response. Fixed two errors when opening an Aloha page in IE7# A JavaScript error occurred when clicking the Live-Preview menu item when insde an Aloha page# When leaving an Aloha page, for example by clicking on a folder in the tree, instead of changing the location of the existing frame, a new window opened. Manual Change The FTP configuration within the node settings was removed. Please use scheduler tasks instead.Here is an example task template that will sync a Node and the GenticsImageStore folder for that node: Manual Change Fixed page-import doesn‘t fill parts with cn_value keyword bug The previous behaviour during a page import filled either a visible or editable part of an imported tag with the element contents. When thefeature cn_page_import_fill_editable_part was true, an editable part wasfilled. Otherwise a visible part was filled.This behaviour was contrary to the documentation, which states that the part with keyword “cn_value“ is filled with the element contents.The behaviour was fixed, so that “cn_value“ will be filled, if it exists. If no such part exists, the import will fall-back to the old behaviour.All tag-types that are used with the page-import must be checked for compatibility with the new behaviour. It must be ensured that, if there is a part with keyword “cn_value” in a tag-type, that it really is thepart that should be filled during page-import, and not one of the other editable or visible parts. Fixed security issues. The LDAP login field for groups can now be mapped with a string which should match the description of the appropriate CMS group. The Gentics Content.Node backend ui was overhauled. This includes multiple changes on ui css and on some backend dialogs.# All user related information are located at the top right cornor. Users may upload an avatar image to gravatar.com using their registered email adress.# When navigating through folders changing the folder views has become more intuitive.# Above page, file and image list a breadcrumb helps navigating.# The main tree view can now be adjusted in width. The tree can also be closed permanently.# Structure of rightclick submenues on page, file and image lists have been reorganized.# Access to the real editor from the page menu has been removed. The default maximum size of tag-values has been increased to from 100KB to 1MB. Fixed the “publish” menu entries not being shown in the page menu when it was shown in the page list context menu (inconsistent behavior). It is now always shown. Fixed non-transactional delete of tagtypes that caused data inconsistency.When a tagtype was deleted, it was possible that template-tags or content-tags referring to the tagtype were left in the system, causing problems with the import/export feature. Fixed: opening a WebDAV folder didn‘t work with some OS and browser configurations Fixed url generation within imagemanipulation2. Previously image/css/js urls were only working within cms and not within the portal. Fixed system messages when a page is put back into revision.Only the ID of the pages that were put into revision were shown in the system message, now the name (incl. full path) + ID are shown.Additionally, too many messages were sent to the editor of the page: one message that lists all pages, and one additional messaeg for each page. Now, only the first message, that lists all pages, will be sent. Fixed rare case when filename is ~62 characters long and the automatically added file extension was cutted (example: .php -> .ph) Fixed omissions in user list when pages are being assigned for revision. A previous fix to disable the paging of the list in the "assign for revision" dialog caused some users to be omitted from the list.
Bugfix SUP-3849
Bugfix SUP-3811
Bugfix SUP-3819
Bugfix SUP-3830
Bugfix SUP-3786
Bugfix SUP-3858
New UI Update
New UI Update
New UI Update
Gentics Content.Node 5.26.6
Bugfix SUP-3780
Bugfix SUP-3679
Bugfix SUP-3743com.gentics.api.lib.exception.NodeException: Error while adding a dependency where logged. Those errors had no functional consequence and will be omitted now.
Bugfix SUP-3808
Gentics Content.Node 5.26.5
Bugfix SUP-3775
Bugfix SUP-3752URL (page) is filled, the Repository Browser will show possible target pages in the current language, even if it is different from the edited page. This has been changed now, the Repository Browser will now use the edited page‘s language.
New UI Update
Gentics Content.Node 5.26.4
Documentation SUP-3719
Documentation SUP-3715
Bugfix SUP-3614
Bugfix SUP-3724span to a div, the updated page would still render the block with a span root tag, which could also lead to invalid markup. This has been fixed.
Bugfix SUP-3739Clean data would incorrectly remove objects from the ContentRepository for the master nodes. This has been fixed now. In cases, where objects have been incorrectly removed, the master nodes must be republished using the content maintenance.
New UI Update
Gentics Content.Node 5.26.3
Bugfix SUP-3655
New UI Update
New UI Update
Gentics Content.Node 5.26.2
Documentation SUP-3647
Please also note that Gentics CMS can now also be used in combintation with MariaDB 5.5 or MariaDB 10.x instead of MySQL. The Gentics Content.Node Compatibility List has been updated as well.
Bugfix SUP-3690
Bugfix SUP-3662
Gentics Content.Node 5.26.1
Enhancement SUP-3356
Please also note that Gentics CMS can now also be used in combintation with MariaDB 11.0 instead of MySQL. The Gentics Content.Node Compatibility List has been updated as well.
Documentation SUP-3625
Bugfix SUP-3636
Bugfix SUP-3443/Node/.node/setup-database.php for resetting the database will now set an exit status != 0 when it fails.
Bugfix SUP-3619activiti_integration was activated without restarting the server, the maintenance dialog for users with admin permission for the task management showed an SGB. This has been fixed now.
Bugfix SUP-3605objprop_page_edit_assistant have been fixed: # The preview of inherited pages did not work (showed an empty page) # When opening the preview of a page, the page was locked
Bugfix SUP-3434-). This has been fixed now.
Gentics Content.Node 5.26.0
Enhancement GTXPE-54rest/user/me/data allows to store user specific data in JSON format to the server. For details see the REST API documentation
Enhancement GTXPE-49
New UI Update
Gentics Content.Node 5.25.32
Enhancement SUP-4907
Bugfix SUP-4293
Bugfix SUP-4308
Bugfix SUP-4363
Bugfix SUP-4867
Bugfix SUP-4824
Bugfix SUP-4910
Gentics Content.Node 5.25.31
Bugfix SUP-4832
Gentics Content.Node 5.25.30
Bugfix SUP-4530
Bugfix SUP-4638
Bugfix SUP-4740/user/save/{id} was too restrictive and has been fixed now.
Bugfix SUP-4309
Gentics Content.Node 5.25.29
Documentation SUP-3892tagfill_light has been added to the Guides
Gentics Content.Node 5.25.28
Documentation SUP-4625
Documentation SUP-4069
Bugfix SUP-4235
Bugfix SUP-4110
Bugfix SUP-4017
Bugfix SUP-4545
Bugfix SUP-4492
Bugfix SUP-4236
Bugfix SUP-4000
Gentics Content.Node 5.25.26
Bugfix SUP-4274
Bugfix SUP-4372
Bugfix SUP-4430
Bugfix SUP-4360
Bugfix SUP-4358
Gentics Content.Node 5.25.25
New UI Update
New UI Update
New UI Update
New UI Update
New UI Update
New UI Update
New UI Update
New UI Update
Gentics Content.Node 5.25.24
Bugfix SUP-4193
Gentics Content.Node 5.25.23
Bugfix SUP-4108
Bugfix SUP-4135
Bugfix SUP-3980
Gentics Content.Node 5.25.22
/Node/etc/conf.d/node.db.conf. If there is no such file – create it.
In the node.db.conf create the following entry:
bc. $SETTINGS[“jdbcparameters“] = “useSSL=false“;
If the jdbcparameters index is already set concatenate parameters with “&“ like
bc. $SETTINGS[“jdbcparameters“] = “someOtherParam=1&useSSL=false”;
When using SSL, server certificate verification should be enabled and configured properly according to the MySQL documentation. See Connecting Securely Using SSL for more information.
Bugfix SUP-4082
Bugfix SUP-4081
Bugfix SUP-4079
Bugfix SUP-4111
Gentics Content.Node 5.25.21
Documentation SUP-4037
Documentation SUP-4006
Bugfix SUP-3543
Bugfix SUP-4021
Bugfix
Bugfix SUP-3991
Bugfix SUP-3288
Bugfix SUP-3997
Bugfix SUP-3914/file/save/{id} with Content-Type: multipart/form-data (for fileuploads) with Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 (or something similar, which preferred xml over json as response) always caused an Internal Server Error (500) response. This has been fixed now.
Gentics Content.Node 5.25.20
Documentation SUP-3934
Documentation SUP-3952
Bugfix SUP-3915
Bugfix SUP-3926
Bugfix SUP-3592
Bugfix SUP-3301
Gentics Content.Node 5.25.19
Bugfix SUP-3591
Bugfix SUP-3867
Bugfix SUP-3908
Bugfix SUP-3871copy_tags to Copy & Paste multiple tags at once, the tags were copied but not inserted at the paste position due to a javascript error. This has been fixed now.
Bugfix SUP-3873
Bugfix SUP-3876
Bugfix SUP-3832
Gentics Content.Node 5.25.18
Enhancement SUP-3699/Node/etc/ directory which is the default location for the configuration file.
Documentation SUP-3884
Bugfix SUP-3897
Bugfix SUP-3878
Bugfix SUP-3725
Bugfix SUP-3857 <object type="application/x-shockwave-flash" data="<node videourl>">
Gentics Content.Node 5.25.17
Documentation SUP-2680
Bugfix SUP-3601
Bugfix SUP-3837file_fetch feature into folders with restricted inheritance (in a multichannelling environment), were not restricted in their inheritance, which subsequently caused errors in the publish process. This has been fixed now.
Bugfix SUP-3797
Bugfix SUP-3820
Bugfix SUP-3849
Bugfix SUP-3811
Bugfix SUP-3819
Bugfix SUP-3830
Bugfix SUP-3786
Bugfix SUP-3858
Gentics Content.Node 5.25.16
Bugfix SUP-3780
Bugfix SUP-3679
Bugfix SUP-3743com.gentics.api.lib.exception.NodeException: Error while adding a dependency where logged. Those errors had no functional consequence and will be omitted now.
Bugfix SUP-3808
Gentics Content.Node 5.25.15
Bugfix SUP-3775
Bugfix SUP-3752URL (page) is filled, the Repository Browser will show possible target pages in the current language, even if it is different from the edited page. This has been changed now, the Repository Browser will now use the edited page‘s language.
Gentics Content.Node 5.25.14
Documentation SUP-3719
Bugfix SUP-3614
Bugfix SUP-3724span to a div, the updated page would still render the block with a span root tag, which could also lead to invalid markup. This has been fixed.
Bugfix SUP-3739Clean data would incorrectly remove objects from the ContentRepository for the master nodes. This has been fixed now. In cases, where objects have been incorrectly removed, the master nodes must be republished using the content maintenance.
Gentics Content.Node 5.25.13
Bugfix SUP-3655
New UI Update
New UI Update
New UI Update
Gentics Content.Node 5.25.12
Bugfix SUP-3690
Bugfix SUP-3662
Gentics Content.Node 5.25.11
Enhancement SUP-3356
Please also note that Gentics CMS can now also be used in combintation with MariaDB 11.0 instead of MySQL. The Gentics Content.Node Compatibility List has been updated as well.
Documentation SUP-3625
Bugfix SUP-3636
Bugfix SUP-3443/Node/.node/setup-database.php for resetting the database will now set an exit status != 0 when it fails.
Bugfix SUP-3619activiti_integration was activated without restarting the server, the maintenance dialog for users with admin permission for the task management showed an SGB. This has been fixed now.
Bugfix SUP-3605objprop_page_edit_assistant have been fixed: # The preview of inherited pages did not work (showed an empty page) # When opening the preview of a page, the page was locked
Bugfix SUP-3434-). This has been fixed now.
Gentics Content.Node 5.25.10
Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes.
Bugfix SUP-3568
Bugfix SUP-3268
Bugfix SUP-3576
Gentics Content.Node 5.25.9
Documentation SUP-3565target.size, which is an integer number in Bytes.
Gentics Content.Node 5.25.8
Completed Tasks can now also be filtered to show either all tasks or the tasks assigned to the current user.
Bugfix SUP-3556
Bugfix SUP-3551
Bugfix SUP-3551
Bugfix SUP-3212
Bugfix SUP-3563
Bugfix SUP-3212
Gentics Content.Node 5.25.7
Bugfix SUP-3547
Bugfix SUP-3347
Bugfix SUP-3527
Bugfix SUP-3367
Bugfix SUP-3538
Bugfix SUP-3378
Bugfix SUP-3334
Bugfix SUP-3324
Bugfix SUP-3501 or any of its subfolders contained objects in the wastebin which would not allow restricting the inheritance, the move operation did not fail with an explicit message naming the conflicting object, but failed with a general error message. This has been fixed now.
Bugfix SUP-3478
Bugfix SUP-3503
Bugfix SUP-3491/Node/bin/nodectl sometimes showed an error when stopping Tomcat, although stopping finally worked. This has been fixed now.
Bugfix SUP-3435URL (page) and one of them referenced a page in the wastebin, opening the tagfill dialog failed with an SGB. This has been fixed now.
Bugfix SUP-3514
Gentics Content.Node 5.25.6
Gentics Content.Node 5.25.5
Bugfix SUP-3441activiti_integration was used and a process was configured for the event onPagePublish publishing a new page (which was never published before) with publish at failed with an internal error. Also processes configured for the events onPagePublish or onPageTakeOffline where not started for pages that went on- or offline due to time management. Both issues have been fixed.
Bugfix SUP-3458attribute_dirting together with instant_cr_publishing and multichannelling, it could happen that objects that were modified again during a publish run for which they were scheduled to be published were not published correctly into channels (not all attributes were updated for the channels). This has been fixed now.
Bugfix SUP-3413Select (single) or Select (multiple) to Checkbox, the values of already existing tags where not consistently interpreted: # The tagfill dialog and the REST API showed the checkbox to not be checked # While rendering, the checkbox was treated as being checked. The tag had to be filled once to fix this behaviour. This issue has been fixed now, the checkbox will now consistenly be handled as “not checked”.
Bugfix SUP-3354
Bugfix SUP-3488
Bugfix SUP-3320
Bugfix SUP-3457
Gentics Content.Node 5.25.4
Bugfix
Bugfix SUP-3465URL parttypes did not work correctly, when this was done in a channel. This has been fixed now.
Gentics Content.Node 5.25.3
Documentation SUP-2106
Gentics Content.Node 5.25.2
Gentics Content.Node 5.25.1
Bugfix SUP-3424
Bugfix SUP-3329
Bugfix SUP-3274
Bugfix SUP-3283
Bugfix SUP-3405
Bugfix SUP-3392
Gentics Content.Node 5.25.0
ln -s /Node/.node/ui /Node/var/httpd/htdocs/.Node/ui
Enhancement GTXPE-42
Enhancement GTXPE-36
URL (page)URL (image)URL (file)URL (folder)node and the node ID as attribute nodeId. Please see the Meta Attributes in the Guides for implementation details. Also consult the guides page about the Aloha Editor Page Link Tag
It is important to note, that this change breaks Import/Export compatibility with older version of the Gentics CMS. It will no longer be possible to import data containing URL parttypes from Gentics CMS Version starting with 5.25.0 to Gentics CMS Versions older than
Enhancement GTXPE-37Overview has a new setting Sticky Channel, which allows selecting objects from specific channels in overviews. Please consult the section about the Overview Part Type in the Guides for further information.
Enhancement GCU-28
Enhancement GCU-121
rest/folder/getFolders/{id} has a new query parameter privilegeMap to get the privileges on each folder in a map representationrest/perm/{type}/{id} has a new query parameter map to get the privileges in a map representation
Enhancement GCU-76
Enhancement GCU-29
Gentics Content.Node 5.24.31
Documentation SUP-3892tagfill_light has been added to the Guides
Documentation SUP-4625
Documentation SUP-4069
Bugfix SUP-4235
Bugfix SUP-4110
Bugfix SUP-4017
Bugfix SUP-4545
Bugfix SUP-4492
Bugfix SUP-4236
Bugfix SUP-4000
Gentics Content.Node 5.24.29
Bugfix SUP-4274
Bugfix SUP-4372
Bugfix SUP-4430
Bugfix SUP-4360
Bugfix SUP-4358
Gentics Content.Node 5.24.28
Bugfix SUP-4193
Gentics Content.Node 5.24.27
Bugfix SUP-4108
Bugfix SUP-4135
Bugfix SUP-3980
Gentics Content.Node 5.24.26
/Node/etc/conf.d/node.db.conf. If there is no such file – create it.
In the node.db.conf create the following entry:
bc. $SETTINGS[“jdbcparameters“] = “useSSL=false“;
If the jdbcparameters index is already set concatenate parameters with “&“ like
bc. $SETTINGS[“jdbcparameters“] = “someOtherParam=1&useSSL=false”;
When using SSL, server certificate verification should be enabled and configured properly according to the MySQL documentation. See Connecting Securely Using SSL for more information.
Bugfix SUP-4082
Bugfix SUP-4081
Bugfix SUP-4079
Bugfix SUP-4111
Gentics Content.Node 5.24.25
Documentation SUP-4037
Documentation SUP-4006
Bugfix SUP-3543
Bugfix SUP-4021
Bugfix
Bugfix SUP-3991
Bugfix SUP-3288
Bugfix SUP-3997
Bugfix SUP-3914/file/save/{id} with Content-Type: multipart/form-data (for fileuploads) with Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 (or something similar, which preferred xml over json as response) always caused an Internal Server Error (500) response. This has been fixed now.
Gentics Content.Node 5.24.24
Documentation SUP-3934
Documentation SUP-3952
Bugfix SUP-3915
Bugfix SUP-3926
Bugfix SUP-3301
Gentics Content.Node 5.24.23
Bugfix SUP-3591
Bugfix SUP-3867
Bugfix SUP-3908
Bugfix SUP-3871copy_tags to Copy & Paste multiple tags at once, the tags were copied but not inserted at the paste position due to a javascript error. This has been fixed now.
Bugfix SUP-3873
Bugfix SUP-3876
Bugfix SUP-3832
Gentics Content.Node 5.24.22
Enhancement SUP-3699/Node/etc/ directory which is the default location for the configuration file.
Documentation SUP-3884
Bugfix SUP-3897
Bugfix SUP-3878
Bugfix SUP-3725
Bugfix SUP-3857 <object type="application/x-shockwave-flash" data="<node videourl>">
Gentics Content.Node 5.24.21
Documentation SUP-2680
Bugfix SUP-3601
Bugfix SUP-3837file_fetch feature into folders with restricted inheritance (in a multichannelling environment), were not restricted in their inheritance, which subsequently caused errors in the publish process. This has been fixed now.
Bugfix SUP-3797
Bugfix SUP-3820
Bugfix SUP-3849
Bugfix SUP-3811
Bugfix SUP-3819
Bugfix SUP-3830
Bugfix SUP-3858
Gentics Content.Node 5.24.20
Bugfix SUP-3780
Bugfix SUP-3679
Bugfix SUP-3743com.gentics.api.lib.exception.NodeException: Error while adding a dependency where logged. Those errors had no functional consequence and will be omitted now.
Bugfix SUP-3808
Gentics Content.Node 5.24.19
Bugfix SUP-3775
Bugfix SUP-3752URL (page) is filled, the Repository Browser will show possible target pages in the current language, even if it is different from the edited page. This has been changed now, the Repository Browser will now use the edited page‘s language.
Gentics Content.Node 5.24.18
Documentation SUP-3719
Bugfix SUP-3614
Bugfix SUP-3724span to a div, the updated page would still render the block with a span root tag, which could also lead to invalid markup. This has been fixed.
Bugfix SUP-3739Clean data would incorrectly remove objects from the ContentRepository for the master nodes. This has been fixed now. In cases, where objects have been incorrectly removed, the master nodes must be republished using the content maintenance.
Gentics Content.Node 5.24.17
Bugfix SUP-3655
Gentics Content.Node 5.24.16
Bugfix SUP-3690
Gentics Content.Node 5.24.15
Documentation SUP-3625
Bugfix SUP-3636
Bugfix SUP-3443/Node/.node/setup-database.php for resetting the database will now set an exit status != 0 when it fails.
Bugfix SUP-3619activiti_integration was activated without restarting the server, the maintenance dialog for users with admin permission for the task management showed an SGB. This has been fixed now.
Bugfix SUP-3605objprop_page_edit_assistant have been fixed: # The preview of inherited pages did not work (showed an empty page) # When opening the preview of a page, the page was locked
Bugfix SUP-3434-). This has been fixed now.
Gentics Content.Node 5.24.14
Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes.
Bugfix SUP-3568
Bugfix SUP-3268
Bugfix SUP-3576
Gentics Content.Node 5.24.13
Completed Tasks can now also be filtered to show either all tasks or the tasks assigned to the current user.
Bugfix SUP-3556
Bugfix SUP-3551
Bugfix SUP-3551
Bugfix SUP-3212
Bugfix SUP-3212
Gentics Content.Node 5.24.12
Bugfix SUP-3347
Bugfix SUP-3527
Bugfix SUP-3367
Bugfix SUP-3378
Bugfix SUP-3334
Bugfix SUP-3324
Bugfix SUP-3501 or any of its subfolders contained objects in the wastebin which would not allow restricting the inheritance, the move operation did not fail with an explicit message naming the conflicting object, but failed with a general error message. This has been fixed now.
Bugfix SUP-3478
Bugfix SUP-3503
Bugfix SUP-3491/Node/bin/nodectl sometimes showed an error when stopping Tomcat, although stopping finally worked. This has been fixed now.
Bugfix SUP-3435URL (page) and one of them referenced a page in the wastebin, opening the tagfill dialog failed with an SGB. This has been fixed now.
Bugfix SUP-3514
Gentics Content.Node 5.24.11
Gentics Content.Node 5.24.10
Documentation SUP-2106
Bugfix SUP-3441activiti_integration was used and a process was configured for the event onPagePublish publishing a new page (which was never published before) with publish at failed with an internal error. Also processes configured for the events onPagePublish or onPageTakeOffline where not started for pages that went on- or offline due to time management. Both issues have been fixed.
Bugfix SUP-3458attribute_dirting together with instant_cr_publishing and multichannelling, it could happen that objects that were modified again during a publish run for which they were scheduled to be published were not published correctly into channels (not all attributes were updated for the channels). This has been fixed now.
Bugfix SUP-3413Select (single) or Select (multiple) to Checkbox, the values of already existing tags where not consistently interpreted: # The tagfill dialog and the REST API showed the checkbox to not be checked # While rendering, the checkbox was treated as being checked. The tag had to be filled once to fix this behaviour. This issue has been fixed now, the checkbox will now consistenly be handled as “not checked”.
Bugfix SUP-3354
Bugfix SUP-3320
Bugfix SUP-3457
Gentics Content.Node 5.24.9
Gentics Content.Node 5.24.8
Bugfix SUP-3424
Bugfix SUP-3329
Bugfix SUP-3274
Bugfix SUP-3283
Bugfix SUP-3405
Bugfix SUP-3392
Gentics Content.Node 5.24.7
Bugfix
Bugfix SUP-3190
Bugfix SUP-3246
Bugfix
Gentics Content.Node 5.24.6
Bugfix SUP-3260
Gentics Content.Node 5.24.5
Bugfix SUP-3275
Gentics Content.Node 5.24.4
Bugfix SUP-3196
Bugfix SUP-3193attribute_dirting and publish handlers that access attributes, which are not dirted for specific objects, additional database statements were done to load the attribute values for each objects. This was inperformant and has been improved now.
Bugfix SUP-3230
Gentics Content.Node 5.24.3
Documentation
Bugfix SUP-3106/folder/disinherit/{id} REST endpoint if the parameter “exclude“ in the DisinheritRequest was set to true but the “disinherit“ and “reinherit” parameters where missing. Also some fields of the DisinheritRequest were undocumented. This has been fixed.
Bugfix SUP-3134
Bugfix SUP-3176dskeepselectvalues with a part of type “Select (multiple)“ in the tagfill dialog, clicking “Apply“ and then “OK“ (or clicking “Apply” multiple times) would clear all selected values from the part. This has been fixed now.
Gentics Content.Node 5.24.2
Bugfix SUP-3093
Bugfix SUP-2917
Bugfix SUP-3087
Bugfix SUP-3090
Bugfix SUP-2790
Bugfix SUP-2637createTag was in some cases not called. This has been fixed now.
Bugfix SUP-2768
Bugfix SUP-3107activiti_integration was activated and the CMS Tomcat not restarted, but only the configuration reloaded, a necessary background job was not started. This caused automatic handling of processes/tasks to not work. This has been fixed now.
Bugfix SUP-3091
Bugfix SUP-3099
Bugfix SUP-2719
Gentics Content.Node 5.24.1
Documentation SUP-3028
Bugfix SUP-2587
Bugfix SUP-2927
Bugfix SUP-3020
Bugfix SUP-2995
Bugfix SUP-3066
Bugfix SUP-3024
Bugfix SUP-3037
Bugfix SUP-2789
Bugfix SUP-3024
Bugfix SUP-3024
Bugfix SUP-2902
Bugfix SUP-2985
Bugfix SUP-3003
Gentics Content.Node 5.24.0
Enhancement
Enhancement GTXPE-4
Enhancement GTXPE-16
Enhancement
Enhancement GTXPE-11
Enhancement GTXPE-14
Enhancement GTXPE-16
Enhancement
Enhancement GTXPE-10
Gentics Content.Node 5.23.35
Documentation SUP-4037
Documentation SUP-4006
Bugfix SUP-3543
Bugfix SUP-4021
Bugfix SUP-3991
Bugfix SUP-3288
Bugfix SUP-3997
Bugfix SUP-3914/file/save/{id} with Content-Type: multipart/form-data (for fileuploads) with Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 (or something similar, which preferred xml over json as response) always caused an Internal Server Error (500) response. This has been fixed now.
Gentics Content.Node 5.23.34
Documentation SUP-3934
Documentation SUP-3952
Bugfix SUP-3915
Bugfix SUP-3926
Bugfix SUP-3301
Gentics Content.Node 5.23.33
Bugfix SUP-3591
Bugfix SUP-3867
Bugfix SUP-3908
Bugfix SUP-3871copy_tags to Copy & Paste multiple tags at once, the tags were copied but not inserted at the paste position due to a javascript error. This has been fixed now.
Bugfix SUP-3873
Bugfix SUP-3876
Bugfix SUP-3832
Gentics Content.Node 5.23.32
Enhancement SUP-3699/Node/etc/ directory which is the default location for the configuration file.
Documentation SUP-3884
Bugfix SUP-3897
Bugfix SUP-3878
Bugfix SUP-3725
Bugfix SUP-3857 <object type="application/x-shockwave-flash" data="<node videourl>">
Gentics Content.Node 5.23.31
Documentation SUP-2680
Bugfix SUP-3601
Bugfix SUP-3837file_fetch feature into folders with restricted inheritance (in a multichannelling environment), were not restricted in their inheritance, which subsequently caused errors in the publish process. This has been fixed now.
Bugfix SUP-3797
Bugfix SUP-3820
Bugfix SUP-3849
Bugfix SUP-3811
Bugfix SUP-3819
Bugfix SUP-3830
Bugfix SUP-3858
Gentics Content.Node 5.23.30
Bugfix SUP-3780
Bugfix SUP-3679
Bugfix SUP-3743com.gentics.api.lib.exception.NodeException: Error while adding a dependency where logged. Those errors had no functional consequence and will be omitted now.
Bugfix SUP-3808
Gentics Content.Node 5.23.29
Bugfix SUP-3775
Bugfix SUP-3752URL (page) is filled, the Repository Browser will show possible target pages in the current language, even if it is different from the edited page. This has been changed now, the Repository Browser will now use the edited page‘s language.
Gentics Content.Node 5.23.28
Documentation SUP-3719
Bugfix SUP-3614
Bugfix SUP-3724span to a div, the updated page would still render the block with a span root tag, which could also lead to invalid markup. This has been fixed.
Bugfix SUP-3739Clean data would incorrectly remove objects from the ContentRepository for the master nodes. This has been fixed now. In cases, where objects have been incorrectly removed, the master nodes must be republished using the content maintenance.
Gentics Content.Node 5.23.27
Bugfix SUP-3655
Gentics Content.Node 5.23.26
Bugfix SUP-3690
Gentics Content.Node 5.23.25
Documentation SUP-3625
Bugfix SUP-3636
Bugfix SUP-3443/Node/.node/setup-database.php for resetting the database will now set an exit status != 0 when it fails.
Bugfix SUP-3619activiti_integration was activated without restarting the server, the maintenance dialog for users with admin permission for the task management showed an SGB. This has been fixed now.
Bugfix SUP-3605objprop_page_edit_assistant have been fixed: # The preview of inherited pages did not work (showed an empty page) # When opening the preview of a page, the page was locked
Bugfix SUP-3434-). This has been fixed now.
Gentics Content.Node 5.23.24
Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes.
Bugfix SUP-3568
Bugfix SUP-3268
Bugfix SUP-3576
Gentics Content.Node 5.23.23
Completed Tasks can now also be filtered to show either all tasks or the tasks assigned to the current user.
Bugfix SUP-3556
Bugfix SUP-3551
Bugfix SUP-3551
Bugfix SUP-3212
Bugfix SUP-3212
Gentics Content.Node 5.23.22
Bugfix SUP-3347
Bugfix SUP-3527
Bugfix SUP-3367
Bugfix SUP-3378
Bugfix SUP-3334
Bugfix SUP-3324
Bugfix SUP-3501 or any of its subfolders contained objects in the wastebin which would not allow restricting the inheritance, the move operation did not fail with an explicit message naming the conflicting object, but failed with a general error message. This has been fixed now.
Bugfix SUP-3478
Bugfix SUP-3503
Bugfix SUP-3491/Node/bin/nodectl sometimes showed an error when stopping Tomcat, although stopping finally worked. This has been fixed now.
Bugfix SUP-3435URL (page) and one of them referenced a page in the wastebin, opening the tagfill dialog failed with an SGB. This has been fixed now.
Bugfix SUP-3514
Gentics Content.Node 5.23.21
Gentics Content.Node 5.23.20
Documentation SUP-2106
Bugfix SUP-3441activiti_integration was used and a process was configured for the event onPagePublish publishing a new page (which was never published before) with publish at failed with an internal error. Also processes configured for the events onPagePublish or onPageTakeOffline where not started for pages that went on- or offline due to time management. Both issues have been fixed.
Bugfix SUP-3413Select (single) or Select (multiple) to Checkbox, the values of already existing tags where not consistently interpreted: # The tagfill dialog and the REST API showed the checkbox to not be checked # While rendering, the checkbox was treated as being checked. The tag had to be filled once to fix this behaviour. This issue has been fixed now, the checkbox will now consistenly be handled as “not checked”.
Bugfix SUP-3354
Bugfix SUP-3320
Bugfix SUP-3457
Gentics Content.Node 5.23.19
Gentics Content.Node 5.23.18
Bugfix SUP-3424
Bugfix SUP-3329
Bugfix SUP-3274
Bugfix SUP-3283
Bugfix SUP-3405
Bugfix SUP-3392
Gentics Content.Node 5.23.17
Bugfix
Bugfix SUP-3190
Bugfix SUP-3246
Bugfix
Gentics Content.Node 5.23.16
Bugfix SUP-3275
Gentics Content.Node 5.23.15
Bugfix SUP-3196
Bugfix SUP-3230
Gentics Content.Node 5.23.14
Documentation
Bugfix SUP-3106/folder/disinherit/{id} REST endpoint if the parameter “exclude“ in the DisinheritRequest was set to true but the “disinherit“ and “reinherit” parameters where missing. Also some fields of the DisinheritRequest were undocumented. This has been fixed.
Bugfix SUP-3134
Bugfix SUP-3176dskeepselectvalues with a part of type “Select (multiple)“ in the tagfill dialog, clicking “Apply“ and then “OK“ (or clicking “Apply” multiple times) would clear all selected values from the part. This has been fixed now.
Gentics Content.Node 5.23.13
Bugfix SUP-3093
Bugfix SUP-2917
Bugfix SUP-3087
Bugfix SUP-3090
Bugfix SUP-2790
Bugfix SUP-2637createTag was in some cases not called. This has been fixed now.
Bugfix SUP-2768
Bugfix SUP-3107activiti_integration was activated and the CMS Tomcat not restarted, but only the configuration reloaded, a necessary background job was not started. This caused automatic handling of processes/tasks to not work. This has been fixed now.
Bugfix SUP-3091
Bugfix SUP-3099
Bugfix SUP-2719
Gentics Content.Node 5.23.12
Documentation SUP-3028
Bugfix SUP-2587
Bugfix SUP-2927
Bugfix SUP-3020
Bugfix SUP-2995
Bugfix SUP-3066
Bugfix SUP-3024
Bugfix SUP-3037
Bugfix SUP-2789
Bugfix SUP-3024
Bugfix SUP-3024
Bugfix SUP-2902
Bugfix SUP-2985
Bugfix SUP-3003
Gentics Content.Node 5.23.11
Bugfix SUP-2549
Bugfix SUP-2968
Bugfix SUP-2967
Bugfix SUP-2926
Gentics Content.Node 5.23.10
Bugfix SUP-2981channelid, when source and target of the link were in different nodes. This has been fixed now, so that the parameter channelid will only be added to the plink, when source and target nodes are different, and the target node actually is a channel.
Gentics Content.Node 5.23.9
Bugfix SUP-2872
Bugfix SUP-2620
Bugfix SUP-2704
Bugfix SUP-2860
Bugfix SUP-2162
Bugfix SUP-2829
Bugfix SUP-2620
Gentics Content.Node 5.23.8
Bugfix SUP-2594
Bugfix SUP-2877
Bugfix SUP-2833
Bugfix SUP-2810list method of the REST API. This has been fixed now.
Bugfix SUP-2863
Gentics Content.Node 5.23.7
Bugfix SUP-2233
Bugfix SUP-2810
Gentics Content.Node 5.23.6
Bugfix SUP-2816
Bugfix SUP-2683
Bugfix SUP-2794
Also a typo in the configuration examples has been fixed.
Gentics Content.Node 5.23.5
Documentation SUP-2577
Bugfix
Bugfix SUP-2634
Bugfix SUP-2783
Bugfix SUP-2731
Bugfix SUP-2776
Bugfix SUP-2728
Bugfix SUP-2728
Bugfix SUP-2775
Bugfix SUP-2475unlocalize REST endpoints required the channel sync permission to unlocalize object, even when a user had enough permissions to delete them. This has been fixed.
Bugfix SUP-2753
Bugfix SUP-2750
Bugfix SUP-2775#gtx_channel is used with an empty channel id, it will no longer log an error but will not change the channel scope (as if the channel directive was not used at all).
Gentics Content.Node 5.23.4
Bugfix SUP-2736
Bugfix SUP-2736
Bugfix SUP-2730
Gentics Content.Node 5.23.3
Bugfix
Bugfix SUP-2702
Bugfix SUP-2721
Bugfix SUP-2717
Bugfix SUP-2718
Bugfix SUP-2717
Bugfix SUP-2714
Gentics Content.Node 5.23.2
Documentation SUP-2698
Documentation SUP-2664
Bugfix SUP-2635
Gentics Content.Node 5.23.1
Bugfix id were not processed properly by the Aloha renderer which could cause problems with front end editing. This has been fixed.
Bugfix SUP-2376
Bugfix SUP-2419
Gentics Content.Node 5.23.0
Enhancement
New REST endpoints The following endpoints will return a list of localized copies together with their channel IDs for the respective object types:
/file/localizations/{id}/folder/localizations/{id}/image/localizations/{id}/page/localizations/{id}activiti_integration is activated, two new endpoints are available:
/activiti/processqueue returns a list of processes due to be triggered/activiti/status returns status information about the connected activiti server/folder/breadcrumb{id} now accepts an optional query parameter tags. If this parameter is true each folder in the breadcrumb list will also contain information about the tags associated with the folder.
Enhancement
Enhancement #gtx_channel has been added, which allows to render velocity code in the scope of another channel. Please read the Guides for more information.
Enhancement
Enhancement
Enhancement SUP-2320
If the CMS Webapp fails to start and the JVM parameter is set, the Tomcat will be terminated. The default behaviour is such that the Tomcat will be started, even if the CMS Webapp cannot be started.
Enhancement SUP-37
Bugfix SUP-1632
Bugfix /user/list could cause the request to fail. This has been fixed.
Bugfix /node/create and /node/save/{id} ignored the languagesId field. This has been fixed.
Gentics Content.Node 5.22.43
Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes.
Bugfix SUP-3568
Bugfix SUP-3268
Bugfix SUP-3576
Gentics Content.Node 5.22.42
Completed Tasks can now also be filtered to show either all tasks or the tasks assigned to the current user.
Bugfix SUP-3556
Bugfix SUP-3551
Bugfix SUP-3551
Bugfix SUP-3212
Bugfix SUP-3212
Gentics Content.Node 5.22.41
Bugfix SUP-3347
Bugfix SUP-3527
Bugfix SUP-3367
Bugfix SUP-3378
Bugfix SUP-3334
Bugfix SUP-3324
Bugfix SUP-3501 or any of its subfolders contained objects in the wastebin which would not allow restricting the inheritance, the move operation did not fail with an explicit message naming the conflicting object, but failed with a general error message. This has been fixed now.
Bugfix SUP-3478
Bugfix SUP-3503
Bugfix SUP-3491/Node/bin/nodectl sometimes showed an error when stopping Tomcat, although stopping finally worked. This has been fixed now.
Bugfix SUP-3435URL (page) and one of them referenced a page in the wastebin, opening the tagfill dialog failed with an SGB. This has been fixed now.
Bugfix SUP-3514
Gentics Content.Node 5.22.40
Gentics Content.Node 5.22.39
Documentation SUP-2106
Bugfix SUP-3413Select (single) or Select (multiple) to Checkbox, the values of already existing tags where not consistently interpreted: # The tagfill dialog and the REST API showed the checkbox to not be checked # While rendering, the checkbox was treated as being checked. The tag had to be filled once to fix this behaviour. This issue has been fixed now, the checkbox will now consistenly be handled as “not checked”.
Bugfix SUP-3354
Bugfix SUP-3320
Bugfix SUP-3457
Gentics Content.Node 5.22.38
Gentics Content.Node 5.22.37
Bugfix SUP-3424
Bugfix SUP-3329
Bugfix SUP-3274
Bugfix SUP-3283
Bugfix SUP-3405
Bugfix SUP-3392
Gentics Content.Node 5.22.36
Bugfix
Bugfix SUP-3190
Bugfix SUP-3246
Bugfix
Gentics Content.Node 5.22.35
Bugfix SUP-3275
Gentics Content.Node 5.22.34
Bugfix SUP-3230
Gentics Content.Node 5.22.33
Bugfix SUP-3196
Gentics Content.Node 5.22.32
Documentation
Bugfix SUP-3106/folder/disinherit/{id} REST endpoint if the parameter “exclude“ in the DisinheritRequest was set to true but the “disinherit“ and “reinherit” parameters where missing. Also some fields of the DisinheritRequest were undocumented. This has been fixed.
Bugfix SUP-3134
Bugfix SUP-3176dskeepselectvalues with a part of type “Select (multiple)“ in the tagfill dialog, clicking “Apply“ and then “OK“ (or clicking “Apply” multiple times) would clear all selected values from the part. This has been fixed now.
Gentics Content.Node 5.22.31
Bugfix SUP-3093
Bugfix SUP-2917
Bugfix SUP-3087
Bugfix SUP-3090
Bugfix SUP-2790
Bugfix SUP-2637createTag was in some cases not called. This has been fixed now.
Bugfix SUP-2768
Bugfix SUP-3107activiti_integration was activated and the CMS Tomcat not restarted, but only the configuration reloaded, a necessary background job was not started. This caused automatic handling of processes/tasks to not work. This has been fixed now.
Bugfix SUP-3091
Bugfix SUP-3099
Bugfix SUP-2719
Gentics Content.Node 5.22.30
Documentation SUP-3028
Bugfix SUP-2587
Bugfix SUP-2927
Bugfix SUP-3020
Bugfix SUP-2995
Bugfix SUP-3066
Bugfix SUP-3024
Bugfix SUP-3037
Bugfix SUP-2789
Bugfix SUP-3024
Bugfix SUP-3024
Bugfix SUP-2902
Bugfix SUP-2985
Bugfix SUP-3003
Gentics Content.Node 5.22.29
Bugfix SUP-2549
Bugfix SUP-2968
Bugfix SUP-2967
Bugfix SUP-2926
Gentics Content.Node 5.22.28
Bugfix SUP-2872
Bugfix SUP-2620
Bugfix SUP-2704
Bugfix SUP-2860
Bugfix SUP-2162
Bugfix SUP-2829
Bugfix SUP-2620
Gentics Content.Node 5.22.27
Bugfix SUP-2594
Bugfix SUP-2877
Bugfix SUP-2833
Bugfix SUP-2810list method of the REST API. This has been fixed now.
Bugfix SUP-2810
Bugfix SUP-2863
Gentics Content.Node 5.22.26
Bugfix SUP-2233
Gentics Content.Node 5.22.25
Bugfix SUP-2816
Bugfix SUP-2683
Gentics Content.Node 5.22.24
Documentation SUP-2577
Bugfix
Bugfix SUP-2634
Bugfix SUP-2783
Bugfix SUP-2731
Bugfix SUP-2736
Bugfix SUP-2728
Bugfix SUP-2728
Bugfix SUP-2475unlocalize REST endpoints required the channel sync permission to unlocalize object, even when a user had enough permissions to delete them. This has been fixed.
Bugfix SUP-2753
Bugfix SUP-2750
Bugfix SUP-2730
Gentics Content.Node 5.22.23
Bugfix
Bugfix SUP-2702
Bugfix SUP-2721
Bugfix SUP-2717
Bugfix SUP-2718
Bugfix SUP-2717
Bugfix SUP-2714
Gentics Content.Node 5.22.22
Documentation SUP-2698
Documentation SUP-2664
Bugfix SUP-2635
Gentics Content.Node 5.22.21
Bugfix SUP-1632
Bugfix id were not processed properly by the Aloha renderer which could cause problems with front end editing. This has been fixed.
Bugfix SUP-2376
Bugfix SUP-2419
Gentics Content.Node 5.22.20
Documentation SUP-2067
Bugfix SUP-2610
Bugfix SUP-2575
Bugfix SUP-2563
Bugfix SUP-2567
Bugfix SUP-2496
Gentics Content.Node 5.22.19
Gentics Content.Node 5.22.18
Bugfix SUP-2614
Bugfix
Gentics Content.Node 5.22.17
Bugfix SUP-2583
Bugfix SUP-2583
Bugfix SUP-2540
Bugfix SUP-2378
Gentics Content.Node 5.22.16
Bugfix SUP-2564
Gentics Content.Node 5.22.15
Bugfix SUP-2555
Bugfix SUP-2551
Bugfix SUP-2504
Bugfix SUP-2525
Bugfix SUP-2515
Bugfix SUP-2550
Bugfix SUP-2511
Bugfix SUP-2539
Bugfix SUP-2451
Bugfix SUP-2451
Bugfix SUP-2514
Gentics Content.Node 5.22.14
#set($anchor = "$!parts.anchor") instead of #set($anchor = "$parts.anchor").
Gentics Content.Node 5.22.13
Bugfix
Bugfix SUP-2495
Gentics Content.Node 5.22.12
Bugfix SUP-2201
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup. This fix just prevents certain subsequent errors when duplicates of a tag are already present in the page.
Gentics Content.Node 5.22.11
Bugfix SUP-2311
Bugfix SUP-2429
Bugfix SUP-2289
Bugfix SUP-2429
Bugfix SUP-2402
Gentics Content.Node 5.22.10
Documentation SUP-1298
Bugfix SUP-2365
Bugfix SUP-2415
Gentics Content.Node 5.22.9
Bugfix SUP-2354
Bugfix SUP-2290
Gentics Content.Node 5.22.8
Bugfix SUP-2269
Bugfix SUP-2353
Bugfix SUP-2303
Bugfix SUP-2177
Bugfix SUP-2338
Bugfix SUP-2324
tags. This has been fixed.
Gentics Content.Node 5.22.7
Bugfix SUP-2194
Gentics Content.Node 5.22.6
Bugfix SUP-2256
Bugfix SUP-2248publish_cache, wastebin and multichannelling and a localized page was put in the wastebin, the inherited page was not contained in the list of pages in a folder, if rendered in velocity. This has been fixed now.
Bugfix SUP-1804
Bugfix SUP-2029
Bugfix SUP-2222
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when duplicates of a tag are already present in the page. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2305
Bugfix SUP-2284
Bugfix SUP-2234
Gentics Content.Node 5.22.5
Gentics Content.Node 5.22.4
Gentics Content.Node 5.22.3
Bugfix SUP-2147
Bugfix SUP-2176
Bugfix SUP-1684
Gentics Content.Node 5.22.2
Bugfix SUP-2160
Bugfix SUP-1862
Also, request done via the REST API did not “touch” the systemsession by setting the time of the last access. This has also been fixed.
Bugfix SUP-2154
Gentics Content.Node 5.22.1
For this fix to work, also the implementation of the tagtype might be changed: The hardcoded type 10008 has to be replaced with $!{cms.tag.parts.file.target.ttype}. See the Guides:“http://www.gentics.com/Content.Node/guides/aloha_gcn_filelink_plugin.html” for details.
Bugfix
Bugfix SUP-2109
Bugfix SUP-2148
Bugfix SUP-2112
Bugfix SUP-1445
Bugfix SUP-1913
Bugfix SUP-1816
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when a tag is not converted to an aloha-block. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2107
Bugfix SUP-1826wastebin is activated, the group Node Super Admin will automatically get the permission to view the wastebin for all Nodes.
Gentics Content.Node 5.22.0
anchor must be added to the gtxalohapagelink, and its template must be updated.
Enhancement
Enhancement
New REST endpoints
/language/list returns a list of all available content languages/node/getLanguages/{id} returns a list of all content languages for the specified node/perm/list/{type} lists all groups with with their permission bits for the given object type
/user/list has new query parameter search to search in login, firstName, lastName and email/user/list result can be sorted by id/user/list has new query parameter group to add group information to response/msg/send allows sending translated messages in multiple languages
RestClient.authenticate() allows to authenticate session credentials (sid and secret)
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Gentics Content.Node 5.21.40
Bugfix
Bugfix SUP-3190
Bugfix SUP-3246
Bugfix
Gentics Content.Node 5.21.39
Bugfix SUP-3275
Gentics Content.Node 5.21.38
Bugfix SUP-3196
Bugfix SUP-3230
Gentics Content.Node 5.21.37
Documentation
Bugfix SUP-3106/folder/disinherit/{id} REST endpoint if the parameter “exclude“ in the DisinheritRequest was set to true but the “disinherit“ and “reinherit” parameters where missing. Also some fields of the DisinheritRequest were undocumented. This has been fixed.
Bugfix SUP-3134
Bugfix SUP-3176dskeepselectvalues with a part of type “Select (multiple)“ in the tagfill dialog, clicking “Apply“ and then “OK“ (or clicking “Apply” multiple times) would clear all selected values from the part. This has been fixed now.
Gentics Content.Node 5.21.36
Bugfix SUP-3093
Bugfix SUP-2917
Bugfix SUP-3087
Bugfix SUP-3090
Bugfix SUP-2790
Bugfix SUP-2637createTag was in some cases not called. This has been fixed now.
Bugfix SUP-2768
Bugfix SUP-3091
Bugfix SUP-3099
Bugfix SUP-2719
Gentics Content.Node 5.21.35
Documentation SUP-3028
Bugfix SUP-2587
Bugfix SUP-2927
Bugfix SUP-3020
Bugfix SUP-2995
Bugfix SUP-3066
Bugfix SUP-3024
Bugfix SUP-3037
Bugfix SUP-2789
Bugfix SUP-3024
Bugfix SUP-2902
Bugfix SUP-2985
Bugfix SUP-3003
Gentics Content.Node 5.21.34
Bugfix SUP-2549
Bugfix SUP-2968
Bugfix SUP-2967
Bugfix SUP-2926
Gentics Content.Node 5.21.33
Bugfix SUP-2872
Bugfix SUP-2620
Bugfix SUP-2704
Bugfix SUP-2860
Bugfix SUP-2162
Bugfix SUP-2829
Bugfix SUP-2620
Gentics Content.Node 5.21.32
Bugfix SUP-2594
Bugfix SUP-2877
Bugfix SUP-2833
Bugfix SUP-2810list method of the REST API. This has been fixed now.
Bugfix SUP-2863
Gentics Content.Node 5.21.31
Gentics Content.Node 5.21.30
Bugfix SUP-2816
Gentics Content.Node 5.21.29
Documentation SUP-2577
Bugfix
Bugfix SUP-2634
Bugfix SUP-2783
Bugfix SUP-2731
Bugfix SUP-2736
Bugfix SUP-2728
Bugfix SUP-2728
Bugfix SUP-2475unlocalize REST endpoints required the channel sync permission to unlocalize object, even when a user had enough permissions to delete them. This has been fixed.
Bugfix SUP-2753
Bugfix SUP-2750
Bugfix SUP-2730
Gentics Content.Node 5.21.28
Bugfix
Bugfix SUP-2702
Bugfix SUP-2721
Bugfix SUP-2717
Bugfix SUP-2718
Bugfix SUP-2717
Bugfix SUP-2714
Gentics Content.Node 5.21.27
Documentation SUP-2698
Documentation SUP-2664
Bugfix SUP-2635
Gentics Content.Node 5.21.26
Bugfix SUP-1632
Bugfix id were not processed properly by the Aloha renderer which could cause problems with front end editing. This has been fixed.
Bugfix SUP-2376
Gentics Content.Node 5.21.25
Documentation SUP-2067
Bugfix SUP-2610
Bugfix SUP-2575
Bugfix SUP-2563
Bugfix SUP-2614
Bugfix
Bugfix SUP-2567
Bugfix SUP-2496
Gentics Content.Node 5.21.24
Bugfix SUP-2583
Bugfix SUP-2583
Bugfix SUP-2540
Bugfix SUP-2378
Gentics Content.Node 5.21.23
Bugfix SUP-2555
Bugfix SUP-2504
Bugfix SUP-2525
Bugfix SUP-2515
Bugfix SUP-2550
Bugfix SUP-2511
Bugfix SUP-2539
Bugfix SUP-2451
Bugfix SUP-2451
Bugfix SUP-2514
Gentics Content.Node 5.21.22
Gentics Content.Node 5.21.21
Bugfix
Bugfix SUP-2495
Gentics Content.Node 5.21.20
Bugfix SUP-2201
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup. This fix just prevents certain subsequent errors when duplicates of a tag are already present in the page.
Gentics Content.Node 5.21.19
Bugfix SUP-2311
Bugfix SUP-2429
Bugfix SUP-2289
Bugfix SUP-2429
Bugfix SUP-2402
Gentics Content.Node 5.21.18
Documentation SUP-1298
Bugfix SUP-2365
Bugfix SUP-2415
Gentics Content.Node 5.21.17
Bugfix SUP-2354
Bugfix SUP-2290
Gentics Content.Node 5.21.16
Bugfix SUP-2269
Bugfix SUP-2353
Bugfix SUP-2303
Bugfix SUP-2177
Bugfix SUP-2338
Gentics Content.Node 5.21.15
Bugfix SUP-2194
Gentics Content.Node 5.21.14
Bugfix SUP-2256
Bugfix SUP-2248publish_cache, wastebin and multichannelling and a localized page was put in the wastebin, the inherited page was not contained in the list of pages in a folder, if rendered in velocity. This has been fixed now.
Bugfix SUP-1804
Bugfix SUP-2029
Bugfix SUP-2222
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when duplicates of a tag are already present in the page. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2305
Bugfix SUP-2284
Bugfix SUP-2234
Gentics Content.Node 5.21.13
Gentics Content.Node 5.21.12
Gentics Content.Node 5.21.11
Bugfix SUP-2147
Bugfix SUP-2176
Bugfix SUP-1684
Gentics Content.Node 5.21.10
Bugfix SUP-2160
Bugfix SUP-1862
Also, request done via the REST API did not “touch” the systemsession by setting the time of the last access. This has also been fixed.
Gentics Content.Node 5.21.9
For this fix to work, also the implementation of the tagtype might be changed: The hardcoded type 10008 has to be replaced with $!{cms.tag.parts.file.target.ttype}. See the Guides:“http://www.gentics.com/Content.Node/guides/aloha_gcn_filelink_plugin.html” for details.
Bugfix SUP-2109
Bugfix SUP-2148
Bugfix SUP-2112
Bugfix SUP-1445
Bugfix SUP-1913
Bugfix SUP-1816
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when a tag is not converted to an aloha-block. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2107
Bugfix SUP-1826wastebin is activated, the group Node Super Admin will automatically get the permission to view the wastebin for all Nodes.
Gentics Content.Node 5.21.8
Documentation SUP-2044
Bugfix SUP-2040
Bugfix SUP-2063
Bugfix SUP-2001
Bugfix SUP-2048
Bugfix SUP-2092
Bugfix SUP-1588
Bugfix SUP-2093
Gentics Content.Node 5.21.7
Bugfix SUP-1992
Bugfix SUP-1273
Bugfix SUP-2010
Bugfix SUP-2043Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'source'.
The Gentics Infoportal also contains a new FAQ page “How can I enable support for pages with more than 16MB of content?”.
Bugfix SUP-2064
Bugfix SUP-2065quickrecursivetranslations is activated, the context menu entry Create translations was shown to all users, even if they had no permission to create a single language. Also in the dialog, the languages were not filtered by permissions. Both issues have been fixed now: # The menu entry Create translations will only be shown, if the user has permission on at least a single language # The dialog will only show languages the user may create.
Bugfix SUP-2018
Bugfix
Bugfix SUP-2018
Bugfix SUP-1193
Bugfix SUP-1957
Bugfix SUP-2032
/file/delete/{id} to delete a file/image/delete/{id} to delete an image
have been added.
Bugfix SUP-1981
Bugfix SUP-1558
This especially concerns the search settings for object lists: Before this change, if a user made a search e.g. in the page list of a specific folder, this setting was still there, even if the user logged out and in again. After this change, search settings will be cleared when the user logs out.
Bugfix SUP-887
createtimestampcreatorcreatoremaileditoreditoremailedittimestampprioritypublisherpublishermailpublishtimestamp
Bugfix SUP-2009
Bugfix SUP-2019
Gentics Content.Node 5.21.6
Bugfix SUP-1849
Bugfix SUP-1257
Bugfix SUP-529clearfix which could conflict with pages using bootstrap. The conflicting class names have been removed.
Bugfix SUP-1976
Gentics Content.Node 5.21.5
Documentation SUP-1915
Bugfix SUP-1927-SUP-903
Bugfix SUP-1773
Bugfix SUP-1749
Bugfix SUP-1773
Gentics Content.Node 5.21.4
Bugfix SUP-1721
Bugfix SUP-1894
Bugfix SUP-1888
Bugfix SUP-1880
Bugfix SUP-1872
Bugfix SUP-1815
Please read the Wastebin Feature documentation for more information.
Gentics Content.Node 5.21.3
Bugfix SUP-1783
Bugfix SUP-1854publishedbefore filter with a request to /rest/folder/getPages the result would contain pages, that were not published yet. This has been fixed.
Gentics Content.Node 5.21.2
Documentation SUP-1777
Documentation SUP-1777
Bugfix SUP-1781
Bugfix SUP-1761
Bugfix SUP-1808
Bugfix SUP-1782contentfile_auto_offline feature would sometimes take files in master nodes offline which were still used in channels of a different master node. This has been fixed.
Bugfix SUP-1784
Bugfix SUP-889
Bugfix SUP-1677
Bugfix SUP-1761
Gentics Content.Node 5.21.1
Bugfix SUP-1520
Bugfix SUP-1576
Bugfix SUP-1771
Bugfix SUP-1520
Bugfix SUP-1697
Bugfix SUP-1487
Bugfix SUP-1600
Bugfix SUP-1519
Bugfix SUP-1774
Gentics Content.Node 5.21.0
Enhancement
Enhancement
Enhancement
Enhancement POST methods can be used to load multiple objects with a single request:
/folder/load/page/load/file/load/image/load
Enhancement
/node/create/ for creating a new node/node/save/{id} for saving changes to a node
Enhancement
Gentics Content.Node 5.20.51
Documentation SUP-3028
Bugfix SUP-2587
Bugfix SUP-2927
Bugfix SUP-3020
Bugfix SUP-2995
Bugfix SUP-3066
Bugfix SUP-3037
Bugfix SUP-2789
Bugfix SUP-3024
Bugfix SUP-2902
Bugfix SUP-2985
Bugfix SUP-3003
Gentics Content.Node 5.20.50
Bugfix SUP-2549
Bugfix SUP-2968
Bugfix SUP-2967
Bugfix SUP-2926
Gentics Content.Node 5.20.49
Bugfix SUP-2872
Bugfix SUP-2620
Bugfix SUP-2704
Bugfix SUP-2860
Bugfix SUP-2162
Bugfix SUP-2829
Bugfix SUP-2620
Gentics Content.Node 5.20.48
Bugfix SUP-2594
Bugfix SUP-2877
Bugfix SUP-2833
Bugfix SUP-2810list method of the REST API. This has been fixed now.
Bugfix SUP-2863
Gentics Content.Node 5.20.47
Gentics Content.Node 5.20.46
Bugfix SUP-2233
Bugfix SUP-2816
Gentics Content.Node 5.20.45
Documentation SUP-2577
Bugfix
Bugfix SUP-2634
Bugfix SUP-2783
Bugfix SUP-2731
Bugfix SUP-2736
Bugfix SUP-2728
Bugfix SUP-2728
Bugfix SUP-2475unlocalize REST endpoints required the channel sync permission to unlocalize object, even when a user had enough permissions to delete them. This has been fixed.
Bugfix SUP-2753
Bugfix SUP-2750
Bugfix SUP-2730
Gentics Content.Node 5.20.44
Bugfix
Bugfix SUP-2702
Bugfix SUP-2721
Bugfix SUP-2717
Bugfix SUP-2718
Bugfix SUP-2717
Bugfix SUP-2714
Gentics Content.Node 5.20.43
Documentation SUP-2698
Documentation SUP-2664
Bugfix SUP-2635
Gentics Content.Node 5.20.42
Bugfix SUP-1632
Bugfix id were not processed properly by the Aloha renderer which could cause problems with front end editing. This has been fixed.
Bugfix SUP-2376
Gentics Content.Node 5.20.41
Documentation SUP-2067
Bugfix SUP-2610
Bugfix SUP-2575
Bugfix SUP-2563
Bugfix SUP-2614
Bugfix
Bugfix SUP-2567
Bugfix SUP-2496
Gentics Content.Node 5.20.40
Bugfix SUP-2583
Bugfix SUP-2583
Bugfix SUP-2540
Bugfix SUP-2378
Gentics Content.Node 5.20.39
Bugfix SUP-2555
Bugfix SUP-2504
Bugfix SUP-2525
Bugfix SUP-2515
Bugfix SUP-2550
Bugfix SUP-2511
Bugfix SUP-2539
Bugfix SUP-2451
Bugfix SUP-2451
Bugfix SUP-2514
Gentics Content.Node 5.20.38
Gentics Content.Node 5.20.37
Bugfix
Bugfix SUP-2495
Gentics Content.Node 5.20.36
Bugfix SUP-2201
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup. This fix just prevents certain subsequent errors when duplicates of a tag are already present in the page.
Gentics Content.Node 5.20.35
Bugfix SUP-2311
Bugfix SUP-2429
Bugfix SUP-2289
Bugfix SUP-2429
Bugfix SUP-2402
Gentics Content.Node 5.20.34
Documentation SUP-1298
Bugfix SUP-2365
Bugfix SUP-2415
Gentics Content.Node 5.20.33
Bugfix SUP-2354
Bugfix SUP-2290
Gentics Content.Node 5.20.32
Bugfix SUP-2269
Bugfix SUP-2353
Bugfix SUP-2303
Bugfix SUP-2177
Bugfix SUP-2338
Gentics Content.Node 5.20.31
Bugfix SUP-2194
Gentics Content.Node 5.20.30
Bugfix SUP-2248publish_cache, wastebin and multichannelling and a localized page was put in the wastebin, the inherited page was not contained in the list of pages in a folder, if rendered in velocity. This has been fixed now.
Bugfix SUP-1804
Bugfix SUP-2029
Bugfix SUP-2222
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when duplicates of a tag are already present in the page. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2305
Bugfix SUP-2284
Bugfix SUP-2234
Gentics Content.Node 5.20.29
Bugfix SUP-2256
Gentics Content.Node 5.20.28
Gentics Content.Node 5.20.27
Gentics Content.Node 5.20.26
Bugfix SUP-2147
Bugfix SUP-2176
Bugfix SUP-1684
Gentics Content.Node 5.20.25
Bugfix SUP-2160
Bugfix SUP-1862
Also, request done via the REST API did not “touch” the systemsession by setting the time of the last access. This has also been fixed.
Gentics Content.Node 5.20.24
For this fix to work, also the implementation of the tagtype might be changed: The hardcoded type 10008 has to be replaced with $!{cms.tag.parts.file.target.ttype}. See the Guides:“http://www.gentics.com/Content.Node/guides/aloha_gcn_filelink_plugin.html” for details.
Bugfix SUP-2109
Bugfix SUP-2148
Bugfix SUP-2112
Bugfix SUP-1445
Bugfix SUP-1913
Bugfix SUP-1816
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when a tag is not converted to an aloha-block. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2107
Bugfix SUP-1826wastebin is activated, the group Node Super Admin will automatically get the permission to view the wastebin for all Nodes.
Gentics Content.Node 5.20.23
Documentation SUP-2044
Bugfix SUP-2040
Bugfix SUP-2063
Bugfix SUP-2001
Bugfix SUP-2048
Bugfix SUP-2092
Bugfix SUP-1588
Bugfix SUP-2093
Gentics Content.Node 5.20.22
Bugfix
Gentics Content.Node 5.20.21
Bugfix SUP-1992
Bugfix SUP-1273
Bugfix SUP-2010
Bugfix SUP-2043Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'source'.
The Gentics Infoportal also contains a new FAQ page “How can I enable support for pages with more than 16MB of content?”.
Bugfix SUP-2064
Bugfix SUP-2065quickrecursivetranslations is activated, the context menu entry Create translations was shown to all users, even if they had no permission to create a single language. Also in the dialog, the languages were not filtered by permissions. Both issues have been fixed now: # The menu entry Create translations will only be shown, if the user has permission on at least a single language # The dialog will only show languages the user may create.
Bugfix SUP-2018
Bugfix
Bugfix SUP-2018
Bugfix SUP-1193
Bugfix SUP-1957
Bugfix SUP-2032
/file/delete/{id} to delete a file/image/delete/{id} to delete an image
have been added.
Bugfix SUP-1981
Bugfix SUP-1558
This especially concerns the search settings for object lists: Before this change, if a user made a search e.g. in the page list of a specific folder, this setting was still there, even if the user logged out and in again. After this change, search settings will be cleared when the user logs out.
Bugfix SUP-887
createtimestampcreatorcreatoremaileditoreditoremailedittimestampprioritypublisherpublishermailpublishtimestamp
Bugfix SUP-2009
Bugfix SUP-2019
Gentics Content.Node 5.20.20
Bugfix SUP-1849
Bugfix SUP-1257
Bugfix SUP-529clearfix which could conflict with pages using bootstrap. The conflicting class names have been removed.
Bugfix SUP-1976
Gentics Content.Node 5.20.19
Documentation SUP-1915
Bugfix SUP-1927-SUP-903
Bugfix SUP-1773
Bugfix SUP-1749
Bugfix SUP-1773
Gentics Content.Node 5.20.18
Bugfix SUP-1721
Bugfix SUP-1894
Bugfix SUP-1888
Bugfix SUP-1880
Bugfix SUP-1872
Bugfix SUP-1815
Please read the Wastebin Feature documentation for more information.
Gentics Content.Node 5.20.17
Bugfix SUP-1783
Gentics Content.Node 5.20.16
Documentation SUP-1777
Bugfix SUP-1781
Bugfix SUP-1761
Bugfix SUP-1808
Bugfix SUP-1782contentfile_auto_offline feature would sometimes take files in master nodes offline which were still used in channels of a different master node. This has been fixed.
Bugfix SUP-1784
Bugfix SUP-889
Bugfix SUP-1677
Bugfix SUP-1761
Gentics Content.Node 5.20.15
Bugfix SUP-1520
Bugfix SUP-1576
Bugfix SUP-1771
Bugfix SUP-1520
Bugfix SUP-1697
Bugfix SUP-1487
Bugfix SUP-1600
Bugfix SUP-1519
Bugfix SUP-1774
Gentics Content.Node 5.20.14
Documentation SUP-1701
Bugfix SUP-1648
Bugfix SUP-1715
Bugfix SUP-1714
Bugfix SUP-1707always_localize was activated the dialogs for editing (object) properties of folders and pages sometimes would not open. This has been fixed.
Bugfix SUP-1728
Gentics Content.Node 5.20.13
Bugfix SUP-1415
Bugfix SUP-1592
Gentics Content.Node 5.20.12
Bugfix SUP-1589
Bugfix SUP-1486
Gentics Content.Node 5.20.11
Bugfix SUP-1337
Bugfix SUP-1399
Bugfix SUP-1398
Gentics Content.Node 5.20.10
Documentation SUP-1294
Bugfix SUP-1500
Bugfix SUP-1323
Bugfix SUP-1484
Bugfix SUP-1502
Bugfix SUP-1522
Bugfix SUP-861
Bugfix SUP-1469
Bugfix SUP-1516
Bugfix SUP-1491
Bugfix SUP-1522
Bugfix SUP-1467
Bugfix SUP-1399
Bugfix SUP-1485
Gentics Content.Node 5.20.9
Bugfix SUP-1459
Bugfix SUP-1336
Bugfix SUP-1396
Gentics Content.Node 5.20.8
Documentation SUP-1447
/CNPortletapp/rest/file/load/{id} should be added as path parameter, instead of a
query parameter, this has been corrected now.
Bugfix SUP-1399
Bugfix SUP-1342
Bugfix SUP-1334
Bugfix SUP-1399
Bugfix SUP-1441
Gentics Content.Node 5.20.7
Bugfix 1326
Bugfix SUP-1357
Bugfix SUP-1361
Bugfix SUP-1342
Bugfix SUP-1419
Bugfix SUP-1398
Bugfix SUP-1339
Gentics Content.Node 5.20.6
Gentics Content.Node 5.20.5
Documentation SUP-1325
Bugfix SUP-1303
Bugfix SUP-1307
Bugfix SUP-1235
Gentics Content.Node 5.20.4
Bugfix SUP-1266
Bugfix SUP-1281
Bugfix SUP-1068
Gentics Content.Node 5.20.3
Bugfix SUP-1196
Bugfix SUP-163
Instead of restarting Tomcat after the update, it is now stopped before updating the libraries and started again after the update is complete.
Bugfix SUP-641
Bugfix SUP-1124
0 instead of 10007 during the publish process. This has been fixed now.
Bugfix SUP-601
Bugfix SUP-601
Bugfix SUP-1126
Gentics Content.Node 5.20.2
Bugfix SUP-918
Bugfix SUP-1091
Bugfix SUP-1096
Bugfix SUP-1163
Bugfix SUP-1185
Bugfix SUP-1192
Bugfix SUP-1056
Bugfix SUP-1192
Bugfix SUP-918
Gentics Content.Node 5.20.1
Bugfix SUP-1078
Bugfix SUP-1003
Bugfix SUP-1114
Bugfix SUP-876
Bugfix SUP-754
Bugfix SUP-1010
Bugfix SUP-1086
Gentics Content.Node 5.20.0
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix SUP-932
Bugfix SUP-694
Gentics Content.Node 5.19.68
Documentation SUP-2067
Bugfix SUP-2610
Bugfix SUP-2575
Bugfix SUP-2563
Bugfix SUP-2614
Bugfix
Bugfix SUP-2567
Bugfix SUP-2496
Gentics Content.Node 5.19.67
Bugfix SUP-2583
Bugfix SUP-2583
Bugfix SUP-2540
Bugfix SUP-2378
Gentics Content.Node 5.19.66
Bugfix SUP-2555
Bugfix SUP-2504
Bugfix SUP-2515
Bugfix SUP-2511
Bugfix SUP-2539
Bugfix SUP-2451
Bugfix SUP-2451
Bugfix SUP-2514
Gentics Content.Node 5.19.65
Gentics Content.Node 5.19.64
Bugfix
Bugfix SUP-2495
Gentics Content.Node 5.19.63
Bugfix SUP-2201
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup. This fix just prevents certain subsequent errors when duplicates of a tag are already present in the page.
Gentics Content.Node 5.19.62
Bugfix SUP-2429
Bugfix SUP-2289
Bugfix SUP-2429
Bugfix SUP-2402
Gentics Content.Node 5.19.61
Documentation SUP-1298
Bugfix SUP-2365
Gentics Content.Node 5.19.60
Bugfix SUP-2354
Gentics Content.Node 5.19.59
Bugfix SUP-2269
Bugfix SUP-2353
Bugfix SUP-2303
Bugfix SUP-2177
Bugfix SUP-2338
Gentics Content.Node 5.19.58
Bugfix SUP-2194
Gentics Content.Node 5.19.57
Bugfix SUP-1804
Bugfix SUP-2029
Bugfix SUP-2222
Bugfix SUP-2184
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when duplicates of a tag are already present in the page. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2305
Gentics Content.Node 5.19.56
Gentics Content.Node 5.19.55
Gentics Content.Node 5.19.54
Gentics Content.Node 5.19.53
Bugfix SUP-2147
Bugfix SUP-2176
Bugfix SUP-1684
Gentics Content.Node 5.19.52
Bugfix SUP-1862
Also, request done via the REST API did not “touch” the systemsession by setting the time of the last access. This has also been fixed.
Gentics Content.Node 5.19.51
For this fix to work, also the implementation of the tagtype might be changed: The hardcoded type 10008 has to be replaced with $!{cms.tag.parts.file.target.ttype}. See the Guides:“http://www.gentics.com/Content.Node/guides/aloha_gcn_filelink_plugin.html” for details.
Bugfix SUP-2109
Bugfix SUP-2148
Bugfix SUP-1445
Bugfix SUP-1913
Bugfix SUP-1816
Note that having several occurrences of the same tag should be avoided. It is not supported in Aloha editor since it implies invalid HTML markup and can only be achieved by editing the contents of an editable directly (for example using the tag fill dialog). This fix just prevents subsequent errors when a tag is not converted to an aloha-block. The different occurrences of a tag are not necessarily synchronized.
Bugfix SUP-2107
Gentics Content.Node 5.19.50
Documentation SUP-2044
Bugfix SUP-2040
Bugfix SUP-2063
Bugfix SUP-2001
Bugfix SUP-2048
Bugfix SUP-2092
Bugfix SUP-1588
Bugfix SUP-2093
Gentics Content.Node 5.19.49
Bugfix SUP-1992
Bugfix SUP-1273
Bugfix SUP-2043Caused by: com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'source'.
The Gentics Infoportal also contains a new FAQ page “How can I enable support for pages with more than 16MB of content?”.
Bugfix SUP-2064
Bugfix SUP-2065quickrecursivetranslations is activated, the context menu entry Create translations was shown to all users, even if they had no permission to create a single language. Also in the dialog, the languages were not filtered by permissions. Both issues have been fixed now: # The menu entry Create translations will only be shown, if the user has permission on at least a single language # The dialog will only show languages the user may create.
Bugfix
Bugfix SUP-1193
Bugfix SUP-1957
Bugfix SUP-2032
/file/delete/{id} to delete a file/image/delete/{id} to delete an image
have been added.
Bugfix SUP-1981
Bugfix SUP-1558
This especially concerns the search settings for object lists: Before this change, if a user made a search e.g. in the page list of a specific folder, this setting was still there, even if the user logged out and in again. After this change, search settings will be cleared when the user logs out.
Bugfix SUP-887
createtimestampcreatorcreatoremaileditoreditoremailedittimestampprioritypublisherpublishermailpublishtimestamp
Bugfix SUP-2009
Bugfix SUP-2019
Gentics Content.Node 5.19.48
Bugfix SUP-1849
Bugfix SUP-1257
Bugfix SUP-529clearfix which could conflict with pages using bootstrap. The conflicting class names have been removed.
Bugfix SUP-1976
Gentics Content.Node 5.19.47
Documentation SUP-1915
Bugfix SUP-1927-SUP-903
Bugfix SUP-1749
Gentics Content.Node 5.19.46
Bugfix SUP-1721
Bugfix SUP-1880
Bugfix SUP-1872
Gentics Content.Node 5.19.45
Bugfix SUP-1783
Gentics Content.Node 5.19.44
Documentation SUP-1777
Bugfix SUP-1781
Bugfix SUP-1782contentfile_auto_offline feature would sometimes take files in master nodes offline which were still used in channels of a different master node. This has been fixed.
Bugfix SUP-1784
Bugfix SUP-889
Bugfix SUP-1677
Gentics Content.Node 5.19.43
Bugfix SUP-1520
Bugfix SUP-1771
Bugfix SUP-1520
Bugfix SUP-1697
Bugfix SUP-1487
Bugfix SUP-1600
Bugfix SUP-1519
Gentics Content.Node 5.19.42
Documentation SUP-1701
Bugfix SUP-1648
Bugfix SUP-1707always_localize was activated the dialogs for editing (object) properties of folders and pages sometimes would not open. This has been fixed.
Bugfix SUP-1728
Gentics Content.Node 5.19.41
Bugfix SUP-1415
Gentics Content.Node 5.19.40
Bugfix SUP-1589
Bugfix SUP-1486
Gentics Content.Node 5.19.39
Bugfix SUP-1337
Bugfix SUP-1399
Gentics Content.Node 5.19.38
Documentation SUP-1294
Bugfix SUP-1323
Bugfix SUP-1484
Bugfix SUP-1502
Bugfix SUP-861
Bugfix SUP-1469
Bugfix SUP-1516
Bugfix SUP-1491
Bugfix SUP-1467
Bugfix SUP-1399
Bugfix SUP-1485
Gentics Content.Node 5.19.37
Bugfix SUP-1459
Bugfix SUP-1336
Gentics Content.Node 5.19.36
Documentation SUP-1447
/CNPortletapp/rest/file/load/{id} should be added as path parameter, instead of a
query parameter, this has been corrected now.
Bugfix SUP-1399
Bugfix SUP-1342
Bugfix SUP-1399
Bugfix SUP-1441
Bugfix SUP-1419
Bugfix SUP-1339
Gentics Content.Node 5.19.35
Bugfix 1326
Bugfix SUP-1357
Bugfix SUP-1361
Gentics Content.Node 5.19.34
Gentics Content.Node 5.19.33
Documentation SUP-1325
Bugfix SUP-1303
Bugfix SUP-1307
Bugfix SUP-1235
Gentics Content.Node 5.19.32
Bugfix SUP-1266
Bugfix SUP-1068
Gentics Content.Node 5.19.31
Bugfix SUP-1196
Bugfix SUP-163
Instead of restarting Tomcat after the update, it is now stopped before updating the libraries and started again after the update is complete.
Bugfix SUP-641
Bugfix SUP-1124
0 instead of 10007 during the publish process. This has been fixed now.
Bugfix SUP-601
Bugfix SUP-601
Bugfix SUP-1126
Gentics Content.Node 5.19.30
Bugfix SUP-918
Bugfix SUP-1096
Bugfix SUP-1163
Bugfix SUP-1056
Bugfix SUP-918
Gentics Content.Node 5.19.29
Bugfix SUP-1078
Bugfix SUP-1003
Bugfix SUP-876
Bugfix SUP-754
Bugfix SUP-1010
Bugfix SUP-1086
Gentics Content.Node 5.19.28
Bugfix SUP-932
Bugfix SUP-694
Gentics Content.Node 5.19.27
Security
Gentics Content.Node 5.19.26
Bugfix SUP-979
for instance), Internet Explorer would serialize those tags incorrectly (e.g. like
). The text of links will now always be transformed to xhtml (like the Aloha Editor dom-to-xhtml plugin would do it).
Bugfix SUP-787
Bugfix SUP-806
Bugfix SUP-806
will now be generated in the language of the recipient, not the sender.
Bugfix SUP-806
Bugfix SUP-765
Bugfix SUP-1009
Bugfix SUP-985
Gentics Content.Node 5.19.25
Documentation SUP-990
Bugfix SUP-976
Gentics Content.Node 5.19.24
Bugfix SUP-941
Bugfix SUP-955
Bugfix SUP-977
Bugfix SUP-964
Bugfix SUP-974
Gentics Content.Node 5.19.23
Enhancement
Bugfix SUP-933
Bugfix SUP-930
Bugfix SUP-826
Bugfix SUP-869
Bugfix SUP-881
Gentics Content.Node 5.19.22
Bugfix SUP-896
Bugfix SUP-664
Bugfix SUP-819
Bugfix SUP-857
Bugfix SUP-635
Gentics Content.Node 5.19.21
Documentation SUP-821
Bugfix SUP-670
Bugfix SUP-506
Bugfix SUP-761
Bugfix SUP-781
Bugfix SUP-767
Bugfix SUP-802
Gentics Content.Node 5.19.20
Bugfix SUP-795
Gentics Content.Node 5.19.19
Bugfix SUP-774
Bugfix SUP-757
Bugfix SUP-560
Bugfix SUP-791
Bugfix SUP-792
Gentics Content.Node 5.19.18
Bugfix SUP-783
Gentics Content.Node 5.19.17
Bugfix SUP-773
Bugfix SUP-772
Bugfix SUP-768
Gentics Content.Node 5.19.16
Security SUP-34
Bugfix SUP-405
Bugfix SUP-746
The behaviour has been fixed now. Saving pages with multiple new links works as expected and each handler will get the html, which was returned by the previous handler, so that the modifications will be cumulated and the last return html will be taken as html of the rendered tag.
Bugfix SUP-762
Bugfix SUP-674
Bugfix SUP-672
Gentics Content.Node 5.19.15
Documentation SUP-665
Bugfix SUP-562
Bugfix SUP-629
Bugfix SUP-102
Bugfix SUP-341
Bugfix SUP-654
Bugfix SUP-679
Bugfix SUP-710
Bugfix SUP-562
Bugfix SUP-710
Bugfix SUP-686
Bugfix SUP-687
Bugfix SUP-101
Gentics Content.Node 5.19.14
Bugfix SUP-644
Bugfix SUP-507
Bugfix SUP-515
Bugfix SUP-610
Bugfix SUP-653
Bugfix SUP-668
Bugfix
Bugfix SUP-448
Bugfix SUP-656
Bugfix SUP-661
Bugfix SUP-430
Bugfix SUP-602
Gentics Content.Node 5.19.13
Enhancement SUP-519
Bugfix SUP-585
Bugfix SUP-556
Bugfix SUP-558
Bugfix SUP-522
Bugfix SUP-588
Bugfix SUP-586
Bugfix SUP-566
Bugfix SUP-569
Bugfix SUP-241
Bugfix SUP-605
Bugfix SUP-274
Gentics Content.Node 5.19.12
Documentation SUP-524
Bugfix SUP-552
Bugfix SUP-70
Gentics Content.Node 5.19.11
Security SUP-323
Security SUP-323
Bugfix SUP-387
Bugfix SUP-401
Bugfix SUP-530
Bugfix SUP-418
Bugfix SUP-479-SUP-488
Bugfix SUP-473
Bugfix SUP-187
Bugfix SUP-187
Bugfix SUP-434
Bugfix SUP-323
Bugfix SUP-480
Bugfix SUP-434
Bugfix SUP-187
Bugfix SUP-370
Bugfix SUP-456
Gentics Content.Node 5.19.9
Bugfix SUP-407
Bugfix SUP-309
they were incorrectly bound to a channel on the target system as well.
Bugfix SUP-450
Bugfix SUP-454
Bugfix SUP-306
Bugfix SUP-428
Gentics Content.Node 5.19.8
Bugfix SUP-361-SUP-364
Bugfix SUP-278
Bugfix SUP-310
Bugfix SUP-307
Bugfix SUP-226
Bugfix SUP-56
Gentics Content.Node 5.19.7
Bugfix SUP-285
Bugfix SUP-297
This i18n support task was redesigned in order to avoid such problems in the future.
Gentics Content.Node 5.19.6
Documentation SUP-170
Bugfix SUP-243
Bugfix SUP-46
Bugfix SUP-137
Bugfix SUP-269
Bugfix SUP-174
Gentics Content.Node 5.19.5
Bugfix SUP-42
Bugfix SUP-98
Gentics Content.Node 5.19.4
Bugfix SUP-59
Bugfix SUP-73
Bugfix SUP-164
Gentics Content.Node 5.19.3
This update includes some major changes to the backend database. The changes will be done during the first Tomcat startup after the update has been installed. Depending on the size of the backend database, configuration settings and overall system performance, this may last very long (up to several hours) during which the system will not be available to users. Errors during the migration process will be logged in the server log and will cause the Tomcat to not start properly See Bugfix RT58702 for further details.
Bugfix SUP-76
Bugfix SUP-78
Example:
Bugfix SUP-77
Bugfix RT58761
Bugfix RT58702
It is strongly recommended to make a backup of the system before doing the update.
The new generation and storage of global IDs fixes the following problems:
Bugfix SUP-77
Bugfix RT58697
Bugfix SUP-84
Bugfix SUP-88
Bugfix RT58739
Bugfix RT58618
Gentics Content.Node 5.19.2
Please note that is change is optional and can be omitted.
Documentation RT58712
Bugfix RT58735
Gentics Content.Node 5.19.1
Bugfix RT58617
Bugfix RT58672
Bugfix RT58713
Bugfix RT58651
Gentics Content.Node 5.19.0
The Aloha Editor textcolor plugin now allows you to set the background-color of text.
See the Aloha Editor Changelog for detailed information.
Feature RT58501
Feature RT58656
Enhancement RT58648
Enhancement
Enhancement KB2089
Enhancement KB2089
Enhancement
/folder/move/{id} for moving a single folder/folder/move for moving multiple folders/page/move/{id} for moving a single page/page/move for moving multiple pages/file/move/{id} for moving a single file/file/move for moving multiple files/image/move/{id} for moving a single image/image/move for moving multiple images
Enhancement KB2086
Bugfix RM14644
Gentics Content.Node 5.18.49
Documentation SUP-1701
Bugfix SUP-1648
Bugfix SUP-1707always_localize was activated the dialogs for editing (object) properties of folders and pages sometimes would not open. This has been fixed.
Bugfix SUP-1728
Gentics Content.Node 5.18.48
Bugfix SUP-1415
Gentics Content.Node 5.18.47
Bugfix SUP-1486
Gentics Content.Node 5.18.46
Bugfix SUP-1337
Bugfix SUP-1399
Gentics Content.Node 5.18.45
Documentation SUP-1294
Bugfix SUP-1323
Bugfix SUP-1502
Bugfix SUP-861
Bugfix SUP-1469
Bugfix SUP-1516
Bugfix SUP-1491
Bugfix SUP-1467
Bugfix SUP-1399
Bugfix SUP-1485
Gentics Content.Node 5.18.44
Bugfix SUP-1459
Bugfix SUP-1336
Gentics Content.Node 5.18.43
Documentation SUP-1447
/CNPortletapp/rest/file/load/{id} should be added as path parameter, instead of a
query parameter, this has been corrected now.
Bugfix SUP-1399
Bugfix SUP-1342
Bugfix SUP-1399
Bugfix SUP-1441
Gentics Content.Node 5.18.42
Bugfix SUP-1419
Bugfix SUP-1339
Gentics Content.Node 5.18.41
Bugfix 1326
Bugfix SUP-1361
Gentics Content.Node 5.18.40
Gentics Content.Node 5.18.39
Documentation SUP-1325
Bugfix SUP-1303
Bugfix SUP-1307
Bugfix SUP-1235
Gentics Content.Node 5.18.38
Bugfix SUP-1266
Bugfix SUP-1068
Gentics Content.Node 5.18.37
Bugfix SUP-163
Instead of restarting Tomcat after the update, it is now stopped before updating the libraries and started again after the update is complete.
Bugfix SUP-641
Bugfix SUP-1124
0 instead of 10007 during the publish process. This has been fixed now.
Bugfix SUP-601
Bugfix SUP-1126
Gentics Content.Node 5.18.36
Bugfix SUP-918
Bugfix SUP-1096
Bugfix SUP-1163
Bugfix SUP-1056
Bugfix SUP-918
Gentics Content.Node 5.18.35
Bugfix SUP-1078
Bugfix SUP-1003
Bugfix SUP-876
Bugfix SUP-1010
Bugfix SUP-1086
Gentics Content.Node 5.18.34
Bugfix SUP-932
Gentics Content.Node 5.18.33
Security
Gentics Content.Node 5.18.32
Bugfix SUP-979
for instance), Internet Explorer would serialize those tags incorrectly (e.g. like
). The text of links will now always be transformed to xhtml (like the Aloha Editor dom-to-xhtml plugin would do it).
Bugfix SUP-787
Bugfix SUP-806
Bugfix SUP-806
will now be generated in the language of the recipient, not the sender.
Bugfix SUP-806
Bugfix SUP-765
Bugfix SUP-985
Gentics Content.Node 5.18.31
Documentation SUP-990
Bugfix SUP-976
Gentics Content.Node 5.18.30
Bugfix SUP-941
Bugfix SUP-955
Bugfix SUP-977
Bugfix SUP-964
Bugfix SUP-974
Gentics Content.Node 5.18.29
Enhancement
Bugfix SUP-933
Bugfix SUP-930
Bugfix SUP-826
Bugfix SUP-869
Gentics Content.Node 5.18.28
Bugfix SUP-664
Bugfix SUP-819
Bugfix SUP-857
Bugfix SUP-635
Gentics Content.Node 5.18.27
Documentation SUP-821
Bugfix SUP-670
Bugfix SUP-506
Bugfix SUP-761
Bugfix SUP-781
Bugfix SUP-767
Bugfix SUP-802
Gentics Content.Node 5.18.26
Bugfix SUP-795
Bugfix SUP-774
Bugfix SUP-757
Bugfix SUP-783
Bugfix SUP-560
Bugfix SUP-772
Bugfix SUP-791
Bugfix SUP-768
Bugfix SUP-792
Gentics Content.Node 5.18.25
Security SUP-34
Bugfix SUP-405
Bugfix SUP-746
The behaviour has been fixed now. Saving pages with multiple new links works as expected and each handler will get the html, which was returned by the previous handler, so that the modifications will be cumulated and the last return html will be taken as html of the rendered tag.
Bugfix SUP-762
Bugfix SUP-674
Bugfix SUP-672
Gentics Content.Node 5.18.24
Documentation SUP-665
Bugfix SUP-629
Bugfix SUP-102
Bugfix SUP-341
Bugfix SUP-654
Bugfix SUP-679
Bugfix SUP-710
Bugfix SUP-710
Bugfix SUP-687
Bugfix SUP-101
Gentics Content.Node 5.18.23
Bugfix SUP-507
Bugfix SUP-515
Bugfix SUP-610
Bugfix
Bugfix SUP-448
Bugfix SUP-656
Bugfix SUP-430
Bugfix SUP-602
Gentics Content.Node 5.18.22
Enhancement SUP-519
Bugfix SUP-585
Bugfix SUP-558
Bugfix SUP-522
Bugfix SUP-566
Bugfix SUP-241
Bugfix SUP-605
Bugfix SUP-274
Gentics Content.Node 5.18.21
Documentation SUP-524
Gentics Content.Node 5.18.20
Security SUP-323
Security SUP-323
Bugfix SUP-387
Bugfix SUP-401
Bugfix SUP-418
Bugfix SUP-479-SUP-488
Bugfix SUP-473
Bugfix SUP-187
Bugfix SUP-187
Bugfix SUP-434
Bugfix SUP-323
Bugfix SUP-480
Bugfix SUP-434
Bugfix SUP-187
Bugfix SUP-370
Bugfix SUP-456
Gentics Content.Node 5.18.19
Bugfix SUP-407
Bugfix SUP-309
they were incorrectly bound to a channel on the target system as well.
Bugfix SUP-450
Bugfix SUP-454
Gentics Content.Node 5.18.18
Bugfix SUP-361-SUP-364
Bugfix SUP-278
Bugfix SUP-307
Bugfix SUP-226
Bugfix SUP-56
Gentics Content.Node 5.18.17
Bugfix SUP-285
Bugfix SUP-297
This i18n support task was redesigned in order to avoid such problems in the future.
Gentics Content.Node 5.18.16
Documentation SUP-170
Bugfix SUP-243
Bugfix SUP-46
Bugfix SUP-137
Bugfix SUP-174
Gentics Content.Node 5.18.15
Bugfix SUP-42
Gentics Content.Node 5.18.14
Bugfix SUP-59
Bugfix SUP-73
Bugfix SUP-164
Gentics Content.Node 5.18.13
Bugfix SUP-78
Example:
Bugfix RT58697
Bugfix SUP-88
Bugfix RT58739
Bugfix RT58618
Gentics Content.Node 5.18.12
Please note that is change is optional and can be omitted.
Documentation RT58712
Bugfix RT58735
Gentics Content.Node 5.18.11
Bugfix RT58617
Bugfix RT58672
Bugfix RT58713
Bugfix RT58651
Gentics Content.Node 5.18.10
Bugfix RT58676
Bugfix RT58544
Bugfix RT58663
Bugfix RT58592
Gentics Content.Node 5.18.9
Bugfix RT58709
Bugfix RM14656
Gentics Content.Node 5.18.8
Enhancement RT58648
Bugfix RT58687
Bugfix RT58610
Bugfix RT58685
Gentics Content.Node 5.18.7
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.
Documentation RT58656
Bugfix RT58620
Bugfix RT58659
Bugfix RT58601
Bugfix RT58657
Bugfix RT58538
Bugfix RT58556
Bugfix KB2086
It is important to note, that for the improved behaviour both the source and target system must be updated.
Gentics Content.Node 5.18.6
Bugfix RT58613
Bugfix RT58613
Gentics Content.Node 5.18.5
Security
The POODLE attack (PaddingOracleOnDowngradedLegacyEncryption) allows to steal “secure” HTTP cookies when SSL 3.0 is being used. We strongly recommend disabling SSL 3.0 support in your apache webserver configuration and if needed to update the openssl library once a fix for this issue has been released.
Bugfix RT58589
Bugfix RT58589
Bugfix RT58539
Bugfix RT58566
Bugfix RT58531
Bugfix RT58561
For these fixes, it is important that both the source and target system are update to the newest version of GCN, before doing the export and import.
imported object, which could lead to “Internal errors“ in subsequent imports.
would not be detected again, which could lead to unwanted overwriting of the local object.
Bugfix RT58564
Bugfix RT58574
Bugfix RT58537
Bugfix RT58596
Bugfix RT58544
Bugfix RT58560
Bugfix RT58557
Bugfix RT58572
Bugfix RT58599
Bugfix RT58570
Bugfix RT58599
Bugfix RT58573
The ‘sanitize names‘ feature now allows the configuration of the standard replacement character. Also the list of allowed characters can be extended. See: Sanitize names
Bugfix RT58067
Gentics Content.Node 5.18.4
Documentation RT58520
Bugfix RT58517
Bugfix RT58516
Bugfix RT58526
Bugfix RT58523
Bugfix RT58528
Bugfix RT58521
Bugfix RT58525
Bugfix RT58509
Gentics Content.Node 5.18.3
text of the tagtype must be inline editable. The documentation has been updated. If this plugin is used, the tagtype implementation must be changed accordingly.
Bugfix RT58503
Bugfix KB1975
Bugfix RT58492
Bugfix RT58459
Gentics Content.Node 5.18.2
Bugfix RT58489
Bugfix RT58412
Bugfix RT58490Text, Text/HTML or Text/HTML (long) (which will replace newlines to br-Tags while rendering) would add superfluous br-Tags every time a page is edited with Aloha Editor. Changing the part to HTML would not change the stored content and newlines stored in the contents would no longer be transformed into br-Tags.
For this reason, the behavior of saving contents into such parts has been changed to strip all contained newlines. In this way, the editables can still be used with Aloha Editor without any further migration necessary.
It is mandatory to activate the feature aloha_annotate_editables for this to work. See the Aloha Editor Migration Guide for details.
Bugfix RT58484
Bugfix RT58430
Gentics Content.Node 5.18.1
Bugfix RT58467
Bugfix RT58451
Bugfix RT58263
Bugfix RT58456
Bugfix RT58456
Bugfix RT58443
Bugfix RT58447
Bugfix RT58334
Bugfix RT58418
Gentics Content.Node 5.18.0
Security KB1662
Feature KB2115
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement RT58185
Enhancement RT58185
Bugfix KB1662
Bugfix RM14229
Gentics Content.Node 5.17.46
Bugfix SUP-979
for instance), Internet Explorer would serialize those tags incorrectly (e.g. like
). The text of links will now always be transformed to xhtml (like the Aloha Editor dom-to-xhtml plugin would do it).
Bugfix SUP-787
Bugfix SUP-806
Bugfix SUP-806
will now be generated in the language of the recipient, not the sender.
Bugfix SUP-806
Bugfix SUP-765
Bugfix SUP-985
Gentics Content.Node 5.17.45
Gentics Content.Node 5.17.44
Bugfix SUP-941
Bugfix SUP-955
Bugfix SUP-977
Bugfix SUP-974
Gentics Content.Node 5.17.43
Enhancement
Bugfix SUP-933
Bugfix SUP-930
Bugfix SUP-826
Bugfix SUP-869
Gentics Content.Node 5.17.42
Bugfix SUP-664
Bugfix SUP-819
Bugfix SUP-857
Bugfix SUP-635
Gentics Content.Node 5.17.41
Documentation SUP-821
Bugfix SUP-670
Bugfix SUP-506
Bugfix SUP-761
Bugfix SUP-781
Bugfix SUP-767
Bugfix SUP-802
Gentics Content.Node 5.17.40
Bugfix SUP-795
Bugfix SUP-774
Bugfix SUP-757
Bugfix SUP-783
Bugfix SUP-560
Bugfix SUP-772
Bugfix SUP-791
Bugfix SUP-768
Bugfix SUP-792
Gentics Content.Node 5.17.39
Security SUP-34
Bugfix SUP-405
Bugfix SUP-746
The behaviour has been fixed now. Saving pages with multiple new links works as expected and each handler will get the html, which was returned by the previous handler, so that the modifications will be cumulated and the last return html will be taken as html of the rendered tag.
Bugfix SUP-762
Bugfix SUP-674
Bugfix SUP-672
Gentics Content.Node 5.17.38
Documentation SUP-665
Bugfix SUP-629
Bugfix SUP-102
Bugfix SUP-341
Bugfix SUP-679
Bugfix SUP-687
Bugfix SUP-101
Gentics Content.Node 5.17.37
Bugfix SUP-507
Bugfix SUP-515
Bugfix SUP-610
Bugfix
Bugfix SUP-448
Bugfix SUP-656
Bugfix SUP-430
Bugfix SUP-602
Gentics Content.Node 5.17.36
Enhancement SUP-519
Bugfix SUP-585
Bugfix SUP-558
Bugfix SUP-522
Bugfix SUP-566
Bugfix SUP-605
Bugfix SUP-274
Gentics Content.Node 5.17.35
Documentation SUP-524
Bugfix SUP-241
Gentics Content.Node 5.17.34
Security SUP-323
Security SUP-323
Bugfix SUP-387
Bugfix SUP-401
Bugfix SUP-418
Bugfix SUP-479-SUP-488
Bugfix SUP-473
Bugfix SUP-187
Bugfix SUP-187
Bugfix SUP-434
Bugfix SUP-323
Bugfix SUP-434
Bugfix SUP-187
Bugfix SUP-370
Bugfix SUP-456
Gentics Content.Node 5.17.33
Bugfix SUP-407
Bugfix SUP-309
they were incorrectly bound to a channel on the target system as well.
Bugfix SUP-450
Gentics Content.Node 5.17.32
Bugfix SUP-361-SUP-364
Bugfix SUP-278
Bugfix SUP-307
Bugfix SUP-226
Bugfix SUP-56
Gentics Content.Node 5.17.31
Bugfix SUP-285
Bugfix SUP-297
This i18n support task was redesigned in order to avoid such problems in the future.
Gentics Content.Node 5.17.30
Documentation SUP-170
Bugfix SUP-243
Bugfix SUP-46
Bugfix SUP-137
Bugfix SUP-174
Gentics Content.Node 5.17.29
Bugfix SUP-42
Gentics Content.Node 5.17.28
Bugfix SUP-59
Bugfix SUP-73
Bugfix SUP-164
Gentics Content.Node 5.17.27
Bugfix SUP-78
Example:
Bugfix RT58697
Bugfix SUP-88
Bugfix RT58739
Bugfix RT58618
Gentics Content.Node 5.17.26
Please note that is change is optional and can be omitted.
Documentation RT58712
Bugfix RT58735
Gentics Content.Node 5.17.25
Bugfix RT58617
Bugfix RT58672
Bugfix RT58713
Bugfix RT58651
Gentics Content.Node 5.17.24
Bugfix RT58676
Bugfix RT58544
Bugfix RT58663
Bugfix RT58592
Gentics Content.Node 5.17.23
Enhancement RT58648
Bugfix RT58687
Bugfix RT58610
Bugfix RT58685
Gentics Content.Node 5.17.22
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.
Documentation RT58656
Bugfix RT58620
Bugfix RT58659
Bugfix RT58601
Bugfix RT58657
Bugfix RT58538
Bugfix RT58556
Bugfix KB2086
It is important to note, that for the improved behaviour both the source and target system must be updated.
Gentics Content.Node 5.17.21
Bugfix RT58613
Bugfix RT58613
Gentics Content.Node 5.17.20
Bugfix RT58589
Bugfix RT58589
Bugfix RT58561
For these fixes, it is important that both the source and target system are update to the newest version of GCN, before doing the export and import.
imported object, which could lead to “Internal errors“ in subsequent imports.
would not be detected again, which could lead to unwanted overwriting of the local object.
Bugfix RT58574
Bugfix RT58596
Bugfix RT58572
Bugfix RT58599
Bugfix RT58570
Bugfix RT58599
Gentics Content.Node 5.17.19
Bugfix RT58566
Bugfix RT58564
Bugfix RT58560
Bugfix RT58557
Bugfix RT58573
The ‘sanitize names‘ feature now allows the configuration of the standard replacement character. Also the list of allowed characters can be extended. See: Sanitize names
Bugfix RT58067
Gentics Content.Node 5.17.18
Security
The POODLE attack (PaddingOracleOnDowngradedLegacyEncryption) allows to steal “secure” HTTP cookies when SSL 3.0 is being used. We strongly recommend disabling SSL 3.0 support in your apache webserver configuration and if needed to update the openssl library once a fix for this issue has been released.
Bugfix RT58539
Bugfix RT58531
Bugfix RT58537
Bugfix RT58544
Gentics Content.Node 5.17.17
Documentation RT58520
Bugfix RT58517
Bugfix RT58516
Bugfix RT58526
Bugfix RT58523
Bugfix RT58528
Bugfix RT58521
Bugfix RT58525
Bugfix RT58509
Gentics Content.Node 5.17.16
text of the tagtype must be inline editable. The documentation has been updated. If this plugin is used, the tagtype implementation must be changed accordingly.
Bugfix RT58503
Bugfix RT58492
Bugfix RT58459
Gentics Content.Node 5.17.15
Bugfix RT58489
Bugfix RT58412
Bugfix RT58490Text, Text/HTML or Text/HTML (long) (which will replace newlines to br-Tags while rendering) would add superfluous br-Tags every time a page is edited with Aloha Editor. Changing the part to HTML would not change the stored content and newlines stored in the contents would no longer be transformed into br-Tags.
For this reason, the behavior of saving contents into such parts has been changed to strip all contained newlines. In this way, the editables can still be used with Aloha Editor without any further migration necessary.
It is mandatory to activate the feature aloha_annotate_editables for this to work. See the Aloha Editor Migration Guide for details.
Bugfix RT58430
Gentics Content.Node 5.17.14
Bugfix RT58467
Bugfix RT58451
Bugfix RT58263
Bugfix RT58456
Bugfix RT58456
Bugfix RT58443
Bugfix RT58447
Bugfix RT58334
Bugfix RT58418
Bugfix RM14229
Gentics Content.Node 5.17.13
Bugfix RM13889
Bugfix RT58422
Bugfix RT58437
Bugfix RT58139
Bugfix RT58256
Bugfix RT58312
Bugfix RT58408
Bugfix RT58434
Bugfix RT58388
Bugfix RT58424
Bugfix RT58436-RT58436
Bugfix RT58448
Gentics Content.Node 5.17.12
Bugfix
Bugfix RT58441
Gentics Content.Node 5.17.11
Bugfix RT58386
Bugfix RT58384
Bugfix RT58432
Bugfix RT58371
Bugfix RT58302
Gentics Content.Node 5.17.10
Bugfix RT58383
Bugfix RM14192
Bugfix RT58403
Bugfix RT58305
Gentics Content.Node 5.17.9
Bugfix RT58362
Gentics Content.Node 5.17.8
Documentation RT58355
Bugfix RT54802
Bugfix
Bugfix RT58327
Bugfix RT58365
Please take a look at our Memory & Performance FAQ for more information.
Gentics Content.Node 5.17.7
Bugfix RT58321
Bugfix RT58339
Bugfix RT58343
Bugfix RT58211
Bugfix RT58298
Bugfix RT58346
Gentics Content.Node 5.17.6
Documentation RT58295
Bugfix RT58278
Bugfix RT58243
Bugfix RT58324
Bugfix RT58320
Bugfix RT58285 datasources that belong to a specific tag that has a part of type "Datasource" during Import/Export has been fixed. They will no longer be treated as individual objects, but as tag content. The changes in detail are:
Bugfix RT58319
Bugfix RT58328
Gentics Content.Node 5.17.5
Documentation RT58220
Bugfix RT58268
Bugfix RT58243
Bugfix RT58207
Bugfix RT58260
Bugfix RT58296
Bugfix RT58279
Bugfix RT58271
Bugfix RT58250
Gentics Content.Node 5.17.4
Security RT58241
Enhancement RT58235
Bugfix RT58264
Bugfix KB1726
Bugfix RT58216
Bugfix RT58246
Bugfix RT58275
Bugfix RT58131
Gentics Content.Node 5.17.3
Bugfix RT58217
Bugfix RT58213
Gentics Content.Node 5.17.2
Bugfix RT58192
Bugfix RT58227
Bugfix RT58209
Gentics Content.Node 5.17.1
Bugfix RT58179
Bugfix RT58204
Bugfix RT58196
Bugfix RT58202
Bugfix RT58156
Bugfix RT58159
Bugfix RT58198
Bugfix RT58187
Gentics Content.Node 5.17.0
Aloha Editor now allows for central configuration of allowed nodes. This reduces configuration overhead as all plugins will adhere these settings. The format plugin now supports hierarchical headlines. New documentation for creating a video block has been added. Aloha Editor is now capable of automatically purging empty paragraphs and multiple breaks.
See the Aloha Editor Changelog for detailed information.
Please note that the JDK 1.7 runtime is required since the hotfix versions 5.14.22 and 5.15.9
The following shared libraries have been updated:
select c.id as construct_id, c.keyword as construct_keyword, p.keyword as part_keyword from value v left join part p on p.id = v.part_id left join construct c on c.id = p.construct_id where v.value_text like '%$cms.imps.date%';
$FEATURE[“disableIE7StandardsMode”] = true;
Read the feature documentation for more information.
Please note that Internet Explorer 10 has known rendering issues (white pages) with frames and should therefore not be used.
Feature KB1481
Feature KB1391
The new REST API Method getExternalLinks will return all external links found in pages inside a given folder. The FolderResource documentation contains more information on this topic.
Enhancement
Enhancement
This slightly increases the memory consumption, but reduces the number of necessary database queries during the publish process
Enhancement
Enhancement
Enhancement RM13252
Enhancement
Enhancement
Enhancement RT57896
Bugfix RT58117
Bugfix KB1568
Bugfix RT57383
Bugfix
Bugfix RT58165
Bugfix RT57729
Bugfix RT58146
Bugfix RT58089
Bugfix RT58176
Gentics Content.Node 5.16.16
Bugfix RT58217
Bugfix RT58213
Gentics Content.Node 5.16.15
Bugfix RT58192
Bugfix RT58227
Bugfix RT58209
Gentics Content.Node 5.16.14
Bugfix RT58204
Bugfix RT58202
Bugfix RT58156
Bugfix RT58198
Gentics Content.Node 5.16.13
Bugfix RT58179
Bugfix RT58159
Bugfix RT58187
Gentics Content.Node 5.16.12
Bugfix RT58117
Bugfix RT57383
Bugfix
Bugfix RT58165
Bugfix RT57729
Bugfix RT58146
Bugfix RT58089
Bugfix RT58176
Gentics Content.Node 5.16.11
Bugfix RT57825
Bugfix RT58148
Bugfix RT58001
Bugfix RT58124
Bugfix RT58084
Bugfix RT58124
Bugfix RT58054
Bugfix RT55699
Bugfix RT58132
Gentics Content.Node 5.16.10
Bugfix RT58063
Bugfix RT58086
Bugfix RT57949
Gentics Content.Node 5.16.9
Bugfix RT57635
Bugfix RT57635
Bugfix RT56639
Bugfix RT58140
Bugfix RT58053
Bugfix RT58104
Bugfix RT58072
Bugfix RT58095
Bugfix RT57635
Gentics Content.Node 5.16.8
Bugfix RT58049
Bugfix RT58073
When the jpeg resizing quality was set in the node configuration, it was ignored when cropping an image. This error has been fixed.
Bugfix RT58016
Gentics Content.Node 5.16.7
Bugfix RT57997
Gentics Content.Node 5.16.6
Enhancement RT58071
Bugfix RT57999
Bugfix RT578055
A new request parameter “nodeId” has been added to the RestAPI preview method. There was an error when calling the GCN JS API function ‘preview‘ in a local folder of a channel. This error has been fixed.
Bugfix RT58030
Bugfix RT58067
Bugfix RT58036
Before the fix, all channel nodes were displayed in the Link Browser. Now only the channel nodes derived from the master node of the actual page are displayed in the navigation tree of the link Browser.
Gentics Content.Node 5.16.5
Bugfix RT58031
When creating a new part type and selecting ‘Web adresse‘ as regular expression only ‘http‘ URLs were accepted. With this fix, ‘https‘ URLs are also accepted.
Bugfix RT58034
Bugfix RT57902
Bugfix RT58007
Gentics Content.Node 5.16.4
The libSSL version 0.9.8 which was included in older Gentics Content.Node installation packages does not contain the Transport Layer Security (TLS) heartbleed extension. It is therefore not affected by the Heartbleed security bug. The latest Gentics Content.Node installation package (5.16.x) does not contain any thirdparty binary libraries.
Bugfix RT57765
Bugfix RT57923
Bugfix RT57976
Bugfix RT57986
Bugfix RT57893
Bugfix RT57985
Gentics Content.Node 5.16.3
Bugfix RT57922
Bugfix RT57977
The Javascript error that was thrown: “TypeError: f.f_filename is undefined”.
Gentics Content.Node 5.16.2
Bugfix RT57984
Bugfix RT57796
Bugfix RT54176
Bugfix RT57874
Bugfix
Gentics Content.Node 5.16.1
Security RT57919
Enhancement
Enhancement RT57948
Documentation RT57920
Bugfix RT57803
Bugfix RT57856
Bugfix RT57918
Bugfix RT57915
Bugfix RT57966
Bugfix RT57950
Bugfix RT57940
Bugfix RT57919
Bugfix RT57820
If the text representing the number of users inline was like ‘999 Benutzer online‘, the text was broken in two lines ‘14 Benutzer‘ and ‘online‘. Just by making bigger the area, the text stays in one line.
Bugfix RT57892
Bugfix RT57916
Bugfix RT57957
Bugfix RT57950
Bugfix RT57955 files that exist in a folder but are bound to a channel, in which the file cannot be visible, because the folder is not visible in that channel could cause a NullPointerException during the publish process while checking online files. This has been fixed now, such files will be treated as “non existent” in the folder‘s node and will be taken offline.
Bugfix RT57921
Gentics Content.Node 5.16.0
When publishing into multichannelling aware content repositories, it is important to use the recent version of Gentics Portal.Node (>= 4.5.0) or the Gentics Content.Connector for reading from this content repository, so that optimized attributes will be read correctly.
The optional changes include:
Please read the configuration and migration guide which is applicable for the latest distributions of SUSE Enterprise Linux, Redhat Enterprise Linux and Debian Linux. Do the package migration after updating Gentics Content.Node to 5.14.* with the Autoupdate.
This optional change will not remove any files automatically.
Feature kb1064
Feature KB1211
Enhancement RT57008
Enhancement RT55266
Enhancement
Enhancement
Enhancement KB1094
See the Gentics Content.Node Guides for details on multithreaded publishing.
Enhancement
Enhancement KB1067
Enhancement
Enhancement KB1276
Enhancement KB1212
Enhancement
Enhancement KB1210
Enhancement KB1094
Enhancement
Enhancement RM12019
Enhancement KB1094
Enhancement KB1210
Bugfix KB1064
White spaces were replaced by underscores (‘_‘) in filenames. With this fix, sanitizing allows white spaces for filenames.
www.gentics.com/Content.Node/guides/feature_sanitize_name.html
Bugfix RT57711
Gentics Content.Node 5.15.30
Bugfix RT58217
Bugfix RT58213
Gentics Content.Node 5.15.29
Bugfix RT58192
Bugfix RT58227
Bugfix RT58209
Gentics Content.Node 5.15.28
Bugfix RT58204
Bugfix RT58156
Bugfix RT58198
Gentics Content.Node 5.15.27
Bugfix RT58179
Bugfix RT58159
Bugfix RT58187
Gentics Content.Node 5.15.26
Bugfix RT58117
Bugfix RT57383
Bugfix
Bugfix RT58165
Bugfix RT57729
Bugfix RT58146
Bugfix RT58089
Bugfix RT58176
Gentics Content.Node 5.15.25
Bugfix RT57825
Bugfix RT58148
Bugfix RT58001
Bugfix RT58124
Bugfix RT58084
Bugfix RT58124
Bugfix RT55699
Bugfix RT58132
Gentics Content.Node 5.15.24
Bugfix RT58063
Bugfix RT58086
Bugfix RT57949
Gentics Content.Node 5.15.23
Bugfix RT57635
Bugfix RT57635
Bugfix RT56639
Bugfix RT58140
Bugfix RT58104
Bugfix RT58072
Bugfix RT58095
Bugfix RT57635
Gentics Content.Node 5.15.22
Bugfix RT58049
Bugfix RT58073
When the jpeg resizing quality was set in the node configuration, it was ignored when cropping an image. This error has been fixed.
Bugfix RT58016
Gentics Content.Node 5.15.21
Bugfix RT57997
Gentics Content.Node 5.15.20
Enhancement RT58071
Bugfix RT57999
Bugfix RT578055
A new request parameter “nodeId” has been added to the RestAPI preview method. There was an error when calling the GCN JS API function ‘preview‘ in a local folder of a channel. This error has been fixed.
Bugfix RT58030
Bugfix RT58067
Bugfix RT58036
Before the fix, all channel nodes were displayed in the Link Browser. Now only the channel nodes derived from the master node of the actual page are displayed in the navigation tree of the link Browser.
Gentics Content.Node 5.15.19
Bugfix RT58031
When creating a new part type and selecting ‘Web adresse‘ as regular expression only ‘http‘ URLs were accepted. With this fix, ‘https‘ URLs are also accepted.
Bugfix RT58034
Bugfix RT57902
Bugfix RT58007
Gentics Content.Node 5.15.18
The libSSL version 0.9.8 which was included in older Gentics Content.Node installation packages does not contain the Transport Layer Security (TLS) heartbleed extension. It is therefore not affected by the Heartbleed security bug. The latest Gentics Content.Node installation package (5.16.x) does not contain any thirdparty binary libraries.
Bugfix RT57765
Bugfix RT57923
Bugfix RT57976
Bugfix RT57986
Bugfix RT57893
Bugfix RT57985
Gentics Content.Node 5.15.17
Bugfix RT57922
Bugfix RT57977
The Javascript error that was thrown: “TypeError: f.f_filename is undefined”.
Gentics Content.Node 5.15.16
Bugfix RT57984
Bugfix RT57796
Bugfix RT54176
Bugfix RT57874
Bugfix
Gentics Content.Node 5.15.15
Security RT57919
Enhancement
Documentation RT57920
Bugfix RT57803
Bugfix RT57856
Bugfix RT57918
Bugfix RT57915
Bugfix RT57966
Bugfix RT57940
Bugfix RT57919
Bugfix RT57820
If the text representing the number of users inline was like ‘999 Benutzer online‘, the text was broken in two lines ‘14 Benutzer‘ and ‘online‘. Just by making bigger the area, the text stays in one line.
Bugfix RT57892
Bugfix RT57916
Bugfix RT57957
Bugfix RT57950
Bugfix RT57955 files that exist in a folder but are bound to a channel, in which the file cannot be visible, because the folder is not visible in that channel could cause a NullPointerException during the publish process while checking online files. This has been fixed now, such files will be treated as “non existent” in the folder‘s node and will be taken offline.
Bugfix RT57921
Gentics Content.Node 5.15.14
Enhancement RT56970
Bugfix RT57745
Bugfix RT57849
Bugfix RM13359
Bugfix RT57819-RT57627
Gentics Content.Node 5.15.13
Bugfix RT57828
File properties:
Bugfix RT57888
Bugfix RT57815
Bugfix RT57610
Bugfix RT57663
Bugfix RT57793
Bugfix RT57867
Gentics Content.Node 5.15.12
Bugfix RT57811
Bugfix RT57808
Bugfix RT57787
Gentics Content.Node 5.15.11
Bugfix RT57494
Bugfix RT57764
Bugfix RT57774
Bugfix RT57813
Gentics Content.Node 5.15.10
Bugfix RT57712
Bugfix RT51701
Bugfix RT57712
Bugfix RT57750
This fix contains database changes that might take some time (~10min for 12M mappedglobalids) and might fail if your database is already corrupted (duplicate GlobalIDs or NULL GlobalIDs).
In order to prevent data corruption, the webapp will refuse to start if a modification to mappedglobalidsequence is detected (See error message in catalina.out).
Bugfix RT57710
Bugfix RT57769
Bugfix RT57633
Gentics Content.Node 5.15.9
Please update the used Java version to Server JRE 1.7.0_51-b13 64 bit Download the Server JRE package and extract it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the tomcat once you finished this step using the /Node/bin/nodectl script.
Enhancement rt57204
Bugfix RT57717
Bugfix RT57602
Bugfix RT57688
Bugfix RT57500
Gentics Content.Node 5.15.8
Enhancement RT57609
Bugfix RT57627
Bugfix RT57658
Bugfix RT56361
Bugfix RT57565
Bugfix RT57684
Bugfix RT57635
Bugfix RT57708
Bugfix RT57697
Bugfix RT57658
Gentics Content.Node 5.15.7
Bugfix RT57568
Bugfix RT56904
Bugfix RT57670
Gentics Content.Node 5.15.6
Enhancement RT57646
Bugfix RT57190
Bugfix RT57462
Bugfix RT57669
Bugfix RT57644
Bugfix RT57650
Bugfix RT57588
Bugfix RT57599
Gentics Content.Node 5.15.5
Bugfix RT57607
Bugfix RT56622
Bugfix RT57606
Bugfix RT56058
Bugfix RT57605
Bugfix RT57624
Gentics Content.Node 5.15.4
Enhancement
Enhancement
Bugfix RT56835
Bugfix RT57297
Bugfix RT57590
Bugfix RT53165
Bugfix RT56031
Bugfix RT57556
Bugfix RT57550
Bugfix RT57212
Bugfix RT57596
Gentics Content.Node 5.15.3
Security RT54513
Security RT54513
Security RT54513
Bugfix RT57434
Bugfix RT57499
Bugfix RT57387
Bugfix RT57495
Bugfix RT57386
Gentics Content.Node 5.15.2
Enhancement
Bugfix
Bugfix RT57435
Bugfix RT57460
Bugfix RT55037
Bugfix
Bugfix RT57259
Bugfix RT57368
Bugfix RT56720
Bugfix RT57371
Bugfix RT57329
Gentics Content.Node 5.15.1
Bugfix RT57442
Gentics Content.Node 5.15.0
More information about restricting user-group assignments to nodes can be found in the Gentics Content.Node Guides
Enhancement RT57304
Enhancement especially to build the folder tree has been improved.
Enhancement RT57003
Node:
Enhancement
Enhancement RT56173
Enhancement
More information about restricting user-group assignments to nodes can be found in the Gentics Content.Node Guides
Enhancement RM10457
Gentics Content.Node 5.14.46
Bugfix RT58278
Bugfix RT58243
Bugfix RT58324
Bugfix RT58285 datasources that belong to a specific tag that has a part of type "Datasource" during Import/Export has been fixed. They will no longer be treated as individual objects, but as tag content. The changes in detail are:
Bugfix RT58328
Gentics Content.Node 5.14.45
Documentation RT58220
Bugfix RT58243
Bugfix RT58260
Bugfix RT58296
Bugfix RT58279
Bugfix RT58271
Bugfix RT58250
Gentics Content.Node 5.14.44
Security RT58241
Bugfix KB1726
Bugfix RT58216
Bugfix RT58275
Bugfix RT58131
Gentics Content.Node 5.14.43
Bugfix RT58213
Gentics Content.Node 5.14.42
Bugfix RT58227
Bugfix RT58209
Gentics Content.Node 5.14.41
Bugfix RT58204
Bugfix RT58156
Bugfix RT58198
Gentics Content.Node 5.14.40
Bugfix RT58179
Bugfix RT58187
Gentics Content.Node 5.14.39
Bugfix RT58117
Bugfix RT57383
Bugfix
Bugfix RT58165
Bugfix RT57729
Bugfix RT58146
Bugfix RT58089
Bugfix RT58176
Gentics Content.Node 5.14.38
Bugfix RT57825
Bugfix RT58148
Bugfix RT58001
Bugfix RT58124
Bugfix RT58084
Bugfix RT58124
Bugfix RT55699
Bugfix RT58132
Gentics Content.Node 5.14.37
Bugfix RT58063
Bugfix RT58086
Bugfix RT57949
Gentics Content.Node 5.14.36
Bugfix RT57635
Bugfix RT57635
Bugfix RT56639
Bugfix RT58140
Bugfix RT58072
Bugfix RT58095
Gentics Content.Node 5.14.35
Bugfix RT58049
Bugfix RT58073
When the jpeg resizing quality was set in the node configuration, it was ignored when cropping an image. This error has been fixed.
Bugfix RT58016
Gentics Content.Node 5.14.34
Bugfix RT57997
Gentics Content.Node 5.14.33
Enhancement RT58071
Bugfix RT57999
Bugfix RT578055
A new request parameter “nodeId” has been added to the RestAPI preview method. There was an error when calling the GCN JS API function ‘preview‘ in a local folder of a channel. This error has been fixed.
Bugfix RT58030
Bugfix RT58067
Bugfix RT58036
Before the fix, all channel nodes were displayed in the Link Browser. Now only the channel nodes derived from the master node of the actual page are displayed in the navigation tree of the link Browser.
Gentics Content.Node 5.14.32
Bugfix RT58031
When creating a new part type and selecting ‘Web adresse‘ as regular expression only ‘http‘ URLs were accepted. With this fix, ‘https‘ URLs are also accepted.
Bugfix RT58034
Bugfix RT57902
Bugfix RT58007
Gentics Content.Node 5.14.31
The libSSL version 0.9.8 which was included in older Gentics Content.Node installation packages does not contain the Transport Layer Security (TLS) heartbleed extension. It is therefore not affected by the Heartbleed security bug. The latest Gentics Content.Node installation package (5.16.x) does not contain any thirdparty binary libraries.
Bugfix RT57923
Bugfix RT57976
Bugfix RT57986
Bugfix RT57893
Bugfix RT57985
Gentics Content.Node 5.14.30
Bugfix RT57922
Bugfix RT57977
The Javascript error that was thrown: “TypeError: f.f_filename is undefined”.
Gentics Content.Node 5.14.29
Bugfix RT57984
Bugfix RT57796
Bugfix RT54176
Bugfix RT57874
Bugfix
Gentics Content.Node 5.14.28
Security RT57919
Enhancement
Documentation RT57920
Bugfix RT57803
Bugfix RT57856
Bugfix RT57918
Bugfix RT57915
Bugfix RT57966
Bugfix RT57919
Bugfix RT57892
Bugfix RT57916
Bugfix RT57957
Bugfix RT57950
Bugfix RT57955 files that exist in a folder but are bound to a channel, in which the file cannot be visible, because the folder is not visible in that channel could cause a NullPointerException during the publish process while checking online files. This has been fixed now, such files will be treated as “non existent” in the folder‘s node and will be taken offline.
Bugfix RT57921
Gentics Content.Node 5.14.27
Enhancement RT56970
Bugfix RT57745
Bugfix RT57849
Bugfix RT57819-RT57627
Gentics Content.Node 5.14.26
Bugfix RT57828
File properties:
Bugfix RT57888
Bugfix RT57815
Bugfix RT57610
Bugfix RT57663
Bugfix RT57793
Bugfix RT57867
Gentics Content.Node 5.14.25
Bugfix RT57808
Bugfix RT57787
Gentics Content.Node 5.14.24
Bugfix RT57764
Bugfix RT57774
Bugfix RT57813
Gentics Content.Node 5.14.23
Bugfix RT57712
Bugfix RT51701
Bugfix RT57712
Bugfix RT57750
This fix contains database changes that might take some time (~10min for 12M mappedglobalids) and might fail if your database is already corrupted (duplicate GlobalIDs or NULL GlobalIDs).
In order to prevent data corruption, the webapp will refuse to start if a modification to mappedglobalidsequence is detected (See error message in catalina.out).
Bugfix RT57710
Bugfix RT57769
Bugfix RT57633
Gentics Content.Node 5.14.22
Please update the used Java version to Server JRE 1.7.0_51-b13 64 bit Download the Server JRE package and extract it in e.g. /Node/. Update the /Node/java symlink to point to the new ‘Server JRE‘ directory. Restart the tomcat once you finished this step using the /Node/bin/nodectl script.
Enhancement rt57204
Bugfix RT57717
Bugfix RT57688
Bugfix RT57500
Gentics Content.Node 5.14.21
Enhancement RT57609
Bugfix RT57627
Bugfix RT57658
Bugfix RT56361
Bugfix RT57565
Bugfix RT57684
Bugfix RT57635
Bugfix RT57708
Bugfix RT57697
Bugfix RT57658
Gentics Content.Node 5.14.20
Bugfix RT57568
Bugfix RT56904
Bugfix RT57670
Gentics Content.Node 5.14.19
Enhancement RT57646
Bugfix RT57190
Bugfix RT57462
Bugfix RT57644
Bugfix RT57650
Bugfix RT57588
Bugfix RT57599
Gentics Content.Node 5.14.18
Bugfix RT57607
Bugfix RT56622
Bugfix RT57606
Bugfix RT56058
Bugfix RT57605
Bugfix RT57624
Gentics Content.Node 5.14.17
Bugfix RT56835
Bugfix RT57297
Bugfix RT57590
Bugfix RT53165
Bugfix RT56031
Bugfix RT57556
Bugfix RT57550
Bugfix RT57212
Bugfix RT57596
Gentics Content.Node 5.14.16
Security RT54513
Security RT54513
Security RT54513
Bugfix RT57434
Bugfix RT57499
Bugfix RT57387
Bugfix RT57495
Bugfix RT57386
Gentics Content.Node 5.14.15
Bugfix
Bugfix RT57435
Bugfix RT57460
Bugfix RT55037
Bugfix RT57259
Bugfix RT57368
Bugfix RT56720
Bugfix RT57371
Bugfix RT57329
Gentics Content.Node 5.14.14
Bugfix RT57442
Gentics Content.Node 5.14.13
Bugfix RT56838
Bugfix RT56799
Bugfix RT57013
Bugfix RT57317
Bugfix RT57198
Bugfix RT57285
Bugfix
Bugfix
Bugfix RT55796
Bugfix RT57194
Bugfix RT57248
Gentics Content.Node 5.14.12
Bugfix RT55801
Bugfix RT57208
Bugfix RT57211
Bugfix RT57133
Bugfix RT50796
Bugfix RT56910
Bugfix RT57243
Bugfix RM12471
Bugfix RT57252
Bugfix RT57156
Bugfix RT56774
Bugfix RT55801
Gentics Content.Node 5.14.11
Enhancement RT55238
Bugfix
Bugfix RT56930
Bugfix RT56663
Bugfix RT57097
Bugfix RT57092
Bugfix RT57120
Bugfix RT56013
Bugfix RT56775
Gentics Content.Node 5.14.10
Bugfix RT57120
Bugfix RT57123
Gentics Content.Node 5.14.9
Bugfix RT57063
Bugfix RT57077
Bugfix RT57034
Gentics Content.Node 5.14.8
Enhancement RT57018
Bugfix RT56516
Bugfix RT56602
Bugfix RT56783
Bugfix RT56403
Gentics Content.Node 5.14.7
Bugfix RT56477
Bugfix RT56980
Bugfix RT56960
Bugfix RT56879
Bugfix RT56571
Gentics Content.Node 5.14.6
Bugfix RT56765
Bugfix RT56667
Bugfix RT56765
Bugfix RT56623
Bugfix RT56249
Gentics Content.Node 5.14.5
Enhancement RT56697
Enhancement RT56682
Enhancement RT56697
Bugfix RT56615
Bugfix RT56403
Bugfix RT54963
Bugfix RT56683
Bugfix
Bugfix RT56251
Bugfix RT56765
Bugfix RT55659
Gentics Content.Node 5.14.4
We recommend that the apache server signature will be hidden.
Set the following settings in the /Node/etc/httpd/extra/httpd-default.conf file: Security RT54513 ServerSignature Off ServerTokens Prod
A restart of the apache webserver is required in order to enable the settings.
Enhancement RT56615
Enhancement RT56609
Bugfix
Bugfix RT56642
Bugfix RT56245
Bugfix RT56477
Bugfix RT56251
Bugfix RT56642
Bugfix RM11868
Bugfix RT56518
Bugfix RT56601
Bugfix RT56498
Bugfix RT56423
Gentics Content.Node 5.14.3
Enhancement RT56423
Enhancement RT56111
Bugfix RT55802
Bugfix RT56282
Bugfix RT56480
Bugfix RT55753
Bugfix RT56423
Bugfix RT56423
Bugfix RT56570
Bugfix RM8723
Bugfix RT56438
Gentics Content.Node 5.14.2
Enhancement RT56423
Enhancement RT55738
Bugfix RT56456
Bugfix RT56517
Bugfix RT56436
Bugfix RT56437
Bugfix
Bugfix RT56274
Bugfix RT56429
Bugfix RT56500
Bugfix RT56435
Bugfix RT56328
Bugfix RT56497
Bugfix RT56020-RT56407
Bugfix
Gentics Content.Node 5.14.1
Enhancement RT56054
Enhancement RT55795
Bugfix RT56139
Bugfix RT55968
Bugfix RT55614
Bugfix RT56260
Bugfix RT54157
Bugfix RT54176
Bugfix RT55401
Gentics Content.Node 5.14.0
Also, the ability to manually select File Upload Manipulator-options on the file upload page has been removed. The decision on how files should be processed is now limited to the FUM itself.
MySQL 64 Bit Server version 5.6 or 5.5.
The package MySQL Server update will increase performance and ensure compatibility with feature releases. The update will also remove the 32Bit memory limitation of the old MySQL Server which was included in older package installations.
Please take a look at the updated database migration FAQ and package installation FAQ for more information on how to configure the MySQL Server and set the needed settings. The Gentics Content.Node Compatibility List contains a list of supported MySQL versions.
Feature RM7461
Feature RM5949
Enhancement RT55296
Enhancement RT55744
Enhancement RM9880
Enhancement RT54655
See Gentics Content.Node Fileuploaders for more information.
Enhancement RT54655
Enhancement RT56044
Enhancement RT55183
Enhancement RT56224
Enhancement RT53174
Bugfix RM7588
Gentics Content.Node 5.13.25
Bugfix RT56838
Bugfix RT56799
Bugfix RT57317
Bugfix RT57285
Bugfix
Bugfix
Bugfix RT55796
Bugfix RT57194
Gentics Content.Node 5.13.24
Bugfix RT55801
Bugfix RT57208
Bugfix RT57211
Bugfix RT57133
Bugfix RT50796
Bugfix RT56910
Bugfix RT57252
Bugfix RT57156
Bugfix RT56774
Bugfix RT55801
Gentics Content.Node 5.13.23
Enhancement RT55238
Bugfix
Bugfix RT56930
Bugfix RT56663
Bugfix RT57097
Bugfix RT57092
Bugfix RT57120
Bugfix RT56775
Gentics Content.Node 5.13.22
Bugfix RT57120
Bugfix RT57123
Gentics Content.Node 5.13.21
Bugfix RT57063
Bugfix RT57077
Bugfix RT57034
Gentics Content.Node 5.13.20
Enhancement RT57018
Bugfix RT56602
Bugfix RT56783
Bugfix RT56403
Gentics Content.Node 5.13.19
Bugfix RT56477
Bugfix RT56980
Bugfix RT56960
Bugfix RT56879
Bugfix RT56571
Gentics Content.Node 5.13.18
Bugfix RT56765
Bugfix RT56667
Bugfix RT56765
Bugfix RT56623
Bugfix RT56249
Gentics Content.Node 5.13.17
Enhancement RT56697
Enhancement RT56682
Enhancement RT56697
Bugfix RT56615
Bugfix RT56403
Bugfix RT54963
Bugfix
Bugfix RT56251
Bugfix RT56765
Bugfix RT55659
Gentics Content.Node 5.13.16
Please update the used JDK to the latest Java 6 version. We suggest a 64 bit version. Updates can be found here: http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6–419409.html
We recommend that the apache server signature will be hidden.
Set the following settings in the /Node/etc/httpd/extra/httpd-default.conf file: Security RT54513 ServerSignature Off ServerTokens Prod
A restart of the apache webserver is required in order to enable the settings.
Enhancement RT56615
Enhancement RT56609
Bugfix RT56642
Bugfix RT56245
Bugfix RT56477
Bugfix RT56251
Bugfix RT56642
Bugfix RM11868
Bugfix RT56518
Bugfix RT56498
Bugfix RT56423
Gentics Content.Node 5.13.15
Enhancement RT56423
Enhancement RT56111
Enhancement RT56423
Bugfix RT55802
Bugfix RT56282
Bugfix RT56480
Bugfix RT55753
Bugfix RT56423
Bugfix RT56423
Bugfix RT56570
Bugfix RM8723
Gentics Content.Node 5.13.14
Enhancement RT55738
Bugfix RT56456
Bugfix RT56517
Bugfix RT56436
Bugfix
Bugfix RT56274
Bugfix RT56429
Bugfix RT56435
Bugfix RT56328
Bugfix RT56497
Bugfix RT56020-RT56407
Gentics Content.Node 5.13.13
Enhancement RT56054
Enhancement RT55795
Bugfix RT56139
Bugfix RT55968
Bugfix RT55614
Bugfix RT56260
Bugfix RT54157
Bugfix RT54176
Bugfix RT55401
Gentics Content.Node 5.13.12
Bugfix
Gentics Content.Node 5.13.11
Because the GCN JS API will no longer automatically activate all tags in a page that is saved after editing, this change may require some implementations to be modified to manually activate in-active tags. A manual change will be necessary for example, if your implementation renders a page‘s inactive object tags in view mode via the GCN JS API. In this case, it will be necessary to first activate the tag using tag.prop('active', true).
Enhancement RT55246
Enhancement RT56261
Enhancement RT56054
Bugfix RT55948
Bugfix RT56138
Bugfix RT55141
Bugfix RT56181
Bugfix RT56098
Bugfix RT56174
Bugfix RT56127
Bugfix RT56138
Bugfix
Bugfix
Gentics Content.Node 5.13.10
Enhancement RT55978
Bugfix RM11269
Bugfix RT55946
Bugfix RT56107
Bugfix RT55676
Bugfix RT50562
Bugfix RT55756
Bugfix RT50562
Bugfix RT55458
$LDAP_LOGIN_FIELDS[“dontuse_uniquememberattribute”] = true;
Bugfix RT55458
Gentics Content.Node 5.13.9
Enhancement RT55980
Bugfix RT54768
Bugfix RT55933
Bugfix RT55983
Bugfix RT55989
Bugfix RT55898
Bugfix RT56053
Bugfix RT56028
Bugfix RT56056
Gentics Content.Node 5.13.8
Enhancement RT55694
Bugfix RT55959
Bugfix RT55875
Bugfix RT55856
Bugfix RT56021
Bugfix RT55941
Bugfix RT55962
Bugfix RT55793
Gentics Content.Node 5.13.7
Bugfix RT55393
Bugfix RT55854
Bugfix RT55744
Bugfix RT55390
Bugfix RT55706
Bugfix
Bugfix RT55744
Gentics Content.Node 5.13.6
Enhancement RT55154
Bugfix RT55739
Bugfix RT55709
Bugfix RT55772
Bugfix RT55887
Bugfix RT55709
Bugfix RT55709
Bugfix RT55761
Bugfix RT54820
Gentics Content.Node 5.13.5
Bugfix RT55269
Bugfix RT55600
Bugfix RT55642
Bugfix RT54936
Bugfix RT55269
Bugfix RT52250
Bugfix RT55307
Bugfix RT55188
Bugfix RT54981
Bugfix RT55680
Bugfix RT55485
Bugfix
Bugfix RT55240
Bugfix RT55500a-z A-Z 0-9 _ , . - ( ) [ ] { } $ Previously it was not possible to rename files to include those characters. The file uploader already accepted those characters within a uploaded file.
Bugfix RT55503
Bugfix RT55716
Bugfix RT55618
Bugfix RT55388
Gentics Content.Node 5.13.4
If you are using validation and have a antisamy.custom.xml file (probably in /Node/etc/), you have to add the following setting to it in order to fix the strict validation:
Bugfix RT54941
Bugfix RT55324
Bugfix RT55239
Bugfix RT55313
Bugfix RT54461
Bugfix RT55451
Bugfix RT55217
Bugfix RT55299
Bugfix RT54936
Bugfix RT55475
Bugfix RT55328
Bugfix RT55394
Bugfix RT55242
Bugfix RT55496
Gentics Content.Node 5.13.3
Security RT54512
Security RT54512
Enhancement
Bugfix RT55346
Bugfix RT55346
Bugfix RT55158
Bugfix RT55312
Bugfix RT55143
Gentics Content.Node 5.13.2
Bugfix RT54731
Bugfix RT55134
Bugfix RT55211 GCN linkbrowser plugin: Fixed href not being updated after selecting a page/file from the link browser. Now the href will be set to a # when a GCN page or file is selected. This also fixes the linkplugin targetRegex setting not correctly working.
Bugfix RT55127
Bugfix RT55065
Bugfix RT55143
Bugfix RT55299
Bugfix RT55260
Bugfix RT53937
Bugfix RT53746
Gentics Content.Node 5.13.1
Enhancement
Bugfix RT54771
Bugfix RT53175
Bugfix RT54620
Bugfix RT54078
Bugfix RT54954
Bugfix
Bugfix RT54935
Bugfix RT54911
Bugfix RM9990
Bugfix RT54509
Bugfix RT54493
Bugfix RT54882
Gentics Content.Node 5.13.0
If you pass the session secret in the ?do=100 URL now, you will be redirected to the same URL without the session secret in the sid= parameter. If your system setup is relying on this information in the URL (which it shouldn‘t) in any way, please enable the following feature in your GCN configuration:
$FEATURE[‘disable_sessionsecretredirect‘] = true;
This will keep the old behavior like in the previous GCN versions. However, we don‘t recommend enabling this, use it at your own risk!
Enhancement
Enhancement RT53533
Enhancement
Enhancement
Enhancement
Although still available for backwards compatibility, the following channels are deprecated with this change:
Enhancement RM2239
Additionally, the maintenance dialog has been improved:
Enhancement RM8177
Enhancement RT54240
Enhancement
Enhancement RM6440
Bugfix
Gentics Content.Node 5.12.28
Bugfix
Gentics Content.Node 5.12.27
Enhancement RT56054
Gentics Content.Node 5.12.26
Bugfix RT55948
Bugfix RT56138
Gentics Content.Node 5.12.25
Bugfix RT55141
Bugfix RT56098
Bugfix RT56174
Bugfix RT56127
Bugfix RT56138
Gentics Content.Node 5.12.24
Enhancement RT55978
Bugfix RM11269
Bugfix RT55946
Bugfix RT56107
Bugfix RT55676
Bugfix RT50562
Bugfix RT55756
Bugfix RT50562
Bugfix RT55458
$LDAP_LOGIN_FIELDS[“dontuse_uniquememberattribute”] = true;
Bugfix RT55458
Gentics Content.Node 5.12.23
Bugfix RT54768
Bugfix RT55933
Bugfix RT55989
Bugfix RT56053
Bugfix RT56028
Gentics Content.Node 5.12.22
Enhancement RT55694
Bugfix RT55959
Bugfix RT55875
Bugfix RT55856
Bugfix RT56021
Bugfix RT55941
Bugfix RT55962
Bugfix RT55793
Gentics Content.Node 5.12.21
Bugfix RT55744
Bugfix RT55390
Bugfix RT55706
Bugfix
Bugfix RT55744
Gentics Content.Node 5.12.20
Bugfix RT55887
Gentics Content.Node 5.12.19
Because the GCN JS API will no longer automatically activate all tags in a page that is saved after editing, this change may require some implementations to be modified to manually activate in-active tags. A manual change will be necessary for example, if your implementation renders a page‘s inactive object tags in view mode via the GCN JS API. In this case, it will be necessary to first activate the tag using tag.prop('active', true).
Bugfix RT55709
Bugfix RT55772
Bugfix RT55709
Bugfix RT55709
Bugfix RT55761
Bugfix RT54820
Gentics Content.Node 5.12.18
Bugfix RT55269
Bugfix RT55600
Bugfix RT54936
Bugfix RT52250
Bugfix RT55307
Bugfix RT55188
Bugfix RT54981
Bugfix RT55485
Bugfix
Bugfix RT55240
Bugfix RT55500a-z A-Z 0-9 _ , . - ( ) [ ] { } $ Previously it was not possible to rename files to include those characters. The file uploader already accepted those characters within a uploaded file.
Bugfix RT55503
Bugfix RT55388
Gentics Content.Node 5.12.17
If you are using validation and have a antisamy.custom.xml file (probably in /Node/etc/), you have to add the following setting to it in order to fix the strict validation:
Bugfix RT54941
Bugfix RT55324
Bugfix RT55239
Bugfix RT55313
Bugfix RT54461
Bugfix RT55451
Bugfix RT55217
Bugfix RT55299
Bugfix RT54936
Bugfix RT55475
Bugfix RT55328
Bugfix RT55394
Bugfix RT55242
Bugfix RT55496
Gentics Content.Node 5.12.16
Security RT54512
Security RT54512
Bugfix RT55346
Bugfix RT55158
Bugfix RT55312
Bugfix RT55143
Gentics Content.Node 5.12.15
Bugfix RT54731
Bugfix RT55134
Bugfix RT55211 GCN linkbrowser plugin: Fixed href not being updated after selecting a page/file from the link browser. Now the href will be set to a # when a GCN page or file is selected. This also fixes the linkplugin targetRegex setting not correctly working.
Bugfix RT55127
Bugfix RT55065
Bugfix RT55143
Bugfix RT55299
Bugfix RT55260
Bugfix RT53937
Bugfix RT53746
Gentics Content.Node 5.12.14
If you pass the session secret in the ?do=100 URL now, you will be redirected to the same URL without the session secret in the sid= parameter. If your system setup is relying on this information in the URL (which it shouldn‘t) in any way, please enable the following feature in your GCN configuration:
$FEATURE[‘disable_sessionsecretredirect‘] = true;
This will keep the old behavior like in the previous GCN versions. However, we don‘t recommend enabling this, use it at your own risk!
Bugfix RT55042
Bugfix RT54509
Bugfix RT54493
Bugfix RT54882
Gentics Content.Node 5.12.13
Bugfix RT54771
Bugfix RT53175
Bugfix RT54620
Bugfix RT54078
Bugfix RT54954
Bugfix
Bugfix RT54935
Bugfix RT54911
Gentics Content.Node 5.12.12
Bugfix RT54602
Bugfix RT54821
Bugfix RT54501
Bugfix RT54157
Bugfix RT54157
Bugfix RT54853
Bugfix RT54794
Bugfix RT51839
Bugfix RT54491
Bugfix RT53854
Bugfix RT54717
Gentics Content.Node 5.12.11
Bugfix RT50917
Bugfix RT54298
Bugfix RT53076
Bugfix RT50917
Bugfix RT52737
Bugfix RT54411
Gentics Content.Node 5.12.10
Bugfix RT54424
Bugfix RT54723
Bugfix RT54696
Bugfix RT54614
Bugfix RT54671
Bugfix RT54671
Bugfix RT54661
Bugfix RT54653
Bugfix RT54684
Bugfix RT54220
Bugfix RT54526
Bugfix RT50986
Bugfix RT54264
Bugfix RT54489
Bugfix RT54628
Bugfix RT54591
Bugfix RT54220
Gentics Content.Node 5.12.9
Bugfix RT54493
Bugfix RT54540
Bugfix RT53095
Bugfix RT54580
Bugfix RT54423
Bugfix RT54074
Bugfix RT54017
Bugfix RT53236
Gentics Content.Node 5.12.8
Bugfix RT54499
Bugfix RT54320
Bugfix RT54424
Bugfix RT54273
Bugfix RT52367
Bugfix RT53896
Bugfix RT54386
Bugfix RT50850
Gentics Content.Node 5.12.7
Enhancement RT54143
Bugfix RT54258
Bugfix RT54269
Bugfix
Bugfix RT53383
Bugfix RT51491
Bugfix RT54164
Bugfix RT54240
Bugfix RT54304
Bugfix RT54332
Gentics Content.Node 5.12.6
Bugfix RT54334
Gentics Content.Node 5.12.5
Bugfix RT54137
Bugfix RT54088
Bugfix RT54272
Bugfix RT54258
Bugfix RT54088
Bugfix RT54077
Bugfix RT54088
Bugfix
Bugfix RT54315
Bugfix RT53910
Bugfix RT52789
Bugfix RT52846
Gentics Content.Node 5.12.4
Bugfix
Bugfix RT53984
Bugfix RT54173
Bugfix RT54207
Bugfix RT50864
Gentics Content.Node 5.12.3
Bugfix RT53835
Bugfix RT54125
Bugfix RT54117
Bugfix RT54130
Gentics Content.Node 5.12.2
Bugfix RT54003
Bugfix RT54011
Bugfix RT53935
Bugfix RT53839
Bugfix RT53921
Bugfix
Bugfix RT53746
Bugfix RT53943
Gentics Content.Node 5.12.1
Bugfix RT52133
Bugfix
Bugfix RT53850
Bugfix RT53460
Bugfix RM6321
Gentics Content.Node 5.12.0
Enhancement RM4207
Enhancement RM6727
Enhancement RM6756
It is important to note, that if an implementation directly uses the property pubdir_ of a node object for files or images, this should be changed to use the new property pubdir_bin_. Otherwise the implementation would fail if separate publish directories are used.
Enhancement RM5973
More information about this new interface can be found in the Gentics Content.Node Guides
Enhancement RM6734
Enhancement
Enhancement RM6214
More information about this new feature can be found in the Gentics Content.Node Guides
Enhancement
Enhancement RT53014
Enhancement
Enhancement RT53254
Enhancement
Bugfix RT53391
Bugfix RT52692
Bugfix RT52759
Bugfix RT53265
Bugfix RT53375
Bugfix
In order to access the profiler, the path /Profiler must be added to the JkMounts of the apache configuration.
The profiler webapp is secured with basic authentication for the roles manager or gentics. In order to gain access, the application server must be configured for basic authentication, e.g. by adding an appropriate user in /Node/tomcat/conf/tomcat-users.xml
Bugfix RT53199
Bugfix RT47489
Bugfix RT53018
Bugfix RT52849
Bugfix RT53378
Bugfix RM7332
Bugfix RT53474
Bugfix RT53706
Bugfix RT53758
Bugfix RT52865
Bugfix RT53635
Bugfix
Bugfix RT53596
Bugfix RT53046
Bugfix RT53383
Bugfix RT53477
Bugfix RT53506
Gentics Content.Node 5.11.5
Bugfix RT53183
Bugfix RT52346
Bugfix RT53148
Bugfix RT52634
Gentics Content.Node 5.11.4
Bugfix
Gentics Content.Node 5.11.3
Bugfix
Gentics Content.Node 5.11.2
Bugfix
Bugfix RT53018
Gentics Content.Node 5.11.1
Enhancement RT52864
Enhancement
Enhancement
Bugfix RT52516
Bugfix RT52746
Bugfix RT52759
Bugfix RT52368 in that case, the logoutpage was only shown in the current frame. After the fix, logout-pages are always displayed in the whole page.
Bugfix RT51642
Bugfix RT52634
Bugfix RT51911
Bugfix RT52573
Bugfix RT52830
Bugfix RT52776
Bugfix RT51051
Bugfix RT52987
Bugfix RT52259 RT52605
Bugfix RT52762
Bugfix
Bugfix RT52290 RT52043
Bugfix RT52964
Bugfix RT52751
Bugfix RT50625
Bugfix RT52876
Bugfix RT52712 RT52660
Gentics Content.Node 5.11.0
Enhancement
Enhancement RT52344
Gentics Content.Node 5.10.0
Enhancement RT5682
Enhancement RM5826 RT52022
Enhancement RT52622
Enhancement RT51756
Enhancement
Enhancement RT51974
Bugfix RT52405
Bugfix RT52572
Bugfix RM5993
Bugfix RT52491
Bugfix RT52442
Bugfix
Bugfix RT52191
Bugfix
Bugfix RM5993
Bugfix RT51642
Bugfix RT52715
Bugfix RT52416
Bugfix RT52202
Bugfix RT52413
Bugfix RT52597
Bugfix RT52297
Bugfix RT51972
Bugfix RT52396
Gentics Content.Node 5.9.5
Bugfix
Bugfix
Gentics Content.Node 5.9.4
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.9.3
Bugfix RM5650
Gentics Content.Node 5.9.2
Bugfix
Bugfix
Bugfix
Bugfix RM5624
Bugfix RM5611
Gentics Content.Node 5.9.1
Bugfix
Bugfix RM4147
Bugfix
Bugfix RM5478
Bugfix
Bugfix RM4624
Bugfix RM3811
Bugfix RM5395
Bugfix RM5550
Bugfix
Bugfix
Gentics Content.Node 5.9.0
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement RM2372
The image within node B will be resized when the GenticsImageStore determined that the referenced node (in this case node b) is publishing into the filesystem. Resizing will otherwise be omitted.The image tag must be adapted to include the node B hostname.
Example velocity implementation:
#if($cms.rendermode.publish) #else
#end
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement RT52125
Enhancement
Enhancement RT52133
Enhancement RT51866
Bugfix RT51687
Bugfix RT51707
Bugfix RT51953
Bugfix RT51959
Bugfix RT51674
Bugfix RT51433
Bugfix RT51554
Bugfix RT51637
Bugfix RT51863
In both cases the #myeditable should be identified as the root element which is to contain the rendered contents of:
Bugfix RT51971
Bugfix
Bugfix RT51641
Bugfix
Bugfix RT51674
Bugfix RT51855
Bugfix RT51638
Bugfix RT51486
Bugfix
Bugfix RT51863
Bugfix
Bugfix RT51638
Bugfix RT51889
Bugfix RT51912
Bugfix
Bugfix RT51757
Bugfix RT52023
Bugfix
Bugfix RT51740
Bugfix RT52004
Bugfix RT51872 the dialog belonged to wasn‘t loaded anymore.
Bugfix RT52044
Bugfix RT52055
Bugfix
Gentics Content.Node 5.8.0
Enhancement
Enhancement
Enhancement
Enhancement /CNPortletapp/rest/page/newtag/{id} now also supports creation of a tag as copy of another tag (in the same page or in another page).
Bugfix
Bugfix
Bugfix
Bugfix RT48547
Bugfix
Bugfix RM3829
Bugfix RT51673
Bugfix RT51544
Bugfix
Bugfix RT51584
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.7.2
Enhancement
The tooltips now include the information that the ‘Publish into the Filesystem‘ checkbox state will only be updated after the next publish run.
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix 50537
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix 50992
Bugfix
Bugfix
Bugfix 51261
Bugfix
Bugfix
Bugfix 50931
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix 51511
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix 51257
Bugfix tag.edit('#content');
The outerHTML of HTMLElement#content will now be:
Rather than:
Bugfix
Bugfix
Gentics Content.Node 5.7.1
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.7.0
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.6.3
Bugfix
Gentics Content.Node 5.6.2
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.6.1
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.6.0
-schema policymap.xsd /Node/etc/policy-map.custom.xml
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Gentics Content.Node 5.5.8
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.5.6
Enhancement
Bugfix
Bugfix
when saved. This
tags will only be present while editing, if not using Internet Explorer.Additionally, the behaviour of creating empty paragraphs will now be consistent across all browsers, and regardless of whether the metaview plugin is turned on or off.
Bugfix
Gentics Content.Node 5.5.5
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.5.4
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix without explicitly clicking 'save' first no new page version was created. When the page was finally published by another user, a page version was created, but incorrectly assigned to the publishing user, not the editor. This behaviour has been fixed now. Placing a page in the publish queue will now always create a new page version, if necessary.
Gentics Content.Node 5.5.3
Enhancement
Enhancement
Example: $ALOHA_SETTINGS_NODE[1]['plugins']['gcn']['config'] = array("tagtypeWhitelist" => array("link", "wikilink", "formspace", "htmllang", "myuncategorizedtagtype")); $ALOHA_SETTINGS_NODE[1]['plugins']['gcn']['editables'] = array( "#customEditableId" => array("tagtypeWhitelist" => array("myuncategorizedtagtype")), ".header" => array("tagtypeWhitelist" => array("link", "seitentag", "download", "upload")), "#GENTICS_METAEDITABLE_page_name" => array("tagtypeWhitelist" => array("fileurl", "breadcrumb", "lswitch")) );
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.5.2
Enhancement
Added features “redirect_check_referer“ and “redirect_assume_https“ for redirecting the request to load the latest version of Aloha Editor with an URL like /CNPortletapp/latest/..., if using an additional Apache to handle SSL.Normally, the redirect would be done relative to the incoming request, but if an additional Apache is used to handle SSL, the incoming request to the backend would not know about https:// and the redirect would be done to http://.To avoid this, it is possible to use the feature “redirect_check_referer“, which would let the redirector check the referer URL and use the schema and hostname from it. In cases, where it is not sure, whether the referer is always available, it is possible to also use the feature “redirect_assume_https“ to always do the redirect to https:// and the hostname sent in the request header “Host”.
Gentics Content.Node 5.5.1
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.5.0
$MULTILEVEL_PUB_WORKFLOW[nodeId] = true;
in the /Node/etc/node.conf for all nodes.
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.22
UPDATE ml SET contenttype = 'text/javascript' WHERE name='JavaScript'; The incompatibility caused pages that were created with the text/javscript mimetype to be displayed incorrectly within any portal that serves pages using the GenticsContentPortlet.
Gentics Content.Node 5.4.21
Gentics Content.Node 5.4.20
Gentics Content.Node 5.4.19
Security
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.16
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.15
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.14
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.12
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.11
Enhancement
Bugfix
Bugfix
Gentics Content.Node 5.4.10
Bugfix
Bugfix
Gentics Content.Node 5.4.9
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.8
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.7
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix Dhttp.connectionmanager.max-per-host=20 Dhttp.connectionmanager.max-total=40
Bugfix
Bugfix
Gentics Content.Node 5.4.6
Enhancement
Bugfix
Bugfix
Gentics Content.Node 5.4.5
Bugfix
Bugfix
Gentics Content.Node 5.4.4
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.3
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.2
Security
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.1
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Enhancement
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Bugfix
Gentics Content.Node 5.4.0
u "%user%,%password%" e "mirror R L e /Node/node/content/publish/pub/%ordner.node.host%%ordner.node.pub_dir% ./%wwwRoot%%ordner.node.pub_dir%;mirror R L e /Node/node/content/publish/pub/%ordner.node.host%/GenticsImageStore ./%wwwRoot%/GenticsImageStore;exit" %targetHost% 2>&1
Security
Enhancement
Enhancement
Enhancement
This maximum is only in effect if the validation feature is turned on and configured correctly. The setting may be changed in the antisamy.custom.xml with the maxInputSize directive.See this article for more information about the validation feature.
Bugfix
Bugfix
Bugfix
WebDAV folders are now opened with the IE Web Folder API. On Windows 7IE8 file:// URLs are still used as the Web Folder API didn't work inthis configuration. The three methods to open a WebDAV folder are# folder is opened automatically immediately on clicking open on a folder in the tree# folder is opened by clicking the "here" link# folder is opened by copying the "here" link and pasting it manually into a new browser windowThese three methods were tested and work in the following configurations:# Windows XP IE7# Windows XP IE8# Windows 7 IE8# Windows 7 IE9To force the use of the Web Folders API the feature webdav_use_file_url can be set to false (default true).To force the old behaviour of opening WebDAV folders the feature webdav_use_web_folders can be set to false (default true).The default is to use the Web Folders API except on Windows Vista IE8 and Windows 7 IE8.If opening a folder doesn't work on Vista or Windows 7, try installing this update
Bugfix
Bugfix
Bugfix
It now cuts the filename first so the file extensions always can be fully added.
Bugfix
Bugfix
Fixed bug in GenticsImageStore which sometimes didn‘t round calculcated proportional widths or heights of images correctly when doing image resizing.
Example:
Gentics Content.Node 5.3.26
Enhancement
The filepublisher will now fetch batches of pages instead of all pages at once. This will increase performance and reduce the memory footprint when writing files into the filesystem.
Enhancement
Add missing startPageId to folder returned from RestAPI
Enhancement
Changed the Node and Content Repository select field in “maintenance“ to not have “All” as first item selected automatically.
Bugfix
Fixed a bug when publishing pages with timemanagement using the REST API: If page had a timemanagement set and was published using the REST API, it was published regardless of the current timeframe of the timemanagement. This is fixed now, timemanagement will now also be honoured when publishing pages using the REST API.
Bugfix
Fixed: A wrong error message which occured when trying to move a page into another folder where a page with the same filename already exists.
It now renames the file instead if printing an error message (in most cases).
Bugfix
Fixed resolving of parts within the get method of custom part types.
Bugfix
Fixed: inconsistency in value table
Deleting a tag-part by importing a tag-type, or restoring a page version, possibly resulted in an inconsistency in the value table. The inconsistency was an entry in the value table that referenced a part that didn‘t exist.This change fixes the deletion of tag-parts, so that whenever a tag-part is deleted, all values will be removed from both the current and the versioned value tables.Additionally, the update procedure will remove all inconsistent values from both the current and the versioned value tables, to fix any existing inconsistency. Only unreachable values will be removed.
Bugfix
Added timeout for UrlIncludeImp connection pool. In rare cases the urlinclude imp could create a deadlock situation when the connection pool is full and no connection is avialiable for pending include actions. In that case the urlincludeimp waited until a connection was freed. In rare cases the connections were never freed thus causing a deadlock situation.
Bugfix
Fixed a bug where the Gentics ImageStore sometimes fails because of missing image mime type mappings.
Bugfix
Fixed file uploader not checking filesizes correctly (it always added ~600bytes to the actual filesize)
Bugfix
Fixed: scheduler task execution during winter-time
A scheduler task with a start date during summer-time was scheduled during winter-time at every minute of the hour leading up to the actual execution-time. This means that the task potentiall executed 60 times instead of only once.
Gentics Content.Node 5.3.24
Bugfix
Fixed missing CHANGELOG type (SQL) in system.CHANGELOG and some missing ‘;‘. Those issues caused a problem with database updates. The previously missing database update did not affect operation since it was just a regular performance optimisation.
Gentics Content.Node 5.3.23
Gentics Content.Node 5.3.22
Enhancement
The rest api will now return translated messages for copy and file upload actions.
Enhancement
Aloha Editor‘s gcn-plugin will now compare the construct id instead of the tagname when searching for magic link constructs.
Bugfix
Fixed i18n file upload limit reached message. Instead of showing the full bytesize we‘ll now show human readable values.
Bugfix
Fixed a bug with $cms.page.versions.major attribute which would not be initialized correctly.
Bugfix
Fixed an exception thrown when accessing the REST API method /CNPortletapp/rest/folder/getItems/... with Content-Type:text/xml. It has to be noted, that the REST API method /CNPortletapp/rest/folder/getItems/... currently is not fully supported when using Content-Type:text/xml. The response currently will not contain all available data (like for Content-Type:application/json).
Bugfix
Aloha Page Servlet will now also provide construct id via Aloha.plugins.gcn.blocks[].constructid for Gentics Content.Node blocks.
Bugfix
Fixed adding links with the gcn-linkbrowser plugin. Previously the highlight css was not removed when selecting an element with the link browser plugin.
Bugfix
Fixed instant messages not showing new lines and htmlentities correctly and also sometimes not showing the message at all.
Bugfix
The gcn repository will now state an error message and log to the console, if an error occurs while querying the Gentics Content.Node backend for files and pages.
Gentics Content.Node 5.3.20
Gentics Content.Node 5.3.19
Bugfix
Fixed a css bug with editicons in Firefox, where icons would have an unwanted offset. Also added zero border with to images within tagicons to prevent them from being outlined when inside an anchor tag. Therefore the following css classes have been changed: “.GENTICS_block .aloha-editicons button” (added borders and background) and .GENTICS_block .aloha-editicons button img (added border 0px).
Bugfix
Fixed: The REST API FolderResource calls to fetch items in folders recursively has been improved to use more efficient SQL statements.
Bugfix
Increased the timeout for AJAX calls to the REST API to be 60s (formerly 10s)
Gentics Content.Node 5.3.18
Manual Change
The gtxalohapagelink tag-type was updated.
Please update the gtxalohapagelink tag-type according to this definition.This fixes a bug where additional whitespace is inserted around internal links.
Manual Change
Removed handling of magic image blocks.
This affects the handling of gtxalohaimage tags. The inline image block handling and editing was replaced with the new imagemanipulation2 feature. This change is only required when the feature aloha010 is enabled.
Enhancement
The type of objects which are listed in the URL field of the link plugin, and in the repository-browser, can now be configured in the node.conf.For example, the default configuration of the URL field of the link plugin will list only pages:
Enhancement
In
Enhancement
The REST API FolderResource has a new method getItems to get a paged,sorted list of pages,images and files
Enhancement
The sidebar can now be disabled using the following setting: $ALOHA_SETTINGS['sidebar']['disabled'] = 'true';For more information please take a look at the aloha editor changelog.
Enhancement
The Aloha Editor gcn plugin will now deliberately ignore magic links with a data attribute data-gcnignore=”true
Enhancement
The Aloha Editor‘s format plugin functionality “removeFormat” may now be configured to remove more than the standard set of formattings. By default it will only remove the following html tags: ‘strong‘, ‘em‘, ‘b‘, ‘i‘, ‘cite‘, ‘q‘, ‘code‘, ‘abbr‘, ‘del‘, ‘sub‘, ‘sup‘. You can however provide a different set of tags to be removed by adding your configuration as an array to the format plugin‘s Aloha settings:
Enhancement
The GCN repositories used by alohaeditor now provide metainformation to support better paging in the browser.
Enhancement
The REST API calls to get objects in folders will now return numItems (total number of items) and hasMoreItems (true if more items are available), to support client side paging
Enhancement
The table and commands plugin were added to the list of default aloha plugins. A guide on how to add additional plugins can be found here.
Enhancement
Templates that don‘t have a doctype will get a default html5 doctype. The doctype will only be added when viewing the page in editmode. Preview and livemode are not affected. For more information please read this FAQ.
Bugfix
The imagemanipulation2 will now display a messagebox whenever the user enters a imagesize that exceeds the given bounds.
Bugfix
When using the Repository Browser in Aloha to find pages, the sorting of folders was different than in the tree: folders starting with ‘[‘ were sorted first in the Repository Browser, while they are sorted last in the tree. This has been fixed now, the sorting should be identical now.
Bugfix
Searching for files from the Aloha-Link-Plugin URL-attribute-field will find files that don‘t match the search text.The Bug only occurred if file-search was configured for the URL-attribute-field.
Bugfix
The default setting of the imagemanipulation2 contained an error that disabled the keep aspect ratio button.
Bugfix
The customform_resolve_nodetags feature didn‘t work in the Portal.Node frontendIf the customform_resolve_nodetags feature was activated, and thetag-fill dialog was opened in the Portal.Node frontend (by clicking on atag) customform parts were rendered as the empty string.
Bugfix
Entering a width or height in the imagemanipulation2 image size fields sometimes led to a reduction of the image size. Values that exceed the bounds of the image will now be correctly reduced to the defined limits of the image manipulation2. The aspect ratio will be preserved correctly.
Bugfix
When using the DiffResource of the REST API to calculate diffs between given HTML codes, using either method diff/html or diff/source, the templates used to render differences are now restricted to accessing Object Properties. It is no longer possible to invoke Methods of objects.
Bugfix
Fixed: the REST-API will now correctly apply filters when querying for files.
Bugfix
When a page-import is performed, the user of all active sessions will be set to the user of the page-import.
Bugfix
The imagemanipulation2 will now automatically resize images to a size that does not exceeds the given bounds.
Bugfix
When using the Repository Browser in Aloha to get pages and files, the paging will now work correctly.
Bugfix
The #nodeViews container in the assistant frame was set to a fixed width.
Bugfix
Fixed a NPE in the REST-API when querying for pages with versioninfo=true.
Bugfix
When using Aloha 0.20 for editing, the language for Aloha UI is now the the CMS UI language for the current user.
Bugfix
The Repository Browser is now translated correctly.
Bugfix
Some i18n translations were missing for the imagemanipulation2 feature. Those missing translations were added.
Bugfix
The ribbon will now no longer toggle between visibe and invisible mode when entering the edit mode. The ribbon will now only be shown when using the realedit mode
Bugfix
Fixed: Clean-up of Aloha editables during initializationEarlier, the generic and the santize content-handler were used toclean-up an editable when it was initialized. Now, no clean-up will beperformed on initialization.In particular, the generic content-handler performed transformationslike turning a strong tag into a b tag, which was undesired.
Bugfix
Fixed a css bug with editicons in Firefox, where icons would have an unwanted offset. Also added zero border with to images within tagicons to prevent them from being outlined when inside an anchor tag. Therefore the following css classes have been changed: “.GENTICS_block .aloha-editicons button” (added borders and background) and .GENTICS_block .aloha-editicons button img (added border 0px).
Bugfix
Publishing a page from the Aloha wiki-mode only saved the page, but didn‘t publish it.
Gentics Content.Node 5.3.15
Manual Change
Aloha Page Link TagType Changes
Please update the gtxalohapagelink tag-type according to this definition new parts are avaialbe, “title“ and “target”. The parts can be accessed by an editor either through the tagfill-dialogue or through the Aloha-Editor sidebar.
Enhancement
Enhanced UI: Icons for disabled tags are displayed with a translucent styleThe change was made for the tag-list of templates and pages, to more quickly identify disabled tags.
Bugfix
SQLException during CRSync causes inconsistencyWhen a SQLException occurred during the attribute-prefetching phase of a CRSync, some attributes were not synced correctly.The inconsistency can be repaired by updating the objects in the source repository.The bug was fixed by aborting the CRSync should an Exception occur during the attribute-prefetching phase.
Bugfix
A OutOfMemory error did not release a database connection properly.
Bugfix
Viewing the differences between two version of a Page takes very longAn inefficient regex in the code that implements the DaisyDiff algorithm caused the Page that shows the differences to take a long time to load.
Bugfix
Permissions on the root folder of a node are handled incorrectlyThere are usually two entries in the perm table for the root folder of a node: an entry with o_type = T_FOLDER and an entry with o_type = T_NODE (both with o_id =
Bugfix
The DaisyDiff algorithm is now only used for pages with the text/html mimetype
Bugfix
Its now possible to delete a contenttag with a new tag button within the edit view. The html structure of that tag icon container has changed. This will affect custom css that modify the tag icon position/behaviour.
Bugfix
Saving pages with the REST API will ignore selected optionsSaving the selection of single-select and multi-select part is now implemented.During this change, the ID, for options of single-select and multi-select parts, were changed to refer to an internal ID (called internally the “dsid”).
Bugfix
When pages are published no notification messages are sent.Notifications were only sent when a page was published from the publish-queue. Notifications were not sent when the user clicked on the page in the publish-queue, or navigated to the page, and published itoutside of the publish-queue page (through the page-menu for example).The new behaviour will always send notifications, no matter where the page is published or saved (put into revision), as long as the page is visible in the publish queue.
Bugfix
Templates that don‘t have a doctype will get a default html5 doctype. The doctype will only be added when viewing the page in editmode. Preview and livemode are not affected. For more information please read this FAQ.
Bugfix
If the Tidy feature was used with the Live Editor, sometimes additional spaces were inserted into the content.
Bugfix
Previously the pageimport didn‘t delete files/pages when importing using the import_diff setting.
Bugfix
The topnav menu for the imagemanipulation2 view was fixed. Its now possible to access the object properties of the image.
Gentics Content.Node 5.3.11
Enhancement
Added css class ‘gtx-diff‘ to CN‘s ins and del tags, so they can be distincted from normal html code.
Enhancement
A velocity inline scope setting was turned off because it may cause too much memory consumption. If the following Velocity setting is activated, macros will be saved in the namespace for each tag instead of the global namespace. Velocity apparently doesn‘t clean up namespaces, which will cause too much memory consumption if there are many tags that use macros.
Bugfix
Fixed a bug that caused the filename extension to be appended to the filename on every save.
Bugfix
Fixed bug in permission checking system (when trying to delete all languages of a page with no language set).
Bugfix
Fixed issue with aloha page links. Previously only pages from the node with folder_id 1 (GCN5 Demo); where displayed within the dropdown list.
Bugfix
Fixed javascript error within the new imagemanipulation2 that occured on pageload.
Bugfix
Fixed a bug in the purgelogs task that prevented the jobrun table to be cleaned.
Bugfix
Fixed isses with the publish queue. Now it is no longer impossible to select multiple users across multiple pages when assigning pages to to users in the publish queue.
Bugfix
Fixed a bug in the REST API when a page with an overview is loaded and subsequently saved. If no selectedItemIds element is provided for an overview in a tag, it will be assumed to be the same as an empty selectedItemIds element.
Bugfix
Fixed bug where it does not check if contentset_id is 0 in the mini browser (it sometimes didn‘t show all pages in page selection tags).
Bugfix
Fixed error that occured when changing the template of multiple pages at once.
Bugfix
Fixed possible NPE when performing the action “Change Template”. This NPE could further lead to DB locks remaining open.
Gentics Content.Node 5.3.5
Bugfix
Fixed the following issue: If the versiondiff (source-mode) processes a page where an opening angle bracket occurs in an HMTL comment or an HTML Tag, it will not be escaped, causing the result diff to break.
Gentics Content.Node 5.3.1
Manual Change
The Aloha Editor plugin API was changed
Aloha Editor 0.10 will no longer expose it‘s internal jQuery object through the $ and/or jQuery variables. You have to include your own version of jQuery if you relied on Aloha Editor‘s version prior to this update.# The “GENTICS_“ prefix for CSS class names has been replaced by “aloha-“. If you targeted those specific class names in your implementation those need to be updated.# The “GENTICS.Aloha“ namespace for Aloha Editor‘s JavaScript objects has been reduced to “Aloha” alone.*Please note:*# If you want to edit your pages using Aloha Editor a valid doctype has to be specified.# As the plugin system has been fully rewritten in Aloha Editor 0.10 plugins you wrote for 0.9.3 will not work with the new version. See our documentation on how to edit plugin settings.
Optional Manual Change
Added new Version 0.10 of Aloha Editor to Gentics Content.Node
Added new Version 0.10 of Aloha Editor to Gentics Content.Node, which brings a load of new features like plugin bundles, dependency loading with requirejs and other improvements to your editing experience. Please refer to http://www.github.com/alohaeditor/Aloha-Editor or http://www.aloha-editor.org for additional and more detailed information. Aloha Editor 0.10 may be activated by setting $FEATURE[“aloha010“] = true; and $FEATURE[“aloha”] = true; in your node.conf. You may continue to use Aloha Editor 0.9.3 though without enabling the new feature.
Enhancement
Added parameter “versioninfo” to REST API call /rest/page/load/ to get version information
Enhancement
Resolving node tags in custom-forms only worked in the tag-fill dialogueof content tags (pages). For template tags (templates) or tag-types, theentire custom-form was rendered as the empty string if thecustomform_resolve_nodetags feature was activated.Now, if the custom-form is rendered as part of the tag-fill dialogue fortemplate tags or tag-types, all will resolve to the emptystring. Special custom-form tags (e.g.
Enhancement
Aloha Editor package is no longer provided by Gentics Content.Node‘s integrated Apache webserver, as it has been moved to the CNPortletapp
Enhancement
The autoupdate dialog will now display the selected update policy which can be configured via the update_policy feature.
Enhancement
Linking a template to a new folder will now check for templates with the same name in the target folder and abort with an error message.
Enhancement
Please follow the steps that are described in our FAQ » "How do I enable the Gentics Profiler webapplication?" to enable the profiler webapp. Activation of the profiler is optional.
Enhancement
The autoupdate dialog will now display the selected update policy which can be configured via the update_policy feature
Enhancement
Reduced z-index of resize handle for resizable lists. This prevents the handles shining through actions dropdown.
Bugfix
Fixed problems with template source view in IE6 and IE7
Bugfix
Fixed language management: It is no longer possible to delete page languages, if pages with that language exist.
Bugfix
Fixed possible deadlocks when publishing into contentrepositories that use Instant Publishing.
Bugfix
Fixed a bug with Aloha Editor that prevents internal links from being created
Bugfix
Fixed detection of deleted/moved/offline objects when publishing into ContentRepository: It was possible that object being deleted, moved or taken offline while a publish process was running, would not be removed from the contentrepository at all.
Bugfix
Fixed possible JS error when saving pages after changing an internal link to an external one using Aloha Editor
Bugfix
Fixed possibly misaligned top menu when switching multiple times between page preview (aloha mode) and taglist.
Bugfix
Fixed: when a Node had no languages assigned, and a user had the deletepermission on only some, but not all folders, and the user tried todelete a page on which he had permissions, he was incorrectly informedthat he didn‘t have any permissions.
Bugfix
Fixed setting links to files using Aloha Editor: When pages are edited, that have links to files, the file information is correctly loaded and thus the link will be preserved
Bugfix
Fixed Import Errors when Importing from older Systems
Gentics Content.Node 5.2.4
Enhancement
Allows a custom definition of the HTML doctype that appears in the application generated HTML.
The application generated HTML wraps the HTML defined in the user-defined implementation of content pages. The application generated HTML wrapper has a doctype.Due to this circumstance, when a HTML5 doctype is defined for the user-defined implementation of a content page, the page may not display properly. As a workaround, the doctype for the application generated HTML may be configured in the node.conf configuration file in the following manner the doctype string should be equal to the one used in contentpages: $CUSTOM_NODE_HTML_DOCTYPE = '';
Please note that this will define the doctype of the wrapper-html, for all content-pages in the system, regardless of which node they belong to.
Changing the doctype might break the system or bring other problems. You might not be able to log in after changing the doctype. We do not advise to use this feature – only use this as a last resort.
Enhancement
Introduced new translation workflow feature. This feature enables the editor of pages to manage the translation tasks. A editor can for example synchronize a page. This mean the editor accepts the translation job and marks the page therefore as synchronized. A overview is provided to review the current state of all translation tasks.
Enhancement
Introduced new versioned publishing feature which will change the publishing behavior.
Before this feature was introduced the publish process would render the current version of a a page not the last published one. Example:There are two pages, a simple content page (A) and an overview page (B). The overview page contains an overview, page url, page tag or any thing else that references to the simple content page. An editor changes page (A) and will therefore modify its contents and change the current version of that page. A publisher now publishes page (B). When publishing page (B) the modified contents of page (A) will be used for rendering. This undesired behaviour could lead to unpublished content or dead links.The versioned publishing feature corrects this behaviour. Now always the last published version will be used for rendering the page.Example:Now the last published version will be used instead of the current modified contents of page (A).
The new publishing behavior will only affect pages that have been published at least one time after the feature has been enabled. The page version information has to be created before it can be used. The feature is enabled by default.
Bugfix
Fixed incorrect values displayed in tag-fill dialog.
For multiple "Tag (Page)" parts, incorrect values were sometimes displayed in the tag-fill dialog, from the second part onwards. The values that were displayed were a concatenation of the values of all previous parts. Due to the limited size of the input-box that displays a value, this made it appeart as if all parts had the same value (the first value the subsequent values being cutoff).
This bug affected how the value was displayed in the tag-fill dialog, but did not affect how the value was stored in the database.
Bugfix
Fixed language management: It is no longer possible to delete page languages, if pages with that language exist.
Bugfix
Fixed itemlist problems and adds more itemlist configuration options.Fixed: when the width of an itemlist was greater than the window size, the last column was not displayed.
Fixed: resizing a column may alter the table width, which may break the page layout.New configuration options:
Bugfix
Fixed copying pages with syncinfo: The copy will have analogous sync information set.
Bugfix
Fixed display issue of the resizeable itemlist feature. Due to a bug the last colum of the tagtype part view was not visible if one part of the tagtype contained a longer name.
Bugfix
Fixed customform_resolve_nodetags feature in the tag-fill dialogue of tag-types and templates.
Resolving node tags in custom-forms only worked in the tag-fill dialogue of content tags (pages). For template tags (templates) or tag-types, the entire custom-form was rendered as the empty string if the customform_resolve_nodetags feature was activated.Now, if the custom-form is rendered as part of the tag-fill dialogue for template tags or tag-types, all will resolve to the empty string. Special custom-form tags (e.g.
Bugfix
When the GCNAuthenticationManager was configured as a secondary authentication system, it retried unsuccessful logins to the GCN backend on every request.
Logins to the GCN backend are unsuccessful if the user authenticated with the primary authentication system doesn't have a GCN account (e.g. read-only privileges for the content in the portal, but no editing privileges in the GCN backend). Another reason may be that the GCN backend may be temporarily unavailable.
Retrying unsuccessful logins may cause performance problems if there are many users that can be authenticated with the primary authentication system but can't be authenticated with the GCNAuthentication manager each request by the user (browser) would cause an additional internal authentication request.
A configurable interval parameter “backendLoginRetryInterval” has been added to the GCNAuthenticationManager configuration, which specifies how many seconds to wait before a failed backend login request is retried.
Bugfix
Fixed inability to assign view permissions on “View permissions” tree-item.
The feature "view_perms" allows all users to see the permissions of other groups, if they have view permissions on the "View permissions" tree-item.
However, assigning view permissions on the “View permissions“ tree-item was not possible, and as such, only the “node” user was in a position to see this tree-item.
Bugfix
Fixed performance problems with too many failing backend logins.
Bugfix
Fixed assign-for-revision displays login-page.
The do-number for the assign-for-revision action was incorrectly specified.
There seems to be a certain range for do-numbers of a specific module.
Bugfix
Fixed SQL validation error that occurred when the execution-list for a task was sorted by duration.
Bugfix
Fixed possible deadlocks when publishing into contentrepositories that use Instant Publishing.
Bugfix
Fixed an erroneously reports of insufficient permissions when trying to delete pages.
When a Node had no languages assigned, and a user had the delete permission on only some, but not all folders, and the user tried to delete a page on which he had permissions, he was incorrectly informed that he didn‘t have any permissions.
Gentics Content.Node 5.1.6
Manual Change
Changes for updating Aloha Link plugin
Fixed Aloha Link plugin. It is now possible to set links to internal files. To enable linking of files the Aloha Link tagtype has to be adapted. See » Aloha Link plugin support FAQ
Enhancement
Now only pages that have the contenttype ‘text/html‘ can be edited with aloha. For other pages the editing will automatically fallback to the oldstyle editing.
Enhancement
The tagname header within the tag edit dialog will now no longer be omitted if the feature tagfill_light is activated. Otherwise the tagname can be viewed by examining the head title. (Mouseover titel)
Enhancement
Added cleanup of sizset sizcache attributes that were set by sizzle and not removed when using internet explorer with aloha editor.
Enhancement
The sizcache and sizset attributes that appeared when using the liveditor will be now be removed automatically.
Enhancement
Now templates that have only one linked folder can only be unlinked if there are no pages that reference this template. This fix was introduced to fix a bug that caused templates that were included within an export file to be hidden from the user.
Bugfix
Removed duplicate dependency that caused ClassNotFound exceptions and therefore stalled the background job tasks.
Bugfix
Fixed an issue within the import that caused imports to fail due to wrong permission check of constructs.
Bugfix
Fixed a bug that caused autoupdate to ignore the doupdate parameter. The autoupdate executed the update even if the feature was disabled via the autoupdate menu. Updates that include manual changes were not and will not be applied automatically.
Bugfix
Fixes error when using the “Assign for revision” functionality. This error was introduced when the changes made in Content Node 4 were merged into Content Node 5. In both branches identical do numbers were used for different features.
Bugfix
Fixed deletion of imports: Do not show objects, which were ignored (or copied) in the last import in the list of objects to be deleted.
Bugfix
Fixed adding of language extension to filename when updating with an empty filename and Feature “contentgroup3_pagefilename” is set.
Gentics Content.Node 5.1.4
Enhancement
Performance enhancement and fixed timeout for Live-Editor page-save.The performance enhancement concerns pages with many live-editabletags. Tests showed, that saving a page with 260 live-editable tags took35 seconds originally, which was reduced to 6 seconds if the page hadchanges, or 3 seconds if the page had no changes. The timeout-fix was made so that no timeout will occur, if saving a pageshould take longer than 30 seconds.
Enhancement
Added render messages to the Aloha settings, such that they will be logged in Aloha, when the page is rendered. The log level can be configured by setting it to log4j.logger.com.gentics.aloha in nodelog.properties.
Bugfix
Fixed NoClassDefFoundError during validation of style attributes.
Bugfix
Fixed an error (SGB) that occurs if the validation the feature is turned on and a tag is edited in the context of Gentics Portal.Node / Aloha.
Bugfix
Fixed Bug that prevented overviews to be republished when a page was published using time management and multithreaded publishing was used.
Bugfix
Removed versioned publishing, which does not work reliable.
Bugfix
Fixed ProxyServlet Exception (invalid uri / invalid query) which occurred when performing an edit operation on a content tag from Gentics Portal.Node in Aloha mode.
Bugfix
Fixed item-list column resizing in IE When certain columns in an item-list, such as the one for the name of apage, were wider than the base column width, the column was firstrendered with the correct (wider) size, but collapsed immediately to thebase column width when the mouse was moved to hover over the item-list.
Bugfix
Fixed UI issue within the tagtype edit view. If a part is defined as liveeditable the editable checkbox will be enabled as well now.
Bugfix
Fixed assistant frame. Aloha will now also add history entries to the assistant frame.
Bugfix
Fixed bug in overviews over pages, which were selected and ordered individually, that prevented correct rendering of pages.
Bugfix
Fixed Rendering of Velocity Parts: Velocity must not be rendered in edit mode. That means that if a Tag is rendered e.g. like $cms.page.tags.test or a Part is rendered via $cms.tag.parts.test it will NOT be editable. If Tags/Parts must be editable inside Tags that render Velocity, the Notation must be used (like in the pre-Aloha Era).
Gentics Content.Node 5.1.3
Manual Change
The JDK was updated
Please perform this step before performing the update of Gentics Content.Node. This change can be omitted it the installation already uses JDK 1.6.0_14. Examine the symlink /Node/java to check which jdk version is currently in use.Version 1.6.0_01 became incompatible with Gentics Content Node due tothe JAXB Library version bundled with the JDK. To update the JDK version to 1.6.0_14, please download theupdate script and execute it as a shell script. The script will ask for the Node folder (defaults to “/Node”) andwhether to use the 64bit version of the JDK (the default will be autodetected).
Enhancement
Added property .istag for objects to determine whether they are tags.
Bugfix
Fixed problem with custom streams which would not be displayed.
Bugfix
Fixed issues with page list when flapping the tree – the page list will now reclaim all available space
Bugfix
Fixes CRSync NoClassDefFound RuntimeProfiler Exception The ProfilerServlet has a dependency on HttpServlet. The servlet-api isonly on the classpath, if the RuntimeProfiler is used in the context of a webapp. A workaround is to specify the servlet-api.jar in the classpath of theCRSync command line.
Bugfix
Fixed rendering of pages that render information of other pages (like overviews, links to other pages, page-tags, ...): If the other page was modified but not yet published, the first page would publish the current data, but not the published data of the other page. This behavior has been fixed now: When a page is published and renders information of other pages, it will always get the published version of the other page.
Gentics Content.Node 5.1.2
Manual Change
(when updating from 5.0.0 or older)
If you attempt to update from Gentics Content.Node 5.0.0 or older, a special patch needs to be applied. Extract the patch file which can be downloaded (gcn5_update_patch.tgz) in /Node/.node:
Manual Change
The PHP APC cache module must be enabled.
Append the following settings to the /Node/etc/php/php.ini file.
Security
Improved security checks for serving images & files from the backend
Security
Improved various permission checks and change password mechanism
Security
Adds XSS checks for tagfill/page_save and folder/page/node/file properties. Also adds the “policy” field for TagParts.
Enhancement
Performance Improvement: parttypes are now cached, thus increasing render performance
Enhancement
Performance Improvement: improved response times for viewing and editing pages
Enhancement
Added LSB Tags for nodectl script to allow usage of dependency boot system.
Enhancement
Gentics Content.Node velocity configuration is now available to the JavaParser.
Enhancement
Setting the page language will now trigger a dirtevent for all language variants.
Enhancement
Performance Improvement: disabled output buffer for user images
Enhancement
Performance Improvement: Refactored the newline to html-break transformation of text part types. Some edge-cases of the old behaviour have been fixed. This change improves render-performance of pages in edit, preview and publish mode noticeably
Enhancement
Performance Improvement: diff between page versions will now be handled in Java, thus increasing the performance
Enhancement
Made isEditMode() and isPreviewMode() available for editing with Aloha.
Enhancement
Improved publish workflows and the page queue, which will now directly lead you to the page preview.
Enhancement
New changelog mechanism (unique change ids instead of build dates)
Enhancement
Performance Improvement: getCurrentTIme() is not called anymore if the RuntimeProfiler is not enabled
Enhancement
Performance Improvement: improved IE6 JavaScript performance by ceaning up jQuery itemlist handlers
Enhancement
Performance Improvement: added indices for id and contenttag_id to the ds_nodeversion table for improved performance
Enhancement
Automatic update mechanism adapted for new Gentics Content.Node 5 package structure
Enhancement
Feature “tagfill2” is not supported anymore – the dialog will fallback to the standard tagfill dialog.
Enhancement
New Feature: “no_userlist_on_startpage” hides user list on startpage for faster loading
Enhancement
Performance Improvement: The communication between PHP and the Java backend now happens via the native PHP Streaming API
Enhancement
Performance Improvement: content files are now served with a fingerprint instead of the current timestamp, so that the browser-cache is used more effectively
Enhancement
Switched deletion of publish directories to pure Java, so that no processes are forked anymore.
Bugfix
Fixed encoding bugs with user name.
Bugfix
Fixed a problem that caused invalid page editor assignments.
Bugfix
Fixed a problem with IE which didn‘t always show the resizable in itemlist columns.
Bugfix
Fixed possible NPE for objects without NodeObject representations like construct categories.
Bugfix
Fixed a timing problem when deleting or taking pages offline while the publish process started.
Bugfix
Fixed errors in CR browser and tagmap list
Bugfix
Fixed dependency calculations when rendering pages within other pages.
Bugfix
Fixed incorrect information in publish log about pages being written to disk even if publishing to the filesystem is disabled.
Bugfix
Fixes consistency check during a CRSync. The contentstatus table could not be created with a customized name.
Bugfix
Fixed error when uploading a new file or image.
Bugfix
Fixed incorrect prompts on clicking the cancel button in the switch template dialog.
Bugfix
Fixed XNL Function registry.
Bugfix
Fixed page-save errors if the same aloha link tag occurs more than once in a page.
Bugfix
Deletion of tagtypes is now decoupled from the browser-request, so that an aborted browser-request doesn‘t leave tags in the system, that have references to the deleted tagtype
Bugfix
Fixes JCS configuration. The cache stopped working after Gentics Portal Node was removed. This was because the system property that configured the location for the cache.ccf file did not get set by the portal node configuration setup code.
Gentics Content.Node 5.0.0
Enhancement
Added ajax gateway whitelist
Enhancement
Added GCNAuthentication do for connection with Gentics Portal.Node
Enhancement
Integrated Aloha Editor, which can be enabled via a node‘s properties.
Enhancement
Added new multi file upload
Enhancement
Unused/discontinued core modules have been removed, only system.node and content.node remain
Enhancement
Added new feature instant_cr_publishing which allows to configure contentrepositories for instant publishing: modified (publishied) objects are immediately written into the contentrepository, dependencies are handled in the publish process, like always
Enhancement
Added contentrepository option to automatically add language information to pages published into the contentrepository
Enhancement
Removed internal Portal.Node Webapp which simplifies architecture
Enhancement
Removed Todo Management (discontinued)
Enhancement
Editor‘s email adresses may now be displayed in the publish queue by enabling the feature ”pubqueue_email
Enhancement
Aloha‘s GCNIntegrationPlugin will now honor wrapper settings for each tag as the live editor did (wrapping a contenttag in div or span tags)
Enhancement
Restructured backend to honor new architecture, also resulting in a new package structure
Enhancement
Added tagfill_light feature, which will open the tagfill dialog in a lighbox instead of popups
Enhancement
Removed ImageManipulation (Aloha CropNResize plugin and the GenticsImageStore are available as a replacement for crop and resize functionality) See » CropNResize.
Enhancement
Added contentrepository option to automatically publish permission information
Bugfix
Replaced sh reference in nodectl script wich caused problems on systems without bash
Bugfix
Fix for Incorrect content-length of gzipped output
Bugfix
Fixed broken topmenu entries in tag list (save, publish) when working in Aloha mode
Bugfix
Fixed editing of object properties from Aloha mode, which would occasionally log you out
Bugfix
Fix to Handle multi-line HTTP headers correctly