Problem/Motivation

I have a complicated case: a multi-page webform that has numerous elements. When upgrading from 6.3-beta5 to 6.3-beta6, a new error is introduced into the form. The error seems to be AJAX related because it affects a custom composite field that has Add and Remove item buttons. It also affects a computed twig field.

The bug related to the computed twig field is obvious. Prior to upgrading webform, the computed value changes immediately whenever one of the fields contributing to the computed value is changed. After upgrading webform, the value no longer changes immediately. The submitted value is correct, so the value appears to update when the form is submitted, but it does not update immediately as expected.

The bug related to the custom composite field is more complicated. Prior to upgrading webform, the add and remove item buttons function correctly, with a new custom composite item immediately appearing (or disappearing) as expected. After upgrading webform, when attempting to add or remove a custom composite item, the form will occasionally show the WSOD. On other occasions, the page will reload instead of having the proper form elements added (or removed) via AJAX. Also, I will occasionally see a validation error on a completely different form field. This seems to indicate that the browser tried to reload the form and couldn't because of validation.

Oddly, I have not seen any errors in the JavaScript console relating to these problems. So, I don't know if it's AJAX or not. But it seems like it is.

Reverting webform back to 6.3-beta5 resolved the problem, so it's definitely a beta6 issue. I looked at the changelog but did not see anything that would seem to be related to AJAX.

The website is on the latest version of Drupal 10 (10.5.7).

Comments

aaronpinero created an issue. See original summary.

liam morland’s picture

Version: 6.3.0-beta6 » 6.3.x-dev

Please use git bisect to determine which commit caused this problem.

aaronpinero’s picture

Status: Active » Closed (outdated)

Yesterday I updated to the latest beta (7) and the issue appears to be resolved.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

liam morland’s picture

Status: Closed (outdated) » Closed (cannot reproduce)

Thanks for following-up.