Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
5.1
-
N/A
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
After editing the same image object from the administration interface, the image is saved to the correct location:
var/<something>/storage/images/media/images/test/1712-1-eng-GB/test.jpg
Steps to reproduce:
1. Create an image object using the public API, verify that the image content is placed directly under <var_dir>/images
2. Create an image through the admin interface, verify that it's placed in <var_dir>/images/<xxx>/...
3. Edit the image object created in step one, and save it again. Verify that the updated image is saved in the correct location (consistent with the result from step two).
Attachments
Issue Links
1.
|
Implement field storage publish events | Closed | Bertrand Dunogier |
|