Gentics Content.Node 5.23.35
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-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 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-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-3997
Copying a Node could fail with a NullPointeException. This has been fixed.
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-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.23.34
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-3301
Fixed the permissions “Create / edit tagtype“ and “Channel sync“ for the “GCN5 Demo” node not being set for the node group.
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.
Gentics Content.Node 5.23.33
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-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-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-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.
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.
Gentics Content.Node 5.23.32
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-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>">
Bugfix SUP-3897
Some inefficient SQL statements for updating data from the tagfill dialog have been improved.
Gentics Content.Node 5.23.31
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-3830
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.
Bugfix SUP-3811
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.
Bugfix SUP-3819
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.
Bugfix SUP-3849
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.
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: “ Files that were imported from a thirdparty media asset system using the 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. 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. When publishing files into a ContentRepository, errors like 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 a tag in a page is filled with the tagfill dialog, and a part of type Applying object properties of folders to subfolders did not work for channel local or localized folders and has been fixed now. The Part Types documentation has been updated. 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 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. 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. Showing the tag status failed with an SGB for templates that contain tags with special characters (like Two issues with the feature 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 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 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. 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. 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. 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 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. 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. 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. Some minor issues with the detection of GCMS version numbers from local updatefiles have been fixed. 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. 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. 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. The default upload folders for images and files could not be unset, once they were set. 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 The script 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 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. When a tagtype contained multiple parts of type 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. 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. Purging the wastebin from many deleted folders consumed a big amount of memory, which could cause OutOfMemory errors. This has been fixed now. 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. When the feature When the type of a part in a construct was changed from 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. 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. 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. 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 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. 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 link was removed in a page, the corresponding link tag was not deleted when the page was saved. This has been fixed. 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. 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. 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 Fixed the top menu not changing, after viewing/editing a content page and changing to another CMS page with the assistant. When the feature 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. 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. 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. 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. When using the GCN JS API to create tags in pages as copy of other tags, the callback passed to the function 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. 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. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. 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. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which has been fixed now. 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 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 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. 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 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. Rest API: Fixed a bug in the auth/validate method where a session with ID -1 was considered as valid. 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 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. The activiti integration has been improved: 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. The constraint expression in the Activiti configuration was not evaluated in the scope of the triggering object‘s channel. 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. 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. 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. 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 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. When the channel directive 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. 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 cache for node objects can now be individually configured for object type. See the Guides for details. 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 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. 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. 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. Installation: Enhanced the database import script to be more bulletproof. The publish statistics for rendering pages have been improved to distinguish between rendering content and rendering other attributes. 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. 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. 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. 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. 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. 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. 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. 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. PLinks with attributes other than 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 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. The REST API has been extended: If the feature Enhanced REST endpoint The endpoint 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. 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: A new Velocity directive The new Part Type “Node” allows selection of a Node. Installation Package: Correctly install and enable nodectl service. The REST endpoints The presence of certain query parameters for the REST endpoint
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-3858
Gentics Content.Node 5.23.30
Bugfix SUP-3808
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-3780
Bugfix SUP-3679
Gentics Content.Node 5.23.29
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.
Bugfix SUP-3775
Gentics Content.Node 5.23.28
Documentation SUP-3719
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-3614
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-3434-). 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-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.
Gentics Content.Node 5.23.24
Installations using the Activiti Integration need to have the Activiti Server updated to get those fixes.
Bugfix SUP-3268
Bugfix SUP-3576
Bugfix SUP-3568
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-3551
Bugfix SUP-3212
Bugfix SUP-3212
Bugfix SUP-3551
Bugfix SUP-3556
Gentics Content.Node 5.23.22
Bugfix SUP-3527
Bugfix SUP-3378
Bugfix SUP-3367
Bugfix SUP-3347
Bugfix SUP-3478
Bugfix SUP-3514
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-3491/Node/bin/nodectl sometimes showed an error when stopping Tomcat, although stopping finally worked. This has been fixed now.
Bugfix SUP-3324
Bugfix SUP-3503
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-3334
Gentics Content.Node 5.23.21
Gentics Content.Node 5.23.20
Documentation SUP-2106
Bugfix SUP-3457
Bugfix SUP-3354
Bugfix SUP-3320
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”.
Gentics Content.Node 5.23.19
Gentics Content.Node 5.23.18
Bugfix SUP-3283
Bugfix SUP-3392
Bugfix SUP-3405
Bugfix SUP-3274
Bugfix SUP-3329
Bugfix SUP-3424
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-3230
Bugfix SUP-3196
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-2790
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-2768
Bugfix SUP-3091
Bugfix SUP-3090
Bugfix SUP-3087
Bugfix SUP-3093
Bugfix SUP-2637createTag was in some cases not called. This has been fixed now.
Bugfix SUP-2917
Bugfix SUP-3099
Bugfix SUP-2719
Gentics Content.Node 5.23.12
Documentation SUP-3028
Bugfix SUP-2587
Bugfix SUP-2902
Bugfix SUP-3024
Bugfix SUP-3024
Bugfix SUP-3020
Bugfix SUP-2927
Bugfix SUP-3037
Bugfix SUP-2789
Bugfix SUP-2995
Bugfix SUP-3066
Bugfix SUP-3024
Bugfix SUP-2985
Bugfix SUP-3003
Gentics Content.Node 5.23.11
Bugfix SUP-2967
Bugfix SUP-2549
Bugfix SUP-2968
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-2162
Bugfix SUP-2829
Bugfix SUP-2704
Bugfix SUP-2620
Bugfix SUP-2620
Bugfix SUP-2860
Gentics Content.Node 5.23.8
Bugfix SUP-2594
Bugfix SUP-2863
Bugfix SUP-2877
Bugfix SUP-2833
Bugfix SUP-2810list method of the REST API. This has been fixed now.
Gentics Content.Node 5.23.7
Bugfix SUP-2810
Bugfix SUP-2233
Gentics Content.Node 5.23.6
Bugfix SUP-2816
Bugfix SUP-2794
Also a typo in the configuration examples has been fixed.
Bugfix SUP-2683
Gentics Content.Node 5.23.5
Documentation SUP-2577
Bugfix
Bugfix SUP-2775
Bugfix SUP-2750
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-2731
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).
Bugfix SUP-2783
Bugfix SUP-2776
Bugfix SUP-2728
Bugfix SUP-2634
Bugfix SUP-2728
Gentics Content.Node 5.23.4
Bugfix SUP-2736
Bugfix SUP-2730
Bugfix SUP-2736
Gentics Content.Node 5.23.3
Bugfix
Bugfix SUP-2718
Bugfix SUP-2717
Bugfix SUP-2702
Bugfix SUP-2714
Bugfix SUP-2717
Bugfix SUP-2721
Gentics Content.Node 5.23.2
Documentation SUP-2698
Documentation SUP-2664
Bugfix SUP-2635
Gentics Content.Node 5.23.1
Bugfix SUP-2376
Bugfix id were not processed properly by the Aloha renderer which could cause problems with front end editing. This has been fixed.
Bugfix SUP-2419
Gentics Content.Node 5.23.0
Enhancement
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 SUP-37
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 #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
Bugfix SUP-1632
Bugfix /node/create and /node/save/{id} ignored the languagesId field. This has been fixed.
Bugfix /user/list could cause the request to fail. This has been fixed.