- Priority: 0
- Status: Queued
- Theme: Alysum
-
Assigned To:
Fred
- Private: No
- Open Date: 08.07.26, 15:29
- Opened by: Niko Magnus
Ticket #26531 - Image Carousel Widget loads broken image path (module-prefixed URL instead of root path)
Hello,
I’m using Creative Elements on PrestaShop with the Alysum theme, with images stored in /img/cms/.
Image Widget: works correctly — images selected from the media library display fine.
Image Gallery Widget: works correctly as well.
Image Carousel Widget: broken. When selecting an image from the media library (e.g. /img/cms/cat-rome.jpg, which loads fine when accessed directly), the widget instead requests /module/creativeelements/img/cms/cat-rome.jpg — an incorrect path prefixed with the module’s own folder — resulting in a 404 and a broken image icon in the back office. Everything’s fine in front office, though.
This is fully and consistently reproducible. The issue appears isolated to the Image Carousel Widget’s path resolution, since the other two image-related widgets work as expected with the same images.
Could you please look into this?
Prestashop9.1.1
Note : I contacted Creative Elements and the ytold me that : “Since Creative Elements is included and used through the Alysum theme, please contact the Alysum theme developers regarding this issue. They are responsible for supporting the Creative Elements integration provided with their theme.”
Comments
Hi, Niko Magnus.
Please fill out all necessary fields in your profile https://support.promokit.eu/myprofile to access to your FTP Server to let me debug the issue
Hi, Fred.
Done.
Please test it out, it should be working now
Updated file
Hi, Fred.
Nope, it does not work, here.
It works for me https://mega.nz/file/cIRG2Z6S#WYvrSpZM0ySROGLlTPfzuzyIQ8-04TXLGAzhrfEkK9 I check the Image carousel widget as you wrote
It still doesn't work in Back office but is OK in front.
In BO, the URL called is /module/creativeelements/img/cms/*jpg but in front is /img/cms/Design/*.jpg (which is the correct url)
linked is the image in the BO.
Note : cache emptied both in prestashop and the navigator.
Attachments: