Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Situation: page contains a form with id="edit-target", hence "edit-target" in the translation form becomes "edit-target-1". JS in l10n client depends on "edit-target" and saving of new translations stops working.
Issue reported originally o OpenAtrium tracker https://community.openatrium.com/issues/node/685
Patch a-comin.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | classtarget.patch | 6.05 KB | gábor hojtsy |
| #3 | edit-target.patch | 3.72 KB | gábor hojtsy |
| #1 | 616106-1_use_classes.patch | 3.61 KB | alex_b |
Comments
Comment #1
alex_b commentedThis patch uses classes instead of ids for selecting the target element and fixes the problem reported here https://community.openatrium.com/issues/node/685
Comment #2
gábor hojtsyLooks good. Did you notice any other similar places where IDs are used as selectors and can break while we are at it?
Comment #3
gábor hojtsyOk, here is an updated version, committed to D6. Needs to be ported to D7.
Comment #4
tinker commentedNo flipping way... I just spent hours figuring all of this out and rolling a patch for D6-dev. Can't believe I missed this post. It would have really helped me work through my problem faster. Oh well, I was still having problems with the dev version because the form ID was not the same as the rendered version in the browser e.g. form ID "l10n-client-form" was "l10n-client-form-1" in my browser. I have introduced more classes to fix the issues I was having in my post http://drupal.org/node/836560
I think I am quite well versed in this now and noticed other ID references that could cause problems. So if you need some help rolling more patches let me know.
Comment #5
gábor hojtsyPorted to D7. Seems to be working fine.