Gentics Content.Node Changelog Summary

Gentics Content.Node 5.15.5


Bugfix RT57624

The GCNJSAPI has been fixed to work as documented when you try to get or set a value of a “Tag (page)” part.
Documentation on this has been clarified, too.


Bugfix RT57606

Importing of localized templates always created a conflict due to missing target folder, if the localized template did not yet exist on the target system.
Because of this, it was impossible to successfully finish the import.
This has been fixed now. For localized templates, no check for target folders is done, because localized templates are always linked to the same folders as their masters.


Bugfix RT57607

When deleting folders, localized copies of templates linked to that folder were deleted, regardless of whether the (master) template was still linked to other folders or used in pages.
This bug, which was introduced in Gentics Content.Node 5.13.25, 5.14.13 and 5.15.0 has been fixed now.


Bugfix RT57605

The SQL statements used to find reusable data files for filesystem attributes in multichannelling aware contentrepositories were inperformant and have been improved.


Bugfix RT56058

When files in the CMS lost their binary content (or were incompletely created without binary content), the publish process failed (due to missing binary data).
The display of such files in the backend was inconsistent and it was not possible to delete such files to resolve the publishing error by using the backend.
This has been fixed now, broken files that cause the publish process to fail will now be shown in the backend specially marked (with an alert icon and in red) and it is possible to delete them.
Additionally, it is now possible to search broken files using either the extended search in the backend or the REST API.


Bugfix RT56622

Removing of objects from a multichannelling aware contentrepository with instant publishing did not work. The objects were removed at the next publish run.
This has been fixed now, when instant publishing is enabled, objects will be immediately be removed unless more than one object is deleted at once.


Gentics Content.Node 5.15.4


Enhancement

Enhanced the permission page for folders (Accessed through the folders context menu)
The permissions are now directly shown for all groups for the currently selected folder.


Enhancement

Inherited content and properties are rendered in REST-API ‘render‘ call (only localized pages).
When calling /rest/page/render/{id} now it is possible to get the inherited content and the inherited properties when the parameter ‘inherited‘ is set to true.
The response then will add 2 new properties:

  • ‘inheritedContent‘: content of the inherited page
  • ‘inheritedProperties‘: properties of the inherited page

Bugfix RT57550

When selecting elements for an overview using the repository browser, the order of the already selected elements was not always shown consistently.
This has been fixed now.


Bugfix RT56031

Pausing the scheduler could take a very long time due to an inperformant SQL statement.
This has been fixed now.


Bugfix RT57596

When writing pages into the contentrepositories was slower than rendering the pages, the internal job queues could grow very big, which could cause memory problems.
This has been fixed now. If one of the queue exceeds the limit of 1000 pages, no more pages will be rendered (and put into the queue), until the queue is below the limit.


Bugfix RT56835

When using small browser windows (e.g. on systems with low resolutions), some data shown on the startpage of the CMS could overlap each other.
This has been fixed now. If the window is too small to show the info boxes side by side the boxes will be shown one on top of the other.


Bugfix RT57556

A minor issue in the autoupdate feature was fixed. Additional protection checks were added to prevent multiple autoupdate invocations.


Bugfix RT57212

When loading the binary contents of a file via the REST API by using /rest/file/content/load/{id} the response always had the ‘Content-Type‘ ‘application/octet-stream‘.
This has been changed now, the response to /rest/file/content/load/{id} will now have the correct ‘Content-Type‘ set.


Bugfix RT53165

When part of type “URL (Page)“ was set to be required in the tagtype, the tagtype itself could not be filled without providing a default value for that part.
This behaviour was different than the behaviour for other parts (e.g. type “Text”) where the part only has to be filled for tags, but not for the tagtype itself.
The behaviour has been changed now to be consistent for all part types: If a part is required, it still can be left empty for the tagtype, but has to be filled in tags (e.g. in pages).


Bugfix RT57297

A bug in the scheduler view was fixed. Previously no error message was being displayed when the user was trying to delete a scheduler task that still got tasks that depended upon it. This issue has now been resolved.


Bugfix RT57590

On some systems the Regex.Admin view did not display properly. A security check prevented the correct rendering of the view. The check has been adapted and the view will now render correctly.


Gentics Content.Node 5.15.3


Security RT54513

Rest API: Removed the “description“ and “login” field for all responses that return user objects (ie. creator and author)
However, methods in the UserResource will still output those two fields for user objects.


Security RT54513

Previously, when an error occured while requesting a page from Tomcat (404 or 500), the Tomcat version number and a detailed message was shown.
That information is now hidden (a static error page is shown). Detailed error output can be found in the log files.


Security RT54513

Fixed security issue that could possibly allow someone to take over your user account by sending you an URL and doing social engineering.


Bugfix RT57386

When creating folder overviews by manually selecting the folders and having the “recursive“ flag activated, the subfolders were not added, if the feature multichannelling was activated.
This has been fixed now, manual folder overviews with “recursive” activated will now render like expected.


Bugfix RT57434

When migrating tags from a tagtype that contained non-editable parts using the tagtype migration tool, the filled value of the non-editable part in the source tagtype was removed, which should not happen.
This has been fixed now. When migrating tags the source and target tagtypes are not changed.


Bugfix RT57499

