Help for Aimeos

You can overwrite the manager class to. Create a new class in your extension in the ./lib/custom/src/MShop/Customer/Manager/Myproject.php extend from \Aimeos\MShop\Customer\Manager\Laravel and overwrite the methods you need. Afterwards, configure your shop to use your new class with https://aimeos.o...

If I remember correctly, this is fixed in dev-master and will be part of the release next week.

No, it would still be one backend where editors can switch between shops.
But if you want to sell tires and shirts in one order, this doesn't work. Then, we would recommend the suggestion of Metalics to hide the attributes and types with no products found via Javascript.

Yes, aimeos-core in an own branch would be the best place. At first, we need to add the required table in https://github.com/aimeos/aimeos-core/blob/master/lib/mshoplib/setup/default/schema/attribute.php . I would suggest that layout: 'mshop_attribute_type_i18n' => function ( \Doctrine\DBAL\Schema\S...

Yes, create a file "mshop.php" in the "./lib/custom/config/" directory of your extension with the same array structure and add the SQL statements you want to overwrite.

We've updated the product CSV file and the required mapping in the Wiki:
https://aimeos.org/docs/Developers/Cont ... lt_mapping

Can you please update your mapping and try to import the new file?

Have you read this article?
https://aimeos.org/docs/Laravel/Extend_ ... os_objects

It explains how to access the Aimeos data from a Laravel controller.

Just to make sure we aren't talking about different things: What is a "security price" in your context?

The example CSV doesn't fit to the current importer requirements any more. It needs at least the currency ID for each price and the non-existing attribute type (import-test) is also invalid. We will update the example CSV so it matches the implementation in version 2017.10.

Thanks for your patience!

Performance of Gettext mo files isn't a problem because they can be cached in APC if you enable that. But in your case it makes sense to use a translation table to for the attribute types if those values change more or less every day. Are you interested in creating a patch to implement that? We woul...