[MAGNOLIA-8078] Page editor becomes unstable when render exception Created: 28/Apr/21  Updated: 07/Jun/21  Resolved: 02/Jun/21

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 6.2.8
Fix Version/s: 6.2.10

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Evzen Fochr
Resolution: Fixed Votes: 1
Labels: VN-Testing, maintenance
Remaining Estimate: Not Specified
Time Spent: 1h 40m
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Sprint: Maintenance 60, Maintenance 61
Story Points: 5

 Description   

Steps to reproduce

  1.  Modify component template to force a rendering exception, for example add to /mtk/templates/components/html.ftl the following line:
    ${content.noProperty}
  1.  Open pages app and create a new page
  2. Add some components different from the previous one
  3. Add a new component of the modified template

Expected results

Editor shows the exception within the component but the rest of the editor works fine allowing editors keep on working

Actual results

Editor becomes unstable, main area goes to the bottom and new added components are not shown

Development notes

In 5.7.X it works as expected.
This is not reproducible in demo author as the instance needs to be restarted after first run so edit mode is enabled (MAGNOLIA-7044).


Generated at Mon Feb 12 04:29:27 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.