Help for Aimeos

Don't think that this is a problem of Aimeos. The credentials in the Laravel .env file doesn't allow the Laravel migrations to access the database or at least the MySQL information schema.

Which payment gateway do you use?
Seems like it's an Omnipay gateway and "omnipay.onsite = 1" is configured in the service provider in the admin interface.

I must be honest and say that the documentation confuses me quite a lot. I thought changing a theme would work like the templates, through the extension, and not through the Default.html template in Aimeos.Shop. What happends when we update? Does the template default to its original code, or does i...

The Flow framework is most probably the hardest one to use because the framework is very complex so integration isn't easy. Laravel is much easier for example and the Aimeos integration works well for many developers adapting it to their needs.

Best is to create a new page for this.
An alternative would be to configure a default category ID of a category that has no products:
https://aimeos.org/docs/Configuration/C ... id-default

Where is your own extension located in your Flow application?

Simply remove the "catalog/lists" part from the page you want this to happen:
https://github.com/aimeos/aimeos-larave ... op.php#L21

Most probably you want to create a new page. Then, please have a look into these articles:
https://aimeos.org/docs/Laravel#Pages

Parallel processing in the tasks led to the problem that you don't see the reason immediately. Most of the time, you need to have a look into the madmin_log table for details. If you run "composer update", you will get a new version of the Aimeos 2017.10 core. It contains a change that pri...

It doesn't work that way. The "client/html/common/template/baseurl" setting is only used to find the CSS files that are included in the HTML e-mails. In Flow, there's a layout file that contains the URLs to the CSS and JS files: https://github.com/aimeos/aimeos-flow/blob/master/Resources/P...

We got a bit further: The problem isn't RealUrl but TYPO3 seems to cache the language selector. The language URLs then contain old parameters (e.g. f_catid/d_prodid) so switching languages also switches back to previous list and detail views. Does anybody know how to configure the TYPO3 language men...