- Issue created by @parasxous
- First commit to issue fork.
- Status changed to Needs review
11 months ago 11:18am 10 June 2024 - Status changed to Needs work
11 months ago 12:08pm 10 June 2024 - First commit to issue fork.
- Status changed to Postponed: needs info
11 months ago 9:13am 14 June 2024 - 🇳🇱Netherlands Lendude Amsterdam
Can we get a real issue summary here? When is this happening? What other modules are you using? Can you reproduce this on a clean Drupal install?
Just adding an isset() is usually just masking the real issue.
- 🇳🇿New Zealand quietone
I have restored the standard issue template. Moving to 11.x, this needs to be fixed there first and then considered for backport.
Thanks for updating the issue summary, that helps. There are still questions from a maintainer that should be answered, "When is this happening? What other modules are you using? Can you reproduce this on a clean Drupal install?"
And I see that an exposed filter is used. There are many issues related to exposed filters, has a search of those issues been done to ensure this is not a duplicate? This search link → may help with that.
- 🇺🇸United States smustgrave
can the steps be written out don't really follow adding the fields as steps. If no steps can be provided think this will be closed out.
I just (08 April 2025) had the exact same problem on Drupal 10.4.6, while testing the new development version of drupal/workflow (1.x-dev, the future v1.9) in a huge Drupal project.
I have a battery of behat tests (about 200 tests), which fail with the new drupal/workflow module version unless I apply patch #9 above. The patch also makes sense to me. I would backport it if possible.