Help for Aimeos

Laravel authentication is already securely designed so there's normally no need to improve that. If you are using Aimeos in very sensible environments, you can add 2FA in addition. There are tutorials for Laravel explaining how to add that.

Yes, if you return true/false in the isAvailable() method of the service provider. Only those for which true is returned are shown.

If you want to use several delivery options, you have to create them ahead of time but the price can be dynamic. If you want to have a totally dynamic selection, than the list entries you can create in getConfigFE() are better.

It's one option to return an entry in getConfigFE() with a "list" configuration but that has limitations displaying the price (you would have to do that in the label). Another option might be to return several delivery options, e.g. for standard or express delivery.

Yes, please create a PR and we are happy to merge the change into the core. It will be part of the next minor release then.

Yes, you can adapt the existing Aimeos pages without problem, e.g. for the checkout page have a look here:
https://aimeos.org/docs/latest/frontend ... omponents/

There's no CSV exports for products because the file format isn't suitable to handle the complexity of the data structures.

This line is added automatically when you create a new TYPO3 extension using the extension builder. Checked that again and it worked.

You are right, that's a problem because the sitemaps are overwritten. Until it's fixed, you can extend the job controller and overwrite the "filename()" and "indexFilename()" methods here to include the site code: https://github.com/aimeos/ai-controller-jobs/blob/master/src/Contr...

There's a "product:prop" search function available: [/quote]
You can only search for exact values, not for strings inside.