Details
-
Bug
-
Resolution: Fixed
-
High
-
5.1, 5.2
-
None
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.