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

            blocks

            Bug - A problem which impairs or prevents the functions of the product. EZP-29027 EzXmlText to RichText validation error : Element section has extra content on <literal> tag

            • High - Major loss of functionality.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. EZP-29601 As a editor I want to be able to insert html code in a richtext field

            • High - Major loss of functionality.
            • Development Review

            Story - A user story, aka a new feature. EZP-29355 As a developer, I want to edit the "ezcontent" of a custom tag

            • High - Major loss of functionality.
            • Closed

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              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
              Hide
              Permalink
              Dariusz Szut added a comment -

              PR in admin-ui created: https://github.com/ezsystems/ezplatform-admin-ui/pull/709

              Show
              Dariusz Szut added a comment - PR in admin-ui created: https://github.com/ezsystems/ezplatform-admin-ui/pull/709
              Hide
              Permalink
              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 .

                People

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

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Agile