- Issue created by @Anas_maw
- 🇨🇦Canada jdhildeb
This is my experience, too. Stay away from version 1.8. I upgraded to 1.8 on a site, worked through several issues including
* https://www.drupal.org/project/workflow/issues/3454189 🐛 hook_update_8003 to 8.x-1.8 installs optional config and breaks my site Active
* https://www.drupal.org/project/workflow/issues/3452716 🐛 Warning : Undefined array key "to_sid" in WorkflowTransitionElement::copyFormValuesToTransition() line 356 when using Ajax button from other field FixedI applied patches from the git repo, tested, had my users test, and thought I was good. But after deploying, my users are getting the "This value should not be null" error (possibly other edge cases of 3452716). And I discovered that handling of the "transition pre" is broken in 1.8. I will log this as a separate issue.
I appreciate the work of the developers and apologize for what may be seen as venting. And I know that they need more specifics in order to reproduce and fix the issues.
My purpose in adding to this issue is that Drupal users should see this info and avoid this version.
- 🇬🇧United Kingdom problue solutions Northern Ireland
It's unusable to be honest, there are multiple bugs that make it completely broken even in basic scenarios, not sure how this has been released as stable.
I went back to 1.7 but there is something broken with that version that means you cannot use date fields on workflow forms, at least in Drupal 10.4 anyway.