Gentics Content.Node Changelog Summary

Gentics Content.Node 5.19.11


Security SUP-323

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.


Security SUP-323

The permissions of object properties are now also respected by the GCN Rest API when loading or saving objects.


Bugfix SUP-480

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).


Bugfix SUP-370

REST-API: When copying a contenttag, using page/newtag, the operation would fail for some content tags.


Bugfix SUP-187

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.


Bugfix SUP-456

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.


Bugfix SUP-187

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:

  • Locking the page for editing
  • Saving a page (with or without changes)
  • Publishing a page

Bugfix SUP-434

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.


Bugfix SUP-434

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.


Bugfix SUP-187

The process of saving a page has been optimized to avoid unnecessary checks, if only content, but no metadata was changed.


Bugfix SUP-323

Fixed object properties not being deleted, when passing their name in the “delete” list of the PageResource.save Rest API method.


Bugfix SUP-479-SUP-488

Changed Contentrepository DB connection pool to be more resilient in cases of reset DB Connections.


Bugfix SUP-387

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.


Bugfix SUP-473

Fixed output of error log message caused by debug output when rendering tags for publishing.


Bugfix SUP-418

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.


Bugfix SUP-530

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.


Bugfix SUP-401

When editing a page with Aloha Editor, the following editing actions would lead to unexpected behaviour:

  • Remove a tag from an editable, where the tag itself contains an editable
  • Create a new tag of the same type in the editable in a way, that the new tag would get the same name as the one deleted before
  • Open the tagfill dialog to fill some data into the new tag
  • Close the tagfill dialog with the “Ok” button
  • Reopen the tagfill dialog of the new tag

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.


Gentics Content.Node 5.19.9


Bugfix SUP-450

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.


Bugfix SUP-428

For images having the mimetype “image/x-png” no thumbnails were generated in the backend, which has been fixed now.


Bugfix SUP-306

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.


Bugfix SUP-454

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.


Bugfix SUP-309

Some problems with copying or importing templates in the backend have been fixed:

  • When a template was copied into a folder of a node (not a channel), it was internally marked as belonging to a channel. This could subsequently lead to erros during the publish process.
  • When templates that were incorrectly bound to a channel were exported and imported into another system,
    they were incorrectly bound to a channel on the target system as well.
  • When a template was copied into the same folder in a channel, it was copied into the master instead.

This update will also correct incorrectly bound templates in the database.


Bugfix SUP-407

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.


Gentics Content.Node 5.19.8


Bugfix SUP-307

Copying a tagmap entry between contentrepositories would fail unconditionally.


Bugfix SUP-278

Comparing Page Versions did not work correctly with Pages in localized Folders. This has been fixed.


Bugfix SUP-361-SUP-364

Connections from the database connection pool are now tested before being used.


Bugfix SUP-226

Fixed a NullpointerException when importing a page that could occur under rare circumstances.


Bugfix SUP-310

Copying of nodes was broken due to some classes, that were removed but still referenced in an internal configuration. This has been fixed now.


Bugfix SUP-56

Multiple bugs fixed in page publishing:

  • page.languages now only returns online pages during publishing.
  • References to non-published language variants would be added in the content repository. Now, only online language variants get references in the content repository.
  • References to deleted pages would not get removed from the content repository. The fix adds dependencies for referenced pages. Affected pages must be re-published for the problem to be solved.

Gentics Content.Node 5.19.7


Bugfix SUP-297

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.
This i18n support task was redesigned in order to avoid such problems in the future.


Bugfix SUP-285

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.


Gentics Content.Node 5.19.6


Documentation SUP-170

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.


Bugfix SUP-174

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.


Bugfix SUP-269

Improved logging output in context of an inconsistency in multichanneling when a localized object does not have a master object.


Bugfix SUP-137

Sometimes, the tree shown to select the target folder for copying pages was rendered incompletely. This has been fixed now.


Bugfix SUP-243

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.


Bugfix SUP-46

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.


Gentics Content.Node 5.19.5


Bugfix SUP-42

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.


Bugfix SUP-98

Creating a page variant in multichannelling environments with localized language versions would sometimes fail or introduce consistency problems to the newly created page variant.


Gentics Content.Node 5.19.4


Bugfix SUP-164

Fixed possible NPE when checking data in contentrepositories


