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

As a editor I want the richtext format to support the equivalent of ezmltext's <literal> tag

    Details

    • Sprint:
      [2.4] - Sprint 3
    • Story Points:
      3

      Description

      In ezxml ( legacy ) we supported the <literal> tag which would basically put the containing text inside a <pre> tag. This is not supported in richtext or the richtext editor ATM

      This also causes problems for people migrating from legacy as the conversion tool cannot deal with this tag until it is supported in ezplatform.

      Note : Don't confuse this request with the already supported docbook's <literallayout> tag which is only about supporting linefeeds inside paragraphs

        Issue Links

          Activity

          Vidar Langseid created issue -
          Vidar Langseid made changes -
          Field Original Value New Value
          Description In ezxml ( legacy ) we supported the <literal> tag which would basically put the containing text inside a <pre> tag. This is not supported in richtext or the richtext editor ATM

          This also causes problems for people migrating from legacy as the conversion tool cannot deal with this tag until it is supported in ezplatform
          In ezxml ( legacy ) we supported the <literal> tag which would basically put the containing text inside a <pre> tag. This is not supported in richtext or the richtext editor ATM

          This also causes problems for people migrating from legacy as the conversion tool cannot deal with this tag until it is supported in ezplatform.

          Note : Don't confuse this request with the already supported richtext tag <literallayout> which is only about supporting linefeeds inside paragraphs
          Vidar Langseid made changes -
          Link This issue blocks EZP-29027 [ EZP-29027 ]
          Bertrand Dunogier made changes -
          Link This issue relates to EZP-29355 [ EZP-29355 ]
          Vidar Langseid made changes -
          Summary As a editor I want the richtext format to supports the equalent of ezmltext' <literal> tag As a editor I want the richtext format to support the equalent of ezmltext's <literal> tag
          Bertrand Dunogier made changes -
          Summary As a editor I want the richtext format to support the equalent of ezmltext's <literal> tag As a editor I want the richtext format to support the equivalent of ezmltext's <literal> tag
          Vidar Langseid made changes -
          Link This issue relates to EZP-29601 [ EZP-29601 ]
          André Rømcke made changes -
          Description In ezxml ( legacy ) we supported the <literal> tag which would basically put the containing text inside a <pre> tag. This is not supported in richtext or the richtext editor ATM

          This also causes problems for people migrating from legacy as the conversion tool cannot deal with this tag until it is supported in ezplatform.

          Note : Don't confuse this request with the already supported richtext tag <literallayout> which is only about supporting linefeeds inside paragraphs
          In ezxml ( legacy ) we supported the <literal> tag which would basically put the containing text inside a <pre> tag. This is not supported in richtext or the richtext editor ATM

          This also causes problems for people migrating from legacy as the conversion tool cannot deal with this tag until it is supported in ezplatform.

          Note : Don't confuse this request with the already supported docbook's <literallayout> tag which is only about supporting linefeeds inside paragraphs
          Hide
          André Rømcke added a comment - - edited

          The approach for this ended up using docbook's <programlisting> tag for the backend format, and html's <pre> tag for Alloy. Both of which are natively supported formats in their respective domain, and are a good match for plain literal tags coming from eZ Publish (which also used <pre> for OE and web output).

          Merged:
          Kernel PR merged in 1.13 and up (part of final 2.3.0 release): https://github.com/ezsystems/ezpublish-kernel/pull/2430
          Migration script PR merged and made part of release: https://github.com/ezsystems/ezplatform-xmltext-fieldtype/pull/71

          In review:
          Admin UI PR: https://github.com/ezsystems/ezplatform-admin-ui/pull/676

          Show
          André Rømcke added a comment - - edited The approach for this ended up using docbook's <programlisting> tag for the backend format, and html's <pre> tag for Alloy. Both of which are natively supported formats in their respective domain, and are a good match for plain literal tags coming from eZ Publish (which also used <pre> for OE and web output) . Merged: Kernel PR merged in 1.13 and up (part of final 2.3.0 release) : https://github.com/ezsystems/ezpublish-kernel/pull/2430 Migration script PR merged and made part of release: https://github.com/ezsystems/ezplatform-xmltext-fieldtype/pull/71 In review: Admin UI PR: https://github.com/ezsystems/ezplatform-admin-ui/pull/676
          André Rømcke made changes -
          Status Backlog [ 10000 ] Specification [ 10002 ]
          André Rømcke made changes -
          Status Specification [ 10002 ] Specification Done [ 10003 ]
          Fix Version/s 2.3.1 [ 15086 ]
          Assignee André Rømcke [ andre.romcke@ez.no ]
          Michał Szołtysek made changes -
          Fix Version/s 2.3.2 [ 15088 ]
          Fix Version/s 2.3.1 [ 15086 ]
          Sylvain Guittard made changes -
          Sprint [2.4] - Sprint 3 [ 117 ]
          Sylvain Guittard made changes -
          Story Points 3
          Hide
          Dariusz Szut added a comment -
          Show
          Dariusz Szut added a comment - PR in admin-ui created: https://github.com/ezsystems/ezplatform-admin-ui/pull/709
          Hide
          Andrzej Longosz added a comment -

          ezsystems/ezplatform-admin-ui#709 merged into 1.3@4e855ee and up to master.

          Show
          Andrzej Longosz added a comment - ezsystems/ezplatform-admin-ui#709 merged into 1.3@4e855ee and up to master .
          Andrzej Longosz made changes -
          Assignee Andrzej Longosz [ andrzej.longosz@ez.no ]
          Andrzej Longosz made changes -
          Status Specification Done [ 10003 ] Development [ 3 ]
          Andrzej Longosz made changes -
          Status Development [ 3 ] Development Done [ 5 ]
          Fix Version/s 2.3.3 [ 15096 ]
          Fix Version/s 2.3.2 [ 15088 ]
          Andrzej Longosz made changes -
          Status Development Done [ 5 ] QA [ 10008 ]
          Andrzej Longosz made changes -
          Assignee Andrzej Longosz [ andrzej.longosz@ez.no ] Katarzyna Zawada [ katarzyna.zawada@ez.no ]
          Katarzyna Zawada made changes -
          Status QA [ 10008 ] QA Done [ 10007 ]
          Assignee Katarzyna Zawada [ katarzyna.zawada@ez.no ]
          Katarzyna Zawada made changes -
          Status QA Done [ 10007 ] Closed [ 6 ]
          Resolution Done [ 9 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Backlog Backlog Specification Specification
          108d 3h 11m 1 André Rømcke 08/Oct/18 1:06 PM
          Specification Specification Specification Done Specification Done
          11s 1 André Rømcke 08/Oct/18 1:06 PM
          Specification Done Specification Done Development Development
          37d 3h 57m 1 Andrzej Longosz 14/Nov/18 4:03 PM
          Development Development Development Done Development Done
          2m 22s 1 Andrzej Longosz 14/Nov/18 4:05 PM
          Development Done Development Done QA QA
          22s 1 Andrzej Longosz 14/Nov/18 4:06 PM
          QA QA QA Done QA Done
          1m 43s 1 Katarzyna Zawada 14/Nov/18 4:07 PM
          QA Done QA Done Closed Closed
          35s 1 Katarzyna Zawada 14/Nov/18 4:08 PM

            People

            • Assignee:
              Unassigned
              Reporter:
              Vidar Langseid
            • Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Agile