Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[REF] Fix issue where forceing sequential broke webform API chained u… #23674

Merged

Conversation

seamuslee001
Copy link
Contributor

…sage

Overview

5.49 backport of #23672

ping @eileenmcnaughton @totten

@civibot
Copy link

civibot bot commented Jun 2, 2022

(Standard links)

@eileenmcnaughton
Copy link
Contributor

This has been confirmed by @KarinG / @demeritcowboy so mop

@KarinG
Copy link
Contributor

KarinG commented Jun 2, 2022

Our WFC tests are still running too.

@demeritcowboy
Copy link
Contributor

I don't know about "confirmed" - I'd agree this is the cause, and that a quick simulation of a similar api call returns the right thing. And it was probably a typo to convert sequential to enforced. Nobody's run it though and as noted the webform tests are still running.

@eileenmcnaughton
Copy link
Contributor

Ok- will wait for you to confirm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants