Help for Aimeos

No, I've said "assign an ID locally and just overwrite the data in ES (without fetching the products first)". Products need to be in ES only but not with an autogenerated ID from ES. Then, you can overwrite the products in ES without the need to fetch them first.

The XML importer is the fastest standard option but it still fetches the products, updates them and stores everything back. When using ElasticSearch and your extension, it's much faster to assign an ID locally and just store/overwrite the data in ES without fetching the products first. Then, it's po...

Create e.g. a ./setup/default/elastic/product.php in your own extension and add your new field there: return array( 'base' => function ( array $mappings ) { $map = [ 'base' => [ 'properties' => [ 'myfield' => [ 'type' => 'date', 'format' => 'yyyy-MM-dd HH:mm:ss' ] ], ], ]; return array_replace_recur...

Thanks a lot for your post!
The wrong exceptions has been fixed and tests has been added. A new release is also tagged.

There had been two problems: - The admin backend used only the product manager to update the ratings, not the index manager - The ElasticIndex class didn't forward the new rating to the product manager This has been fixed and new 2022.10.x versions of the aimeos/ai-admin-jqadm and aimeoscom/ai-elast...

Your test file is wrong because each field is enclosed by """ instead of "

The EU Vies server doesn't respond properly (too many requests according to the first error message).
There's nothing you can do besides allowing customers to continue if the VIES server is not available using:

There was a configuration missing for the price manager. We've added that and created a new release of the aimeoscom/ai-customergroups extension. Can you please update and try again?

Did you configure the extension according to the ./vendor/aimeoscom/ai-customergroups/README.md file?

Yes, ElasticSearch doesn't allow migrating properties like relational databases. Thus, it requires in many cases recreating the index and re-importing the data. This is only not necessary if you add the new properties to the schema before you insert new data. The easiest way in production environmen...