- 🇦🇺Australia mstrelan
BulkForm was moved to views.module in #2916451: Move everything related to Bulk Form to Views module → , updating component
The core BulkForm plugin first executes an action and only then the confirm form is beeing displayd if it exists.
This leads to unlogical behaviour where the action execute method has to contain code for saving results to a temporary storage instead of actually executing the action.
The problem has been solved in Views Bulk Operations → module, it'd be possible to implement a similar solution in core and update the existing node delete action at the same time.
The main problem here is that by doing this the right way, modules already implementing the confirm_form_route_name the old way (and using the execute method to save results to a temp storage) will stop working.
This way of doing things can be marked as deprecated, but how can we make the BulkForm::viewsFormSubmit know if a module is using the old (deprecated) or the new method?
The only solution that comes to my mind is introducing a new method in the action interface like 'doExecute' that is used only for executing the action and checking if that method exists in BulkForm.
If anyone is interested in making this right or has better ideas to solve the backward compatibility problem, please let me know.
Active
11.0 🔥
views.module
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
BulkForm was moved to views.module in #2916451: Move everything related to Bulk Form to Views module → , updating component