Project:
| View Revisions: Issue #40911 | [ Back to Issue ] | ||
| Summary | 0040911: Limitations in RemoveImagesEventHandler | ||
| Revision | 2019-05-20 12:07 by caristu | ||
| Description | There are some limitations in the RemoveImagesEventHandler observer: - The "Dummy Image" mechanism used when deleting an image property that is mandatory does not support multiple clients: if the dummy image is created in one client, then it will not be possible to create it in another client (because the dummy image has a fixed id) - When updating the image of a particular record there is a mechanism that checks if the "old" image is being referenced in order to proceed with its removal. But this check is only done for the Product entity...this means that for example when updating the image of a product category the usage of the "old image" is performed just against the product images. This can cause to not make possible to replace the "old" image of a product category if exactly the same image is used by some other category. |
||
| Revision | 2019-05-20 12:03 by caristu | ||
| Description | There are some limitations in the RemoveImagesEventHandler observer: - The "Dummy Image" mechanism used when deleting an image property that is mandatory does not support multiple clients: if the dummy image is created in one client, then it will not be possible to create it in another client (because the dummy image has a fixed id) - When updating the image of a particular record there is a mechanism that checks if the "old" image is being referenced in order to proceed with is removal. But this check is only done for the Product entity...this means that for example when updating the image of a product category the usage of the "old image" is performed just against the product images |
||
| Revision | 2019-05-20 12:02 by caristu | ||
| Description | There are some limitations in the RemoveImagesEventHandler observer: - The "Dummy Image" mechanism used when deleting an image property that is mandatory does not support multiple clients: if the dummy image is created in one client, then it will not be possible to create it in another client (because the dummy image has a fixed id) - When updating the image of a particular record there is a mechanism that checks if the "old" image is being referenced in order to proceed with is removal. But this check is only done for the Product entity...this means that for example when updating the image of a product category the image usage is performed just against the product images |
||
| Revision | 2019-05-20 11:52 by caristu | ||
| Description | There are some limitations in the RemoveImagesEventHandler observer: - The "Dummy Image" mechanism used when deleting an image property that is mandatory does not support multiple clients: if the dummy image is created in one client, then it will not be possible to create it in another client (because the dummy image has a fixed id) - When updating the image of a particular record there is a mechanism that checks if the "old" image is being referenced in order to proceed with is removal. But this check is only done for the Product entity...this means that for example when updating the image of a product category the "old" image is not properly cleaned up. |
||
| Copyright © 2000 - 2009 MantisBT Group |
 |