Gentics Content.Node Changelogs

---

Bugfix SUP-88

Fixed possible NPE when saving pages containing empty overviews

---

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.

---