Bernhard Rusch

@jdreesen this is not yet finally decided, but currently our favorite is to separate them out into their own repos. There are multiple reasons for that, mostly organizational wise, e.g....

Strategy is as follows: 1. bundles which will be a community bundle in future, will be moved to their own repos / packages 2. functionality / bundles that are going...

See https://github.com/pimcore/pimcore/issues/12959#issuecomment-1255083803

Let's keep this open for discussion for now ...

Obsolete, see https://github.com/pimcore/pimcore/issues/12968#issuecomment-1230234838 Thanks anyway for your PR 😊

That's probably not only the case for assets, but also data objects and documents, right? And there's already an existing listener for that, that uses the message queue for processing...

Thank you very much! 👍

We should consider JS BC layers here as well, such as: https://github.com/pimcore/pimcore/blob/d34b60574994ea91db51758603c056b3033a3e52/bundles/AdminBundle/Resources/public/js/pimcore/object/classes/layout/layout.js#L29 https://github.com/pimcore/pimcore/blob/2f18a0f26380c56b609d937b40d2050c8d1a3e1a/bundles/AdminBundle/Resources/public/js/pimcore/object/fieldlookup/helper.js#L27

I'm not entirely sure if this is really the intended behavior ... Changing the language in the grid is ONLY for localized values. Translated labels of select data-types are not...

The value is still right, the value is NOT the label and the export should export the actual data, not some translated labels. Different example, select is used as an...