Closed (won't fix)
Project:
Workflow buttons
Version:
2.0.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 May 2026 at 21:09 UTC
Updated:
7 May 2026 at 14:27 UTC
Jump to comment: Most recent
Comments
Comment #2
jcandan commentedThinking more about the original issue description, maybe it is obvious to which form display a user might be routed--we just route to the canonical form display route. Which form display is used is handled by just landing on the edit route.
I attempted a patch where we did just that, and simply forwarded the error messages on during the redirect. However, for my use-case, this doesn't quite address our niche issue: we change the error messages.
As it stands, in a
hook_form_alter()$form['#validate']callback, the$form_state->getErrors()are very different when submitting from the view display rather than the form display. So, our niche error manipulation logic needs to change--Or, rather than capture and pass on the validation error messages, the validation needs to be run again once redirected to the form display.
Not sure yet if this is a good general case or feature. Digging.
Comment #3
jcandan commentedNot a recommended path. We ended up abandoning having the buttons on the view display.