Gentics CMS Changelogs

---

Bugfix SUP-11342 Link to this entry

Administration User Interface: Fixed issue with overlapping icons on the dashboard and Administration Permissions interface.

---

Bugfix SUP-14301 Link to this entry

Administrator User Interface: Activity message is shown, upon sync from/to filesystem button clicked in packages.

---

Bugfix SUP-11735 Link to this entry

When publishing into a Mesh ContentRepository, all calls to get data using graphql will now have the parameter “wait“ set to “false” and will therefore never wait for the search sync to be idle in Mesh.

---

Bugfix SUP-14422 Link to this entry

Administration User Interface: Synchronizing Dev-Tool Packages from or to the File-System will now wait for 5 seconds to complete. If it is not able to complete in time, the sync will be continued in the Background. The User will now also receive the appropriate messages for the status of the sync.

---

Bugfix SUP-14380 Link to this entry

Changing the language reloads the page and updates the language.

---

Bugfix SUP-14392 Link to this entry

Editor User Interface: When the Maintenance-Mode is activated, the user is now properly signed out with a correct error message.

---

Bugfix SUP-14424 Link to this entry

Editor UI: Error message is shown and prevent the saving, when clicking on the ‘save and close‘ button after closing the image properties editor and it contains invalid data.

---

Bugfix SUP-14489 Link to this entry

Administration User Interface: While creating a Node, it‘s now possible to change the SEO and Internationalization settings. The default values for these settings have also been updated to hide file extensions and without additional file-encoding.

---

Bugfix SUP-14491 Link to this entry

When adding a contentrepository to a devtool package, which is assigned to a node, and the node has no contentrepository assigned, the node is modified to have the contentrepository assigned. Before this fix, this was done with user ID 0, which changed the last editor of the node to 0, causing errors when reading the node over the REST API. This has been fixed now.

---