Help for Aimeos

Done and that shouldn't be a problem in the future any more.

This is one possible option but it doesn't exists in Aimeos yet you have have to build it on your own. Another option would be to use the product ID in the URL by removing "d_prodid" from the "client/html/catalog/detail/url/filter" option: https://github.com/aimeos/aimeos-laravel...

Yes, overwrite this configuration in your ./config/shop.php and add your subparts where it should be displayed:
https://github.com/aimeos/ai-admin-jqad ... #L123-L138

In Aimeos 2024.x it's fairly simply because you can overwrite the Aimeos.app() method in your own JS file: https://github.com/aimeos/ai-admin-jqadm/blob/master/js/admin.js#L123-L139 Something like this should do the job: // in libs.js to create a new JS bundle using NPM import 'vuetify/styles' impor...

The base URL for images is defined here: https://github.com/aimeos/aimeos/blob/master/config/shop.php#L137 In the templates, the real URLs are created by calling the "$this->content()" view helper, e.g.: <img src="<?= $enc->attr( $this->content( $mediaItem->getPreview(), $mediaItem->g...

Did you enable/change the ASSET_URL in your .env file?
https://github.com/aimeos/aimeos/blob/m ... example#L7

If yes, try to remove that setting as it's only useful for remote cloud storages

You can influence what the browser is choosing by removing e.g. the 960px image size to force the browser to use the next best one, which is 720px in your case.

You have to index your products so they are found. Assuming you are using Laravel, execcute this command:

Everything is correct but the browser selects itself which image it will use. You can only influence that partially with a different imageset-sizes configuration.

Would be interesting to find out why and what line is causing that.