Bugfix SUP-73

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.


Bugfix SUP-59

Fixed documentation of AuthenticationResource to describe the proper parameters for the validate method.


Gentics Content.Node 5.19.3


Bugfix SUP-77

Fixed potential inheritance restriction consistency problem when moving pages between channels.


Bugfix SUP-84

SVG images could not be exchanged in the image properties page. This has been fixed.


Bugfix RT58702

The generation and internal storage of global IDs in the backend database has been changed:

  • global IDs are no longer stored in a separate table ‘mappedglobalid‘, but are stored in columns ‘uuid‘ of the tables, that need to have global IDs
  • new generated global IDs will be constructed as [globalprefix].[UUID] where [globalprefix] consists of the first four characters of the systems license key and [UUID] is a UUID
  • The tables ‘mappedglobalid‘ and ‘mappedglobalidsequence‘ are no longer needed and are dropped (after the relevant data is migrated to the columns [table].uuid

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).
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:

  • Inserting into a very large table mappedglobalid could cause performance problems affecting the whole system (due to locks)
  • Separation of global IDs from the data records could easily lead to inconsistencies
  • If an older version of table mappedlobalidsequence was restored (e.g. from a backup), already existing global IDs could be re-generated. This could lead to problems if data from the state before restoring the backup was exported.
  • Different systems using the same license key would create identical global IDs, belonging to different objects. Since global IDs basically are UUIDs the chance of duplicates is minimal.

However, there are some drawbacks:

  • It is not possible to import data into a system with the old global IDs (that does not have this change), if the data was exported from a system with the new global IDs.
  • Migrating the existing data might take a while (but of course this is only done once).

Bugfix SUP-88

Fixed possible NPE when saving pages containing empty overviews


Bugfix SUP-76

Deleting one or more files caused an error if a workflow is activated that moves deleted files to another folder. This has been fixed.


Bugfix RT58761

REST-API: Removed unused “folder” field from FolderCreateRequest. This prevents a JsonMappingException in the Java REST client.


Bugfix SUP-77

Moving files/images across channel trees would always return an error message.


Bugfix SUP-78

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.
Example:

  • Folder A is moved from the master node to a channel (of the same master node).
  • Page B in Folder A, which belonged to the master node is also moved to the channel (because it cannot belong to the master, when the folder does not belong to the master).
  • Page C in Folder A, which belonged to the channel is not moved (already belongs to the target channel).
  • Page D in Folder A, which belonged to a subchannel is also not moved, because it does not violate the channel integrity.

Bugfix RT58697

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.


Bugfix RT58739

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.


Bugfix RT58618

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.


Gentics Content.Node 5.19.2


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.
Please note that is change is optional and can be omitted.


Documentation RT58712

Corrected paths for cleaning up unneccesary directories when performing the RHEL GCN package migration


Bugfix RT58735

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.


Gentics Content.Node 5.19.1


Bugfix RT58617

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.


Bugfix RT58672

The memory consumption of the timetrigger script (used for time based workflows) has been reduced.


Bugfix RT58651

The assignment of languages to nodes was imported with the language, but not with the node:

  • if only the language was imported (without nodes), the node assignment was modified to match the assignment of the source system
  • if only the node was imported (without languages), the language assignment was not modified
  • if a new node was imported, that had a new language assigned, the language was not assigned to the node

The behaviour has been changed now, so that the language assignment is changed, when the node is imported.


Bugfix RT58713

Fixed curl printing debug output to error.log when the PHP curl extension is enabled.


Gentics Content.Node 5.19.0


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.


Aloha Editor Change Summary
The Aloha Editor textcolor plugin now allows you to set the background-color of text.
See the Aloha Editor Changelog for detailed information.


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;


Feature RT58656

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.


Feature RT58501

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.


Enhancement KB2089

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.


Enhancement KB2089

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.


Enhancement KB2086

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.


Enhancement

The REST API has been extended:

  • /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 RT58648

Added a new default blue Gentics stream for the login mask and the top header background.


Enhancement

The feature “multichannelling” has been enhanced, so that the inheritance of objects can now be configured.

  • Objects can be excluded from inheritance
  • Objects can be removed from selected channels

Please consult the Gentics Infoportal for further details.


Bugfix RM14644

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.