Gentics Content.Node 5.24.31
Documentation SUP-4625 Link to this entry
Improved translation for documentation of breadcrumb part type.
Documentation SUP-3892 Link to this entry
A description for the feature tagfill_light
has been added to the Guides
Documentation SUP-4069 Link to this entry
The description for mounting a folder via WebDAV has been updated. Please note that the WebDAV feature is deprecated.
Bugfix SUP-4235 Link to this entry
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-4545 Link to this entry
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-4000 Link to this entry
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.
Bugfix SUP-4017 Link to this entry
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-4492 Link to this entry
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 Link to this entry
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-4110 Link to this entry
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.
Gentics Content.Node 5.24.29
Bugfix SUP-4274 Link to this entry
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-4360 Link to this entry
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-4372 Link to this entry
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-4358 Link to this entry
Fixed an error in the REST API, which could lead to recurrent NullPointerExceptions.
Bugfix SUP-4430 Link to this entry
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.
Gentics Content.Node 5.24.28
Bugfix SUP-4193 Link to this entry
Fixed logging in not working for IPv6 HTTP clients.
Gentics Content.Node 5.24.27
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.
Link to this entryOptional 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.
Link to this entry
Bugfix SUP-4108 Link to this entry
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 Link to this entry
Under special circumstances, the URL to translate a page could lead to an SGB. This has been fixed now.
Bugfix SUP-3980 Link to this entry
Logged rendering errors will now include more specific information, which object was rendered when the error occurred.
Gentics Content.Node 5.24.26
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.
Link to this entryThis 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-4079 Link to this entry
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-4082 Link to this entry
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-4111 Link to this entry
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.
Bugfix SUP-4081 Link to this entry
Some icons in the CMS UI were missing tooltips, which have been added now.
Gentics Content.Node 5.24.25
Documentation SUP-4006 Link to this entry
Added MySQL 5.7 to the list of tested database systems in the compatibility documentation.
Documentation SUP-4037 Link to this entry
Added missing documentation for the getItems method in FolderResource.
Bugfix SUP-3997 Link to this entry
Copying a Node could fail with a NullPointeException. This has been fixed.
Bugfix Link to this entry
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-3914 Link to this entry
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.
Bugfix SUP-3991 Link to this entry
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 Link to this entry
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-3543 Link to this entry
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 Link to this entry
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.
Gentics Content.Node 5.24.24
Documentation SUP-3952 Link to this entry
A page with details on the “ExpressionParser for TagMap Entries” has been added to the documentation.
Documentation SUP-3934 Link to this entry
Added missing documentation on how to setup support for Oracle or SQL-Server Content Repositories in the CMS.
Bugfix SUP-3301 Link to this entry
Fixed the permissions “Create / edit tagtype“ and “Channel sync“ for the “GCN5 Demo” node not being set for the node group.
Bugfix SUP-3926 Link to this entry
The permission checks for some rarely used administrative functions have been improved.
Bugfix SUP-3915 Link to this entry
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.
Gentics Content.Node 5.24.23
Bugfix SUP-3867 Link to this entry
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-3873 Link to this entry
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-3591 Link to this entry
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-3871 Link to this entry
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-3832 Link to this entry
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-3908 Link to this entry
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-3876 Link to this entry
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.
Gentics Content.Node 5.24.22
Enhancement SUP-3699 Link to this entry
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 Link to this entry
The documentation of imps has been improved in the Gentics CMS Guides
Bugfix SUP-3725 Link to this entry
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-3878 Link to this entry
Some german umlauts were wrongly encoded. This bug only affected the cms webinterface. This has been fixed.
Bugfix SUP-3857 Link to this entry
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 Link to this entry
Some inefficient SQL statements for updating data from the tagfill dialog have been improved.
Gentics Content.Node 5.24.21
Documentation SUP-2680 Link to this entry
Updated documentation to avoid a common mistake in velocity implementions from tagtypes that are editable with the aloha editor.
Bugfix SUP-3811 Link to this entry
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-3849 Link to this entry
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-3601 Link to this entry
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-3819 Link to this entry
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-3837 Link to this entry
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-3858 Link to this entry
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.
Bugfix SUP-3797 Link to this entry
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 Link to this entry
Fixed issue where corrupted node-tags (node-notation without tagname and closing bracket: “ 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. 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. 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 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. 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 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. When publishing multiple nodes (with their channels) into the same Multichannelling aware ContentRepository, the ContentRepository Maintenance action 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 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. When the feature Two issues with the feature The script 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 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. 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. 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 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. 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. 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. 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. 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 tagtype contained multiple parts of type 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. When a folder was moved into another folder with more restrictive inheritance settings (in a multichannelling environment), and the moved folder 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. The default upload folders for images and files could not be unset, once they were set. This has been fixed now. 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 script 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 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. 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 the type of a part in a construct was changed from When using the feature 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. 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. 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. 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 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 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 a link was removed in a page, the corresponding link tag was not deleted when the page was saved. This has been fixed. 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. 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. 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. 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 using the Feature 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 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. 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 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 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. In some cases, an additional tag was automatically added to rendered page sources, containing a Gentics Copyright notice. This has been removed now. Fixed the top menu not changing, after viewing/editing a content page and changing to another CMS page with the assistant. When the feature 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. 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. 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. 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 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 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. Under special circumstances, the dependency calculation for a modified node or folder could fail with a NullPointerException, which 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. 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. The tagfill dialog still showed the names of referenced objects, even if they were put into the wastebin. 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 scheduler will now show more detailed information (the complete stacktrace with causing exceptions), when the publish run fails with an exception. 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. 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. 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 scheduler can start Activiti processes now. Please read the documentation for more information. 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 “cancel” option to throw away all changes done to a page is now also available in the assistant frame. 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 new feature Attribute Dirting can reduce publish times when publishing into Content Repositories by only dirting and rendering attributes, that depend on changed data. Rest API: The FolderResource now supports sorting by the deletion date and the full user name who deleted an object (wastebin feature). The list in the wastebin view is now sortable by name, deletion date and user who deleted the object.
Bugfix SUP-3830 Link to this entry
Gentics Content.Node 5.24.20
Bugfix SUP-3679 Link to this entry
Bugfix SUP-3743 Link to this entry
com.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 Link to this entry
Bugfix SUP-3808 Link to this entry
Gentics Content.Node 5.24.19
Bugfix SUP-3752 Link to this entry
URL (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 Link to this entry
Gentics Content.Node 5.24.18
Documentation SUP-3719 Link to this entry
Bugfix SUP-3739 Link to this entry
Clean 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.
Bugfix SUP-3614 Link to this entry
Bugfix SUP-3724 Link to this entry
span
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.
Gentics Content.Node 5.24.17
Bugfix SUP-3655 Link to this entry
Gentics Content.Node 5.24.16
Bugfix SUP-3690 Link to this entry
Gentics Content.Node 5.24.15
Documentation SUP-3625 Link to this entry
Bugfix SUP-3636 Link to this entry
Bugfix SUP-3619 Link to this entry
activiti_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-3605 Link to this entry
objprop_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-3443 Link to this entry
/Node/.node/setup-database.php
for resetting the database will now set an exit status != 0 when it fails.
Bugfix SUP-3434 Link to this entry
-
). 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-3268 Link to this entry
Bugfix SUP-3576 Link to this entry
Bugfix SUP-3568 Link to this entry
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 Link to this entry
Bugfix SUP-3212 Link to this entry
Bugfix SUP-3551 Link to this entry
Bugfix SUP-3212 Link to this entry
Bugfix SUP-3551 Link to this entry
Gentics Content.Node 5.24.12
Bugfix SUP-3367 Link to this entry
Bugfix SUP-3527 Link to this entry
Bugfix SUP-3378 Link to this entry
Bugfix SUP-3347 Link to this entry
Bugfix SUP-3435 Link to this entry
URL (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-3478 Link to this entry
Bugfix SUP-3503 Link to this entry
Bugfix SUP-3501 Link to this entry
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-3324 Link to this entry
Bugfix SUP-3514 Link to this entry
Bugfix SUP-3334 Link to this entry
Bugfix SUP-3491 Link to this entry
/Node/bin/nodectl
sometimes showed an error when stopping Tomcat, although stopping finally worked. This has been fixed now.
Gentics Content.Node 5.24.11
Gentics Content.Node 5.24.10
Documentation SUP-2106 Link to this entry
Bugfix SUP-3441 Link to this entry
activiti_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-3320 Link to this entry
Bugfix SUP-3457 Link to this entry
Bugfix SUP-3354 Link to this entry
Bugfix SUP-3413 Link to this entry
Select (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-3458 Link to this entry
attribute_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.
Gentics Content.Node 5.24.9
Gentics Content.Node 5.24.8
Bugfix SUP-3424 Link to this entry
Bugfix SUP-3329 Link to this entry
Bugfix SUP-3283 Link to this entry
Bugfix SUP-3392 Link to this entry
Bugfix SUP-3274 Link to this entry
Bugfix SUP-3405 Link to this entry
Gentics Content.Node 5.24.7
Bugfix SUP-3246 Link to this entry
Bugfix SUP-3190 Link to this entry
Bugfix Link to this entry
Bugfix Link to this entry
Gentics Content.Node 5.24.6
Bugfix SUP-3260 Link to this entry
Gentics Content.Node 5.24.5
Bugfix SUP-3275 Link to this entry
Gentics Content.Node 5.24.4
Bugfix SUP-3193 Link to this entry
attribute_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 Link to this entry
Bugfix SUP-3196 Link to this entry
Gentics Content.Node 5.24.3
Documentation Link to this entry
Bugfix SUP-3106 Link to this entry
/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-3176 Link to this entry
dskeepselectvalues
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.
Bugfix SUP-3134 Link to this entry
Gentics Content.Node 5.24.2
Bugfix SUP-2768 Link to this entry
Bugfix SUP-3093 Link to this entry
Bugfix SUP-2637 Link to this entry
createTag
was in some cases not called. This has been fixed now.
Bugfix SUP-3087 Link to this entry
Bugfix SUP-3091 Link to this entry
Bugfix SUP-3090 Link to this entry
Bugfix SUP-3099 Link to this entry
Bugfix SUP-2790 Link to this entry
Bugfix SUP-3107 Link to this entry
activiti_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-2917 Link to this entry
Bugfix SUP-2719 Link to this entry
Gentics Content.Node 5.24.1
Documentation SUP-3028 Link to this entry
Bugfix SUP-3024 Link to this entry
Bugfix SUP-3024 Link to this entry
Bugfix SUP-3066 Link to this entry
Bugfix SUP-2927 Link to this entry
Bugfix SUP-3020 Link to this entry
Bugfix SUP-3024 Link to this entry
Bugfix SUP-2995 Link to this entry
Bugfix SUP-2789 Link to this entry
Bugfix SUP-2902 Link to this entry
Bugfix SUP-3037 Link to this entry
Bugfix SUP-2587 Link to this entry
Bugfix SUP-3003 Link to this entry
Bugfix SUP-2985 Link to this entry
Gentics Content.Node 5.24.0
Enhancement GTXPE-4 Link to this entry
Enhancement Link to this entry
Enhancement GTXPE-10 Link to this entry
Enhancement Link to this entry
Enhancement GTXPE-11 Link to this entry
Enhancement GTXPE-14 Link to this entry
Enhancement Link to this entry
Enhancement GTXPE-16 Link to this entry
Enhancement GTXPE-16 Link to this entry