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

New draft based on a selected version doesn't respect image binaries versions

    Details

      Description

      This issue is similar to EZP-27128, but insted of keywords, use images/media/files

      Steps to Reproduce
      1. Add an image/media/file attribute to a Article content type
      2. Create one article with name "Article1" and insert an image/media/file "111".
      3. Publish. This will create version1
      4. Edit the created article and update name to "Article2" and replace the image/binary/file attachement. (attach "222")
      5. Publish it. This will create version2
      6. Go to "versions" tab of the article, and create a new draft based on verison1 (the one that has the first inserted image/media/binary ("111"))
      7. When we edit this new draft, we see that the article name is respected accordingly to the chosen version (Article1), but the image/binary/file
        is not. We have the attach "222", that is related to version2 and not the chosen version (should be attach "111")

        Issue Links

          Activity

          Hide
          Rui Silva (Inactive) added a comment -

          After previous discussion, it was decided that the scope of this issue is only the image fieldtype, the file fieldtype and media fieldtype are to be handled on EZP-27324.
          Tested and approved by QA for 1.7.

          Show
          Rui Silva (Inactive) added a comment - After previous discussion, it was decided that the scope of this issue is only the image fieldtype, the file fieldtype and media fieldtype are to be handled on EZP-27324 . Tested and approved by QA for 1.7.
          Hide
          Rui Silva (Inactive) added a comment -

          Bertrand Dunogier, indeed, it is probably best to follow up on another issue the resolution of the other ones.

          Show
          Rui Silva (Inactive) added a comment - Bertrand Dunogier , indeed, it is probably best to follow up on another issue the resolution of the other ones.
          Hide
          Bertrand Dunogier added a comment -

          Created EZP-27324 for the remaining types. This one should be closed as it is fixed for images in 1.7.3. Do you agree QA ?

          Show
          Bertrand Dunogier added a comment - Created EZP-27324 for the remaining types. This one should be closed as it is fixed for images in 1.7.3. Do you agree QA ?
          Hide
          Rui Silva (Inactive) added a comment -

          The issue seems to have been solved for Image fieldtype definitions. However, for File fieldtype definition, only the name of the file fetched for the download link seems to have been corrected, but the downloaded file still is the wrong one when you open it afterwards, and for Media fieldtype definitions, it simply seems to not be fixed at all: wrong version file is shown on player.

          Show
          Rui Silva (Inactive) added a comment - The issue seems to have been solved for Image fieldtype definitions. However, for File fieldtype definition, only the name of the file fetched for the download link seems to have been corrected, but the downloaded file still is the wrong one when you open it afterwards, and for Media fieldtype definitions, it simply seems to not be fixed at all: wrong version file is shown on player.
          Show
          Bertrand Dunogier added a comment - PR: https://github.com/ezsystems/ezpublish-kernel/pull/1951 .
          Hide
          Damien Pobel (Inactive) added a comment - - edited

          It's actually a "design" bug in the REST API resources to download a binary file or to load an image variation. The version number (or something that varies with the version) is missing in the URI. As a result, you always get the binary file or the image variation of the last published version instead of the one for a given version.

          Show
          Damien Pobel (Inactive) added a comment - - edited It's actually a "design" bug in the REST API resources to download a binary file or to load an image variation. The version number (or something that varies with the version) is missing in the URI. As a result, you always get the binary file or the image variation of the last published version instead of the one for a given version.

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Nunes (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: