Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Translatable fields might have the need to share the values of some field columns, for instance a file field might have a textual description which need to be translated while the fid itself should be shared among the field translations.
A possibile solution to this need could be introducing synchronization at field column level. On the translation UI we could only introduce a warning that changing the field value would trigger a change into all the field translations. We could then have a field set in the field settings form allowing to choose which solumn need to be synchronized.
| Comment | File | Size | Author |
|---|---|---|---|
| #14 | et_sync-1133038-14.patch | 7.33 KB | plach |
| #8 | et-1133038-8.patch | 7.38 KB | plach |
| #7 | et-1133038-7.patch | 6.52 KB | plach |
| #6 | et-1133038-6.patch | 6.28 KB | plach |
| #5 | et-1133038-5.patch | 5.29 KB | plach |
Comments
Comment #1
vasikesubscribe
Comment #2
plachComment #3
plachHere is a patch. It provides column synchronization for file and image fields. To test it apply the patch, clear the caches and enable field synchronization in field settings.
Comment #5
plachThis one should work.
Comment #6
plachBetter one: now elements may be freely reordered without triggering synchronization. I think this is ready to go. Please confirm.
Comment #7
plachSmall enhancement.
Comment #8
plachFixed a couple of edge cases.
Comment #10
plach#8: et-1133038-8.patch queued for re-testing.
Comment #12
plachRight, this has been rolled against the ml_edit_form branch.
Comment #13
plachAlso this one is waiting for #1495648: Introduce entity language support.
Comment #14
plachThis works even with non existing field translations.
Comment #15
plachTotally needs test coverage.
Comment #16
plachGoing to commit soon.
Comment #17
plachCommitted and pushed.