Gentics Content.Node Changelogs

---

---

Bugfix RT57986

Multiple bugs concerning overviews have been fixed: An overview would be dirted if a matching object was added in a channel. A recursive overview of images would not be dirted if an image was added in a subfolder of a selected folder. An overview would not render objects created in the same channel, if there were no other dependencies of the page in that channel (as compared to the parent channel).

---

Bugfix RT57893

Improved robustness of publish process A race condition that allowed the publish process to run multiple times in parallel has been removed. A potential deadlock in error handling during the initialisation phase of the publish process has been removed.

---

Bugfix RT57976

When defining velocity macros in tag implementations, the macros were globally available and would be overwritten by macros defined in other tags but with the same name. This resulted in unexpected and random behavior if multiple macros with the same name were defined. The scope of inline defined macros has been changed to be local to the template, like documented in the Gentics Content.Node Guides.

---

Bugfix RT57765

Copying nodes: Fixed copying nodes with the user interface not correctly working. When copying a node, the copy would not appear in the users tree or node list because the permission cache was not refreshed.

---

Bugfix RT57923

Email sending: Fixed GCN not setting the “Return-Path“ in some cases when “$MAILRETURNPATH” is specified in the configuration. This happened for example when someone took pages back into revision in the publish queue.

---

Bugfix RT57985

When only a tagmap entry was modified for a ContentRepository, but no data was changed, the subsequent call to CRSync or MCCRSync would not synchronize this changed tagmap entry to the target CR. This has been fixed now, CRSync and MCCRSync will always synchronize modified tagmap entries, even if no actual data was changed.

---