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

          Paulo Nunes (Inactive) created issue -
          Paulo Nunes (Inactive) made changes -
          Field Original Value New Value
          Description This issue is similar to EZP-27128, but insted of keywords, use images/media/files

          h5.Steps to Reproduce
          -Add an image/media/file attribute to a Article content type
          -Create one article with name "Article1" and insert an image/media/file "111".
          -Publish. This will create version1
          -Edit the created article and update name to "Article2" and replace the image/binary/file attachement. (attach "222")
          - Publish it. This will create version2
          -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"))
          -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")
          This issue is similar to EZP-27128, but insted of keywords, use images/media/files

          h5.Steps to Reproduce
          -Add an image/media/file attribute to a Article content type
          -Create one article with name "Article1" and insert an image/media/file "111".
          -Publish. This will create version1
          -Edit the created article and update name to "Article2" and replace the image/binary/file attachement. (attach "222")
          -Publish it. This will create version2
          -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"))
          -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")
          Paulo Nunes (Inactive) made changes -
          Status Open [ 1 ] Confirmed [ 10037 ]
          Damien Pobel (Inactive) made changes -
          Link This issue is duplicated by EZP-26989 [ EZP-26989 ]
          Damien Pobel (Inactive) made changes -
          Description This issue is similar to EZP-27128, but insted of keywords, use images/media/files

          h5.Steps to Reproduce
          -Add an image/media/file attribute to a Article content type
          -Create one article with name "Article1" and insert an image/media/file "111".
          -Publish. This will create version1
          -Edit the created article and update name to "Article2" and replace the image/binary/file attachement. (attach "222")
          -Publish it. This will create version2
          -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"))
          -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")
          This issue is similar to EZP-27128, but insted of keywords, use images/media/files

          h5.Steps to Reproduce

          # Add an image/media/file attribute to a Article content type
          # Create one article with name "Article1" and insert an image/media/file "111".
          # Publish. This will create version1
          # Edit the created article and update name to "Article2" and replace the image/binary/file attachement. (attach "222")
          # Publish it. This will create version2
          # 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"))
          # 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")
          Damien Pobel (Inactive) made changes -
          Component/s Platform > REST API v2 [ 10310 ]
          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.
          Damien Pobel (Inactive) made changes -
          Status Confirmed [ 10037 ] InputQ [ 10001 ]
          Damien Pobel (Inactive) made changes -
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Bertrand Dunogier made changes -
          Status InputQ [ 10001 ] Development [ 3 ]
          Bertrand Dunogier made changes -
          Status Development [ 3 ] Development Review [ 10006 ]
          Show
          Bertrand Dunogier added a comment - PR: https://github.com/ezsystems/ezpublish-kernel/pull/1951 .
          Bertrand Dunogier made changes -
          Status Development Review [ 10006 ] Documentation Review done [ 10011 ]
          Fix Version/s 1.7.3 [ 14701 ]
          Fix Version/s 1.9.1 [ 14708 ]
          Fix Version/s 1.8.2 [ 14720 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Rui Silva (Inactive) made changes -
          Status Documentation Review done [ 10011 ] QA [ 10008 ]
          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.
          Rui Silva (Inactive) made changes -
          Status QA [ 10008 ] InputQ [ 10001 ]
          Assignee Rui Silva [ rui.silva@ez.no ]
          Paulo Nunes (Inactive) made changes -
          Link This issue relates to EZP-27264 [ EZP-27264 ]
          Damien Pobel (Inactive) made changes -
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Bertrand Dunogier made changes -
          Summary New draft based on a selected version doesn't respect image/media/files binaries New draft based on a selected version doesn't respect image binaries versions
          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 ?
          Bertrand Dunogier made changes -
          Status InputQ [ 10001 ] Development Review done [ 10028 ]
          Assignee Bertrand Dunogier [ bertrand.dunogier@ez.no ]
          Bertrand Dunogier made changes -
          Status Development Review done [ 10028 ] Documentation Review done [ 10011 ]
          Bertrand Dunogier made changes -
          Link This issue testing discovered EZP-27324 [ EZP-27324 ]
          Rui Silva (Inactive) made changes -
          Status Documentation Review done [ 10011 ] QA [ 10008 ]
          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
          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.
          Rui Silva (Inactive) made changes -
          Assignee Rui Silva [ rui.silva@ez.no ]
          Status QA [ 10008 ] Closed [ 6 ]
          Resolution Fixed [ 1 ]
          Alex Schuster made changes -
          Workflow EZ* Development Workflow [ 103299 ] EZEE Development Workflow [ 126395 ]
          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          Open Open Confirmed Confirmed
          49s 1 Paulo Nunes 28/Mar/17 12:36 PM
          Confirmed Confirmed InputQ InputQ
          6d 3h 21m 1 damien.pobel@ez.no 03/Apr/17 3:57 PM
          InputQ InputQ Development Development
          7d 1h 2m 1 Bertrand Dunogier 10/Apr/17 4:59 PM
          Development Development Development Review Development Review
          3s 1 Bertrand Dunogier 10/Apr/17 4:59 PM
          Development Review Development Review Documentation Review done Documentation Review done
          2d 18h 27m 1 Bertrand Dunogier 13/Apr/17 11:27 AM
          QA QA InputQ InputQ
          1h 2m 1 rui.silva@ez.no 13/Apr/17 5:01 PM
          InputQ InputQ Development Review done Development Review done
          19d 20h 29m 1 Bertrand Dunogier 03/May/17 1:30 PM
          Development Review done Development Review done Documentation Review done Documentation Review done
          9s 1 Bertrand Dunogier 03/May/17 1:30 PM
          Documentation Review done Documentation Review done QA QA
          6h 41m 2 rui.silva@ez.no 03/May/17 3:40 PM
          QA QA Closed Closed
          1d 19h 20m 1 rui.silva@ez.no 05/May/17 11:01 AM

            People

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

              Dates

              • Created:
                Updated:
                Resolved: