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

Video width and height params are not saved during content creation

    Details

      Description

      Media (video) attributes like width/height are not properly saved during content creation.
      When content is uploaded (but not yet published), then in preview the mentioned properties are set correctly. After publish, there are no width/height values. In edit view of this content, you can see that width and height are set to 0.
      If you manually change values in the edit mode and publish content, then values will be correctly saved.

      Steps to reproduce
      1. Create ContentType with Media field, for e.g. Video
      2. Create content of type Video, select some file
      3. You can see, that in preview video width and height are set correctly
      4. Publish content
      5. Go to the content preview, there is lack of these parameters
      6. Edit content -> you can see, that these parameters have default (0) values
      7. Edit values and publish
      8. Go to the preview -> you can see, those manually set parameters were saved correctly

      More information
      I did some test, and I see that during new content publishing, PlatformUI sends to the REST width and height values equal 0, although these values are correct in the preview.

      Open question
      After the additional test, I realized that in video preview (before content was published) values which are visible in width and height fields are empty, and we see only placeholders. I think that it might be really confusing for the customer. Sylvain Guittard what do you think? How should it be solved?

        Activity

        Hide
        Sylvain Guittard added a comment -

        Hi Kamil!
        Thanks for the tests.

        what do you think?

        I agree with you, it's really confusing for the editor. When the user sees the values in those fields, the user expects that those values to be saved / stored. It's definitely a bug.

        How should it be solved?

        I think instead of updating the placeholder, we should update the value of the field.

        Show
        Sylvain Guittard added a comment - Hi Kamil! Thanks for the tests. what do you think? I agree with you, it's really confusing for the editor. When the user sees the values in those fields, the user expects that those values to be saved / stored. It's definitely a bug. How should it be solved? I think instead of updating the placeholder, we should update the value of the field.
        Show
        Kamil Madejski added a comment - PR: https://github.com/ezsystems/PlatformUIBundle/pull/909

          People

          • Assignee:
            Unassigned
            Reporter:
            Kamil Madejski
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: