Gentics Content.Node Changelogs

---

Bugfix RT58589

When creating folders over the REST API, the inheritable object tags from the mother folder were not automatically set for the new created folder. This has been fixed now.

---

Bugfix RT58599

Some errors, that occurred while rendering the tree will be logged now.

---

Bugfix RT58574

Editing pages with Aloha Editor: When using the method addDeleteButton() to add delete buttons to blocks, that contain nested blocks, the delete button was also attached to the nested blocks. This has been fixed now.

---

Bugfix RT58572

When content repositories, that have instant publishing enabled are not available, this might affect the whole system. With some new configuration options, it is possible to have instant publishing temporarily disabled in case of availability problems. See Instant Publishing in the Guides for details.

---

Bugfix RT58589

Creating new folders in the backend sometimes produced an SGB due to duplicate object tags. The folder was created in the DB, but caches were not properly cleared, which caused some problems afterwards. This has been fixed now, duplicate object tags will be ignored now.

---

Bugfix RT58599

The tree used to select the target folders when copying pages internally used too many requests to the REST API. This has been fixed now, which will reduce the render times for the tree.

---

Bugfix RT58570

In some situations, dirting of folders upon changed object properties might not work, because a new object tag object had been created since the folder was last published. Storing of dependencies has been improved to be insensitive against such situations. It is important to note, that this change will only affect objects, that are republished after this update.

---

Bugfix RT58561

Some issues of export and import of channel structures have been fixed.
For these fixes, it is important that both the source and target system are update to the newest version of GCN, before doing the export and import.

• When importing a master node together with at least one channel, that contained at least one localized folder, into a system, where neither of the nodes already existed, it could happen, that the import failed with an “Internal error“.
• When exporting a master with channel and subchannel, it could happen that the this channel structure was not imported correctly.
• When resolving a conflict with behaviour “copy“, some parts of the new created object possibly had the same global IDs as the
  imported object, which could lead to “Internal errors“ in subsequent imports.
• When resolving a conflict with behaviour “copy” and then doing another import of the same bundle, the conflict
  would not be detected again, which could lead to unwanted overwriting of the local object.

---

Bugfix RT58596

When publishing into a non MCCR content repository and not using multithreaded publishing, the motherid of an object sometimes would not be updated after the object had been moved to another folder. This has been fixed now.

---