You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During todays debugging session with @jensens and @gogo we found out that editing the properties modal and the field settings modal have the following regressions:
Since the original edit form is loaded and saved via GET/POST requests in mosaic.overlay.js the patterns aren't initialized correctly again in the .mosaic-original-content form. This leads to a JS error when saving the whole page.
Additionally the events are bound multiple times, so every time you edit your properties modal the reload event of the original content node gets duplicated 😰
Possible solution:
manipulate the .mosaic-original-content form values via JS when you edit Properties or field tile settings.
your idea here
The text was updated successfully, but these errors were encountered:
This issue also affects RichText Fields in the Properties Form. Note that if inline mode is selected you won't get TinyMCE for RichText Fields in the Properties Form. When you disable inline mode the Editor will appear (workaround).
During todays debugging session with @jensens and @gogo we found out that editing the properties modal and the
field
settings modal have the following regressions:mosaic.overlay.js
the patterns aren't initialized correctly again in the.mosaic-original-content
form. This leads to a JS error when saving the whole page.Possible solution:
.mosaic-original-content form
values via JS when you editProperties
orfield
tile settings.The text was updated successfully, but these errors were encountered: