Updated: Comment #21
The "field synchronization" feature provided by the FieldTranslationSynchronizer class is written with the "old / BC" syntax for accessing field values. It works in HEAD because calling code takes care of passing entities wrapped in the BC layer.
rewrites a fair amount of the code flow surrounding FieldTranslationSynchronizer, and triggers hard to debug test fails related to the BC layer.
At this point in the cycle, all fieldable entity types in core implement EntityNG, aside from the 'test_entity' used in some Field API tests, that do not leverage "field synchronization", that is fully tested separately.
So, it makes more sense to move that code to work on EntityNG, which will need to happen anyway, and state that it will not work on the one entity type that is not NG yet, rather than spending time in debugging the BC layer.
Rewrite field sync on top of NG entities
User interface changes
The "field synchronization" will not work on the 'test_entity' entities still used by some Field API tests.
This is blocking these:
- All issues with the Entity Field API tag to show up http://entity.worldempire.ch/conversions.
|PASSED: [[SimpleTest]]: [MySQL] 58,566 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 57,537 pass(es).|
|PASSED: [[SimpleTest]]: [MySQL] 57,393 pass(es).|