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

ezxmltext -> richtext conversion : <custom> inside <section>

    Details

      Description

      Legacy will will put both block and inline customs tags inside a <paragraph> element in ezxmltext. Block custom tags will however be placed in temporary namespace

          <section>
              <paragraph
                  xmlns:tmp="http://ez.no/namespaces/ezpublish3/temporary/">
                  <custom name="factbox" custom:title="factbox" custom:align="right">
                      <paragraph>block - custom tag</paragraph>
                  </custom>
              </paragraph>
              <paragraph>
                  <custom name="strike">inline - custom tag</custom>
              </paragraph>
          </section>
      

      However, in a old legacy db I find custom tags just below <section>. I am not able to reproduce this on 5.4 in neither OE or simplified xml, so I assume this is some old behavior:

            <section>
              <custom name="linebreak"/>
              <header>Advisers:
                <custom name="linebreak"/>Foobar Corp.
              </header>
            </section>
      

      Custom tags in headers needs to be considered inline ( and they are in conversion script).
      IMO it sounds natural to treat custom tags just below section as block, but that is not possible in this case (the same custom tag name is used in both places).

      I see 3 possible conversion solution

      1. <section><custom/></section> is transformed to <eztemplate/>
      2. <section><custom></section> is transformed to <para><eztemplateinline></para>
      3. convers script gets a command option where user may specify which custom tags are inline

        Activity

        Hide
        Vidar Langseid added a comment -

        I'll transform <section><custom/></section> into <eztemplate/> and issue a warning about it

        I'll also issue a warning on every inline custom tag as that is not supported by ezplatform's richtext editor ATM ( it is supported by the richtext markup and xhtml output though)

        Show
        Vidar Langseid added a comment - I'll transform <section><custom/></section> into <eztemplate/> and issue a warning about it I'll also issue a warning on every inline custom tag as that is not supported by ezplatform's richtext editor ATM ( it is supported by the richtext markup and xhtml output though)
        Show
        Vidar Langseid added a comment - PR : https://github.com/ezsystems/ezplatform-xmltext-fieldtype/pull/76
        Show
        Vidar Langseid added a comment - Merged to master in https://github.com/ezsystems/ezplatform-xmltext-fieldtype/commit/cb94776c33879203ef5e9f5d8caafe49cda7d0f0

          People

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

            Dates

            • Created:
              Updated: