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.
In our setup of Drupal 6, we are using I18N and also the i18n sync module. It happens that when one person is editing a node and another person comes along to edit another node in the translation set, saving one of the nodes causes the other node to not be allowed to be saved.
Using the attached patch, when a person starts editing one node in the translation set, it causes the content locking messages to appear on any other nodes in the translation set. This helps prevent users from losing work.
Let me know if you have any questions or concerns with this.
Trevor
Comment | File | Size | Author |
---|---|---|---|
#2 | add_option_for_locking-1817288-2.patch | 2.06 KB | SpaghettiBolognese |
content_lock_lock_translation_set.patch | 2.21 KB | tschellhorn |
Comments
Comment #1
pandaski CreditAttribution: pandaski at XiNG Digital commentedComment #2
SpaghettiBolognese CreditAttribution: SpaghettiBolognese at Emble commentedWe're experiencing exactly the same problem with this module on Drupal 7 with i18n_sync. I've updated the patch so it will apply clean on 7.x-2.x (all credits go to tschellhorn).