Gentics Content.Node Changelogs

---

Bugfix SUP-7308 🔗 Link

Fixed a bug that showed wrong live urls when using the Gentics Mesh content repository with the project per node setting disabled.

---

Bugfix SUP-7308 🔗 Link

The publish process failed when only a channel was assigned to a Mesh ContentRepository (with project per node enabled). This has been fixed now.

---

Bugfix SUP-7308 🔗 Link

Assigning nodes to content repositories over the REST API will now do the same conflict tests like when assigning using the UI.

---

Bugfix SUP-9249 🔗 Link

Rendering of links to objects, which are published into a Mesh Content.Repository always rendered Mesh Links, regardless of whether the source object was also published into the same Mesh Content.Repository, or not, which caused incorrectly rendered links in some cases. The link rendering has been changed to only render Mesh Links, when the source and target object will be published into the same Mesh Project. All other cases will render static links (including the host name of the target node).

---

Bugfix SUP-9169 🔗 Link

File and image properties are now immediately updated when an item is replaced.

---

Bugfix SUP-7715 🔗 Link

Synchronizing a construct from a devtool package into the CMS failed, if the type of a part was changed from a non-text based type to a text based type. This has been fixed.

---

Bugfix SUP-9140 🔗 Link

Object properties for images are immediately shown when an image is uploaded.

---

Bugfix SUP-9072 🔗 Link

In rare cases, the REST API would return untranslated error messages. This has been fixed now.

---

Bugfix SUP-9064 🔗 Link

When publishing pages into a Mesh Content.Repository, the tagmap entry “content” could not be used to publish something different than the rendered page. If the tagname was e.g. changed to the name of a specific tag, instant publishing would render that tag but the regular publish process would overwrite the field with the rendered page content.
This has been fixed now.

---