Help for Aimeos

We support all payment gateways through Omnipay and if one of the drivers is out of date or missing, you should update or implement it. This should be preferred over a direct integration using the Aimeos payment service provider interface.

Are the HTML entities in the XML file or only after the import in the new system?

Don't create the index manager (you don't use it) and open a DB transaction which you don't commit afterwards. All your changes are rolled back at the end of the task.

Do you have more information about what you import, your configuration and when that happens?

The footer is part of the base Blade template and the header is a combination of code from the same template and the output of some HTML client components: https://github.com/aimeos/aimeos-laravel/blob/master/views/base.blade.php You can override that template in your application like described here...

We are unable to reproduce the issue. We've created a new scheduler task for the media/scale job and executed it using "vendor/bin/typo3 scheduler:run -f -i <task id>". There wasn't an exception in our case. Can you please provide more details about your setup (output of "composer sho...

Thank you for your bug report!
The issue has been fixed in the latest 2025.04 version. Please run "composer up" to get the latest version

Does the URL you try matches with the path you've entered in the field in the other tab and the route you can see executing "php artisan route:list"?

Did you click outside the content iframe before clicking on the Save button? If you click directly on the Save button, the content is not updated before sending the request to the server. This is one known issue with the used GrapesJS integration.

Please keep in mind, that only 100 products are loaded by default if you just remove the existing limit and it doesn't work if you have thousands of product in one category.