View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002248 | OXID eShop (all versions) | 2. ----- eShop backend (admin) ----- | public | 2010-12-09 16:13 | 2012-12-10 14:22 |
| Reporter | faltmeyer | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Summary | 0002248: wrong references on image | ||||
| Description | I do upload images via directimport, not with backend. First I put alle images in the Folder master/1...12. Then I will go to the article in Shopfrontend. Now, all images will be created automatically. Now I will change one of these images image. I will upload the new image into the folder master/4 and will reset the field oxpicsgenerated in oxarticles. Now I will refresh the detail site of the article and the new image will be created. Unfortunately the new image is only referenced on a temporary file in folder tmp. In database is still the old imagename. If I delete all files in tmp folder the old image will appear on detail of this article. | ||||
| Tags | Export, Import | ||||
| Theme | |||||
| Browser | All | ||||
| PHP Version | any | ||||
| Database Version | any | ||||
| duplicate of | 0002122 | resolved | Linas Kukulskis | New product pictures will not be generated |
|
|
Reminder sent to: faltmeyer Hi, In this case, after new image file is uploaded - it's not enough to reset the oxpicsgenerated setting, but also need to update the DB entry in OXPIC field with new file name. So this behavior is intended, it's not a bug. |
|
|
if my new image and the old image have the same name, the shop will copy the new image into the pictures folder and give a new name to it like image(1).jpg. In this case, I cannot update the database because I do not know the the imagename, given by shop. |
|
|
Reminder sent to: faltmeyer Hi, Now it's clear - if the new file name is exactly the same as previous file - then this bug is already fixed in eShop version 4.4.5. Please check the bug entry 0002122. If you still experience this issue on the 4.4.5 version, please ReOpen this entry with comment. |
