Pieter Hoste
Pieter Hoste
In case people haven't seen it yet, there was recently a change published in version 104.3.4 that might help against this problem: https://github.com/akeneo/magento2-connector-community/compare/v104.3.3...v104.3.4 In our case, using `ROW_FORMAT=DYNAMIC` in combination...
Possible fix here I think: https://github.com/akeneo/magento2-connector-community/pull/643 Maybe somebody can confirm?
Small update: just tested this on a staging environment with MySQL 8.0.36 (Percona) where MyISAM is disabled, and it works good without problems. So that's a good sign!
Yes, that was already mentioned on https://github.com/akeneo/magento2-connector-community/issues/177#issuecomment-805318039 But that will require a lot more work, possibly multiple days of refactoring, so I chose the quick solution for now.
You should change your condition from `ALL` to `ANY`. Or alternatively only add one condition but use the `is one of` and add all your Attribute Sets in that one...
Yeah, in Magento we don't use keys for translations, we use the actual English phrases that are used in the application, and those phrases are then translated in different languages...
It indeed sounds like an idea is shaping here However, the Magento case is even more complex, because there are a lot of different layers of translations involved where we...
Okay great Here's a proposal, not really thought through but might be a good start. I would propose we have something like this that we can configure: ```xml ... /path/to/the/custom/translation/file/for/the/project/de_DE.csv...
Small update from our part, because we've decided to take another approach and a colleague of mine already finished an initial working prototype. Unfortunately it's in private code part of...