Details
-
Type:
Story
-
Status: Closed
-
Priority:
High
-
Resolution: Done
-
Affects Version/s: 2.2.0-beta1, 2.0.2, 1.13.3
-
Fix Version/s: 2.3.3
-
Component/s: Online Editor & Rich Text field type
-
Labels:None
-
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
-
EZP-29027 EzXmlText to RichText validation error : Element section has extra content on <literal> tag
-
- Closed
-
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