Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-22517

ezxml header level handling is broken inside custom tags

    Details

      Description

      In the Online Editor, if you create a custom tag with a header at the top, and there is a header one level lower as the first element above the custom tag, the custom tag breaks (in other words, you lose the custom tag element).

      Steps to reproduce:

      1. Create or edit an article;
      2. Add a paragraph to "body" field e.g. "Heading 1";
      3. Set it with a "Heading 1" style;
      4. Click on "Insert custom tag" button and add a factbox;
      5. Set the text inside the factbox with a "Heading 2" style;
      6. Disable text editor, and verify the resulting code is OK:

      <header level="1">Heading 1</header>
      <custom name="factbox" custom:title="factbox" custom:align="right">
        <header level="2">factbox</header>
      </custom>
      

      7. Re-enable editor;
      8. Highlight first paragraph and set it with a different style e.g. Heading 3;
      9. Disable editor, and check the resulting code. The custom tag is gone:

      <header level="3">Heading 1</header>
      <header level="2">factbox</header>
      

        Activity

        Show
        Damien Pobel (Inactive) added a comment - PR: https://github.com/ezsystems/ezpublish-legacy/pull/918
        Show
        Damien Pobel (Inactive) added a comment - Fixed in ezpublish-legacy: master: http://github.com/ezsystems/ezpublish-legacy/commit/2e56b2953056f432129b17d97a0d582a805a503a
        Hide
        Eduardo Fernandes (Inactive) added a comment -

        QA Approved.

        Show
        Eduardo Fernandes (Inactive) added a comment - QA Approved.

          People

          • Assignee:
            Unassigned
            Reporter:
            Nuno Oliveira (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: