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

Storage paths for binaries are different if stored via public api or legacy

    Details

    • Type: Bug Bug
    • Status: Confirmed
    • Priority: High High
    • Resolution: Unresolved
    • Affects Version/s: 5.4.9
    • Fix Version/s: QA tracked issues
    • Component/s: 5.x > Legacy IO
    • Labels:
      None

      Description

      When I use the Public API to create a content of any kind of content object with an Image attribute, I can't have the image displayed in the frontend or in the admin interface.
      To create content with the API, QA is using the CreateImageCommand.php given in the API cookbook.
      When troubleshooting the issue, I found out that the image binary file was stored in a location similar to:

      ezpublish_legacy/var/ezdemo_site/storage/images/1/2/3/0/321-1-eng-GB/ValidJpgImage.jpg
      

      If I use the legacy admin interface, the image is correctly pubished and displayed, and stored in a location similar to:

      ezpublish_legacy/var/ezdemo_site/storage/images/folder26698/valid-jpg-image/321-1-eng-GB/Valid-JPG-Image.jpg
      

      This was discovered while testing EZP-26963.

        Activity

        Rui Silva (Inactive) created issue -
        Rui Silva (Inactive) made changes -
        Field Original Value New Value
        Description When I use the Public API to create a content of any kind of content object with an Image attribute, I can't have the image displayed in the frontend or in the admin interface.
        To create content with the API, QA is using the [CreateImageCommand.php|https://github.com/ezsystems/CookbookBundle/blob/master/Command/CreateImageCommand.php] given in the API cookbook.
        When troubleshooting the issue, I found out that the image binary file was stored in a location similar to:
        {code}
        ezpublish_legacy/var/ezdemo_site/storage/images/1/2/3/0/321-1-eng-GB/ValidJpgImage.jpg
        {code}
        If I use the legacy admin interface, the image is correctly pubished and displayed, and stored in a location similar to:
        {code}
        ezpublish_legacy/var/ezdemo_site/storage/images/1/2/3/0/321-1-eng-GB/ValidJpgImage.jpg
        {code}
        This was discovered while testing EZP-26963.
        When I use the Public API to create a content of any kind of content object with an Image attribute, I can't have the image displayed in the frontend or in the admin interface.
        To create content with the API, QA is using the [CreateImageCommand.php|https://github.com/ezsystems/CookbookBundle/blob/master/Command/CreateImageCommand.php] given in the API cookbook.
        When troubleshooting the issue, I found out that the image binary file was stored in a location similar to:
        {code}
        ezpublish_legacy/var/ezdemo_site/storage/images/1/2/3/0/321-1-eng-GB/ValidJpgImage.jpg
        {code}
        If I use the legacy admin interface, the image is correctly pubished and displayed, and stored in a location similar to:
        {code}
        ezpublish_legacy/var/ezdemo_site/storage/images/folder26698/valid-jpg-image/321-1-eng-GB/Valid-JPG-Image.jpg
        {code}
        This was discovered while testing EZP-26963.
        Paulo Nunes (Inactive) made changes -
        Status Open [ 1 ] Confirmed [ 10037 ]
        Alex Schuster made changes -
        Workflow EZ* Development Workflow [ 103495 ] EZEE Development Workflow [ 108804 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Confirmed Confirmed
        4h 20m 1 Paulo Nunes 13/Apr/17 2:41 PM

          People

          • Assignee:
            Unassigned
            Reporter:
            Rui Silva (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated: