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

PAPI image/binary should avoid using orignal name & hitting filesystem node limits

    XMLWordPrintable

    Details

      Description

      When creating image objects through the Public API, image content is placed directly in the legacy images root, for example:

          var/<something>/storage/images/1712-1-eng-GB/Chrysanthemum.jpg
      

      However in this case where the Content name is "test", it should be something like

          var/<something>/storage/images/171/2/1/eng-GB/test.jpg
      

      The example is just an example, this can be solved different ways, here it makes sure all id's are splinted per 3 digits, it could be 4. Also the language folder can be skipped if field is untranslatable, but only if this is easily achievable.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              andre.romcke@ez.no André Rømcke
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Time Spent - 2 days, 3 hours, 30 minutes Remaining Estimate - 5 hours
                5h
                Logged:
                Time Spent - 2 days, 3 hours, 30 minutes Remaining Estimate - 5 hours
                2d 3h 30m