When the action “check data“ or “repair data“ for a ContentRepository was started, the status changed to “Running“, even though the job was actually queued (along with other dirt or maintenance events or even the publish process).
This has been changed now. The status will now show “Queued“ as long as the job is in the Queue and will only switch to “Running“ when the job really is started.
Additionally, queued ContentRepository jobs will now be shown as “ContentRepository Maintenance Action“ instead of “Dependency Calculation” in the maintenance dialog.


Bugfix RT57387

Moving of inherited or localized folders is not allowed, because they must be moved in their master node. If an editor tried to move a localized or inherited folder,
nothing happened, but the editor got no information telling why.
This has been fixed now: If an editor tries to move an inherited or localized folder, an information will be displayed that this is not possible (similar to moving pages, images or files).


Bugfix RT57495

When editing tags as blocks using Aloha Editor and the tagtype implementation contained script tags and a jQuery version >= 1.9.0 was used,
the script tags were replaced by some random numbers when the tag was re-rendered in the page after being modified using the tagfill dialog.
These numbers were not saved to the page and did not affect the published content of the page, but were just shown while editing the page.
This has been fixed now, re-rendering tags containing script tags will now also work with jQuery versions >= 1.9.0.


Gentics Content.Node 5.15.2


Enhancement

Documented tag icon rendering for node style syntax.


Bugfix RT55037

Ordering the file or image list by file size works now correctly.


Bugfix

Diagonal resizing in the MiniBrowser works properly now.
The diagonal resizing region was very small and therefore very difficult to select.


Bugfix RT56720

The action “Delete (only this language)“ on pages has been removed for nodes with no languages assigned, for it does nothing.
You can use “Delete (all languages)“ instead.
For pages that have no language set, although the node has languages assigned, the action “Delete (only this language)” will now delete the page.


Bugfix RT57368

Multichannelling: Fixed the mother_obj_id of a folder not getting updated in the CR when the mother folder gets localized.


Bugfix RT57371

Email sending: Fixed deleted user receiving notification emails from GCN
Now deleted users don‘t receive notification emails anymore.


Bugfix RT57259

Sending messages to groups using the GCN Javascript API did not work at all and has been fixed.


Bugfix RT57329

Executing the command ‘Change Template‘ on page variants failed with an error, which has been fixed now.
When changing the template for multiple pages at once, the pages will now be processed one by one so changes to every single page will now be visible immediately.


Bugfix

When pages were dirted due to changed dependencies, this was not logged any more.
This has been fixed now: when a page is dirted, an entry in the logcmd table will be made.


Bugfix RT57435

Previously, if you translated a page using the page/translate REST-API call, it would create excessive language versions of the same language if the master page was not located in a master node.
Now, the page/translate call will not create multiple language variants of the same language any more.


Bugfix RT57460

The dirting mechanism has been slightly changed to avoid changes to the page table.
This will avoid unnecessary locks of the page table that could cause errors while pages are edited during a long running dirt process.


Gentics Content.Node 5.15.1


Bugfix RT57442

When resizing images during a publish run using the GenticsImageStore, some file handles were not closed. This subsequently could cause publish run failures caused by a “too many open files” error.
This has been fixed now, file handles will now immediately be closed after usage.


Gentics Content.Node 5.15.0


Manual Change

Permission settings, that were set on channels (root folders of channels) will not be effective any more.

Permission settings on channels will now always be inherited from the master node, even for the root folder of the channel.
In order to restrict user access to specific channels, the assignment of the user to the group granting this permissions has to be restricted to the channels.

More information about restricting user-group assignments to nodes can be found in the Gentics Content.Node Guides


Enhancement

The performance for checking permissions especially to build the folder tree has been improved.

  • Permission entries with all permission bits set to 0 will no longer be stored in the database, which reduces the size of the perm table.
  • Checking the permissions will now be done using the REST API and will not access the perm table. All permission entries will be kept in the memory of the JVM. The memory consumption will be about 40 byte per perm entry (not counting the entries having all 0s). The database is only accessed, when permissions change.

Enhancement RT57003

The following meta attributes have been added for Velocity and the node notation:

Node:

  • https
  • master
  • utf8
  • alohaeditor

Check out the documentation for more information.


Enhancement RT56173

Various enhancements have been made to the repository browser.
Resizing the repository browser now works.


Enhancement RT57304

Improvements have been to the repository browser UI.
The way that notifications are shown when an item is selected with the
resopsitory browser has also been be replaced with a better implemenation, and
improved UI.


Enhancement

The error log now shows all errors – displaying errors as “internal errors” has been removed.
Also, additional data like the request query string and the user is displayed if available.


Enhancement RM10457

The feature “always_localize” has been introduced. It allows you to skip the dialogue that asks, whether
Gentics Content.Node should localize an inherited object before editing or just edit the inherited object.
If it is skipped, the default answer is to localize. If the feature is enabled in your node.conf, You can
configure it separately for every node in the Node Features menu.


Enhancement

The permission system has been enhanced to allow restricting user-group assignments to specific nodes/channels.
This allows granting permissions to specific channels, without granting the permissions to other channels or the master node of the same channel structure.

More information about restricting user-group assignments to nodes can be found in the Gentics Content.Node Guides