- Issue created by @vegardjo
- π©πͺGermany jurgenhaas Gottmadingen
The reason is that with the ajax request the form ID changes and the Gin javascript is correctly updating the new form ID for the action buttons and adds a new event listener to them. However, the previous event listener remains in place, and that uses the old form ID.
The solution can be one of these:
- Remove the old event listener before adding the new one
- Let the old ones run as well but prevent the error from happening
Will push an MR in a minute.
- Merge request !546Issue #3492920 by vegardjo, jurgenhaas: Js error when saving reference field β (Merged) created by jurgenhaas
- π©πͺGermany jurgenhaas Gottmadingen
OK, please give this MR a try, it should be fixing it.
- π³π΄Norway vegardjo
Thanks! Tested with this as a patch, and the described problem went away. Also tested creating various other field types, editing existing field etc., with no console errors. :)
- πΊπΎUruguay fanton Uruguay
I confirm that the problem in the node editing form is solved.
-
saschaeggi β
committed 60ed0160 on 8.x-3.x authored by
jurgenhaas β
Issue #3492920 by vegardjo, jurgenhaas: Js error when saving reference...
-
saschaeggi β
committed 60ed0160 on 8.x-3.x authored by
jurgenhaas β
-
saschaeggi β
committed 139691b1 on 4.0.x authored by
jurgenhaas β
Issue #3492920 by vegardjo, jurgenhaas: Js error when saving reference...
-
saschaeggi β
committed 139691b1 on 4.0.x authored by
jurgenhaas β