Help for Aimeos

There are a few problems in your code. $productCode = $request->input('product_id'); Use the product ID if possible because it's easier to handle. $filter = $productManager->filter(true); $filter->add('product.code', '==', $productCode); $filter->add('product.status', '==', 1); filter(true) automati...

Yes, because the URLs will change when you use the #gigacommerce extension and you would have to change the site IDs of all records to move them to different sites

No, that isn't the case.

Having /uploads/tx_aimeos/ prefix in the file path is wrong. Do you know where this comes from?

If you don't want the site code in the URL it's best to use the domain as site code: 'routes' => [ 'admin' => ['domain' => '{site}', 'prefix' => 'admin', 'middleware' => ['web']], 'jqadm' => ['domain' => '{site}', 'prefix' => 'admin/jqadm', 'middleware' => ['web', 'auth']], 'graphql' => ['domain' =>...

No known issues but most likely, no one did such an update before. You have to upgrade to a supported LTS version as soon as possible because that version has security issues and isn't even supported by ELTS any more.

The Aimeos system itself is free - I deployed it on my server, turned on "SHOP_MULTISHOP=true", prescribed routes for level 3 domains (for stores) and that's it. I understand that stores for sellers are created in the "Supplier" section. This isn't correct. If you create a SaaS-...

Your PostgreSQL database isn't listening on 127.0.0.1:5432

Most likely, your decorator doesn't use the correct namespace and directory:
namespace: Aimeos\Client\JsonApi\Customer\Address\Decorator
directory: src/Client/JsonApi/Customer/Address/Decorator/AddressDecorator.php

Use this to remove all listeners: