Major Feature #62292
Support for entity translation
Status: | New | Start date: | 2014-10-17 | |
---|---|---|---|---|
Priority: | Should have | Due date: | ||
Assigned To: | - | % Done: | 0% |
|
Category: | I18n | |||
Target version: | TYPO3 Flow Base Distribution - 2.x | |||
PHP Version: | Complexity: | |||
Has patch: | No |
Description
It seems TYPO3 Flow doesn't support the translation of entities currently in a generic way. So either you choose some non generic approach like the following and do it again and again for all your entities which needs to be translatable:
/** * @Flow\Entity */ class Product { /** * @var Product * @ORM\ManyToOne(inversedBy="translations") */ protected $translationOriginal; /** * @var Collection<Product> * @ORM\OneToMany(mappedBy="translationOriginal") */ protected $translations; /** * @var string */ protected $locale; ... }
Or you try to implement it in a aspect oriented way like this, which of course might be a lot of work to realize:
/** * @Flow\Entity */ class Product { /** * @var string * @Flow\Translatable */ protected $name; ... }
Currently we have some multi-language projects in the pipe for which we could use TYPO3 Flow but without the aspect Translatable
it makes our decision not so easy.
Please excuse if this is a stupid feature request. The examples are from Akii and his article My thoughts on Entity Translation in TYPO3 Flow. So are there any plans about it or is this a pretty rare aspect?
History
#1 Updated by Artus Kolanowski 10 months ago
Sorry, I forgot to mention that the aspect Translatable
also would require an API for the CRUD operations of the translations of properties.