Firstly: Yes, I’ve read that Umbraco say that not to place controls in a content app - but the alternative is not to use Umbraco at all, and that wont be accepted by “the powers that be”.
- We have a new member function in a content app, that sets read/write
permissions on the member based on the node the member is created. - There is also a content app on the same doctype that lists associated
members with their permission as radio buttons, with the
functionality to change the permission.
These things work fine, and the app with list of members gets refreshed when a new member is added.
But! Editing one of the content apps triggers “You have unsaved changes” when navigating from the node - even though no change is made in content, and it appears like the surrounding “editor-form” gets $dirty == true.
I’ve tried setting the “new-member”-form and the permissions-form to
$pristine after update, but that doesn’t fix it.
Anyone with a hint how to fix that one?
(Preferably other than hacking some part of Umbraco…)
This is a companion discussion topic for the original entry at https://our.umbraco.com/forum/105674-content-app-triggering-unsaved