Gentics Content.Node Changelogs

---

---

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.

---