Gentics Content.Node Changelogs

---

Bugfix SUP-3488

The repository browser didn‘t work in the tagfill dialog when the multichannelling feature was not enabled. This has been fixed.

---

Bugfix SUP-3441

When the feature activiti_integration was used and a process was configured for the event onPagePublish publishing a new page (which was never published before) with publish at failed with an internal error. Also processes configured for the events onPagePublish or onPageTakeOffline where not started for pages that went on- or offline due to time management. Both issues have been fixed.

---

Bugfix SUP-3320

When editing a page with aloha editor, and a tag in an editable was refreshed (e.g. because the tag had been modified using the tagfill dialog), and the tag contained a nested tag in an editable, sometimes the order of initialization of the nested blocks and editables was incorrect and could cause side-effects. One of this side-effects was the automatic modification of editables through the browser when using internet explorer by inserting a br-tag. The initialization order of nested tags has been fixed now.

---

Bugfix SUP-3457

Purging the wastebin from many deleted folders consumed a big amount of memory, which could cause OutOfMemory errors. This has been fixed now.

---

Bugfix SUP-3354

When a page rendered the tag of another page, which rendered a velocity overview containing the original page, and a tag of the original page was rendered that resolved , this was incorrectly not resolved to the name of the page in the overview, but the name of the page containing the overview. This has been fixed now.

---

Bugfix SUP-3413

When the type of a part in a construct was changed from Select (single) or Select (multiple) to Checkbox, the values of already existing tags where not consistently interpreted: # The tagfill dialog and the REST API showed the checkbox to not be checked # While rendering, the checkbox was treated as being checked. The tag had to be filled once to fix this behaviour. This issue has been fixed now, the checkbox will now consistenly be handled as “not checked”.

---

Bugfix SUP-3458

When using the feature attribute_dirting together with instant_cr_publishing and multichannelling, it could happen that objects that were modified again during a publish run for which they were scheduled to be published were not published correctly into channels (not all attributes were updated for the channels). This has been fixed now.

---