Changes with Gentics Content.Node 5.31.10

Date: 06.08.2018

Bugfix SUP-6523 🔗 Link

Tagmap entries with the same name but for different object types would be shown as “inconsistent“ if they were different in attributes, which had no relevance for the entry type (e.g. different targetType setting for entries of type “text“). This resulted in “conflicts” which could not be resolved and has been fixed now.

Bugfix SUP-6673 🔗 Link

Excluding CR Fragments from export by type did not work (Fragments were still exported). This has been fixed now.

Bugfix SUP-6337 🔗 Link

Copying tagmap entries into other ContentRepositories will now check for duplicates (same mapname and type) and will either ignore or overwrite the tagmap entries.

Bugfix SUP-6539 🔗 Link

When a new node with the flag for publish directory segments enabled was imported, the publish directory segment of the root folder possibly contained slashes. This has been fixed now.

Bugfix SUP-6615 🔗 Link

The field for elasticsearch settings of new ContentRepository Fragment entries was always prefilled with “null”. This has been fixed now.

Bugfix SUP-6337 🔗 Link

Copying of tagmap entries did not work any more and has been fixed.

Bugfix SUP-6235 🔗 Link

When loading a template over the REST API with a given nodeId, the list of objecttags in the template will now be restricted to the objecttags, which are either globally available or assigned to the node.

Bugfix SUP-6640 🔗 Link

The publish process failed with an error like “Duplicate field name for field … detected. The name for a field must be unique.” if the Mesh ContentRepository contained identical entries coming from different CR Fragments. This has been fixed now.

Bugfix SUP-6725 🔗 Link

Devtool packages, which are created as symbolic links are not automatically detected. Directories with names starting with ‘.‘ (like ‘.git‘, ‘.svn‘, ...) are no longer detected as devtool packages. It is also no longer possible to create a package over the UI or REST API with a name starting with ‘.‘.

Bugfix SUP-6439 🔗 Link

Synchronizing template tags with pages behaved inconsistently: Missing tags were only added to pages, which also contained tags that needed to be migrated (because they used different constructs). This has been fixed now, when synchronizing template tags with pages, this will:

  • Create missing tags
  • Migrate existing tags to the construct used in the template
  • Remove superfluous tags (tags that came from the template, but no longer exist in the template or are no longer editable in pages)

Synchronization of template tags with pages can be triggered via

  • Template|Tag list (Action sync with pages)
  • Template|Define tags (Button Apply and sync with pages)
  • Template|Tagstate (Button sync with pages)

Bugfix SUP-6675 🔗 Link

Adds extra validity checks and uniqueness on breadcrumbs creation.

Bugfix SUP-5480 🔗 Link

Sometimes, when updating the binary contents of files, some temporary files could be left over in the folder /Node/tomcat/temp This has been fixed now.

Bugfix SUP-5404 🔗 Link

Changes made on object property definitions were not automatically synchronized to devtool packages, even when the automatic sync was enabled. This has been fixed now.

Bugfix SUP-6325 🔗 Link

When an import changed only tags of a template, but no properties of the template itself (like the name or source), the editor and edate of the template were not modified. This has been fixed now.

Bugfix SUP-6227 🔗 Link

When copying a ContentRepository, some attributes were not copied:

  • Elasticsearch Setting of ContentRepository
  • Flag for Instant Publishing
  • Flag to add Language Information
  • Flag to add Permission Information
  • Flag for “Project per Node” (Mesh ContentRepository)
  • Permission Property (Mesh ContentRepository)
  • Elasticsearch Setting of Entry
  • Flag for Display Field of Entry
  • Flag for Segment Field of Entry
  • Flag for URL Field of Entry
    Those attribute will now also be copied.

Bugfix SUP-5519 🔗 Link

The cookie handling of the RestClient has been modified, so that every instance will use a separate store. This fixes overwriting of the session cookie when multiple logged in instances were used.

Bugfix SUP-5378 🔗 Link

The previews of images, which were resized with the GenticsImageStore were cached, regardless of whether the editor was allowed to view them. This could cause editors to see the cached “not allowed” image, if if they had sufficient privileges. This has been fixed now.

This Gentics Content.Node version includes the Aloha Editor 1.4.47 – 13.06.2018

This Gentics Content.Node version includes the .Node Version 2.3.2