- Issue created by @joel_osc
- 🇫🇷France dcoppel
Hi, I'm agree with you. I think it's the same issue that mine : https://www.drupal.org/project/workflow/issues/3458984 🐛 TypeError: 'WidgetBase::errorElement(): Argument #1 ($element) must be of type array, null given, called in WidgetBase.php' Active
But it seems that nobody works on it... - 🇩🇪Germany Rudi Teschner
This issue still seems to be a problem, we get the message after upgrading to 1.8 or latest dev too in our project too. If me or my colleague have time we will try to dip into this issue in the next days.
First guess is that it could be related to https://www.drupal.org/project/workflow/issues/2926094 🐛 WorkflowTransitionElement is called twice on a form Fixed and commit https://git.drupalcode.org/project/workflow/-/commit/ad73361bec3d8fc6ce8... but we will see.
- 🇳🇱Netherlands johnv
Please check latest dev-version, that contains 🐛 New transition is not properly created in 8.x-1.8 Active
- 🇩🇪Germany Rudi Teschner
@johnv: I still get the validation error ("This value should not be null.") when i update workflow to latest dev version (#3caa0ec) in my existing project - for new content as well as when editing/saving existing content if that helps.
- 🇩🇪Germany Rudi Teschner
I noticed that once i change the display of the field in the node form display from "workflow transition form" to "checkboxes/radio buttons" I was able to save nodes again, maybe that helps narrowing it down
- 🇳🇱Netherlands johnv
I realized that that might be the problem, so I tested and corrected that situation in 🐛 New transition is not properly created in 8.x-1.8 Active .
- 🇳🇱Netherlands johnv
I guess this is fixed now with latest dev. Please reopen if not.
Automatically closed - issue fixed for 2 weeks with no activity.