Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-8078

Page editor becomes unstable when render exception

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Neutral
    • 6.2.10
    • 6.2.8
    • None

    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).

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              efochr Evzen Fochr
              jayala Jonathan Ayala
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Bug DoR
                  Task DoD

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - Not Specified
                    Not Specified
                    Logged:
                    Time Spent - 1h 40m
                    1h 40m