Skip to content
This repository was archived by the owner on Apr 13, 2023. It is now read-only.

Possible image path collision if images are uploaded with ftp. #220

Open
vovayatsyuk opened this issue Jul 23, 2012 · 0 comments
Open

Possible image path collision if images are uploaded with ftp. #220

vovayatsyuk opened this issue Jul 23, 2012 · 0 comments
Labels

Comments

@vovayatsyuk
Copy link
Contributor

http://axiscommerce.com/forum/%D0%BE%D1%88%D0%B8%D0%B1%D0%BA%D0%B0-%D0%BF%D1%80%D0%B8-%D0%B2%D1%8B%D0%B2%D0%BE%D0%B4%D0%B5-%D0%B8%D0%B7%D0%BE%D0%B1%D1%80%D0%B0%D0%B6%D0%B5%D0%BD%D0%B8%D0%B9

Scenario:

  • User upload the ready to use folder with images and the picture path is not filename[0]/filename[1]/filename

Example:
sony/image.jpg
samsung/image.jpg

  • Products are added to the database with csv import functionality or by hand with setting the image path with catalog image browser.
  • Our Imager.php helper will try to create the resized image in i/m folder: i/m/image.jpg for sony and i/m/image.jpg for samsung wich cause image collisions.

Solution:
Add the parent folder path to imagename, if image path doesn't match the standard pattern: filename[0]/filename[1]/filename.

Example:
i/m/image_sony.jpg
i/m/image_samsung.jpg

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant