Uploaded image for project: 'CMS'
  1. CMS
  2. CMS-10648

Invert two repeater entries containing rich_text with image

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • 4.5.0
    • None
    • None
    • None
    • 4.2, 4.3, 4.4
    • 4.5 M2

      How to reproduce : 

      1 - Create a FAQ with 2 "Questions" entries and fill "Réponse" field with a local image. 

      Here is an example : 

      2 - Save this FAQ.

      3 - Open it in edition and click on following arrow, to change the order of entries : 

      4 - Click on Save button. 

      Following error is displayed : 

          [CMS-10648] Invert two repeater entries containing rich_text with image

          This is a quite important issue as wrong data is stored.
          For a local image/audio/video, the following uri is stored in the docbook : "<content id>@<attribute path>;<filename>"
          The content id is overridden by the current content, but the attribute path is taken as is.
          The main issue is that content id and attribute path should not be stored at all !

          When fixing this issue, all rich text should be migrated to remove references to content id and attribute path.
          One way to fix is to rebuild the docbook @fileref attribute when SAXing a RichText

          Cédric Damioli added a comment - This is a quite important issue as wrong data is stored. For a local image/audio/video, the following uri is stored in the docbook : " <content id>@<attribute path>;<filename> " The content id is overridden by the current content, but the attribute path is taken as is. The main issue is that content id and attribute path should not be stored at all ! When fixing this issue, all rich text should be migrated to remove references to content id and attribute path. One way to fix is to rebuild the docbook @fileref attribute when SAXing a RichText

            cbayle Caroline Bayle
            mfranchet Magali Franchet
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: