My view contains both draggable views sorting and vbo operations. It works great except the "Modify values" action witch does not provide "Next" button on the values modification step form.
When I remove draggable views sorting from the view the button is displayed correctly so it seems the DraggableViews is overwriting $form['actions'] or $form['actions']['submit'] of that step.
I know this might be and issue for VBO so please feel free to move it but I'm using version 3.1 of VBO and this was working fine before I've updated DraggableViews at some point two weeks ago.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | next-button-missing-in-modify-values-action-1914890-3.patch | 728 bytes | philipz |
Comments
Comment #1
cjtriplett commentedI have the same issue.
Comment #2
philipz commentedProblem seems to be gone now in combined dev versions of both modules.
Comment #3
philipz commentedWell it was not fixed after all. I've found and fixed the condition responsible for hiding submit button. I don't know if this is a proper way to do this but works fine for me. Might be to VBO oriented though.
Comment #4
istryker commentedIMO, this is not the way to do it. I do not like injecting other modules field checks into draggableviews hooks. That being said, VBO is now in D8 core so I might be willing to commit this
Comment #5
philipz commentedI understand that mixing other modules field checks is not a clean solution but it's not any dependency in this case. I don't know if there's any other way to check if the button should stay if we come from bulk views operations or not.
Including this patch that would be very helpful as both modules used combined are super powerfull. Do you know when will you commit this?
Comment #6
istryker commentedThere is another issue, that has an issue with VBO. It fixes the form_alter hook better. Still a special case for VBO.
Fixed in Patch #12 of #2013839: Work with Views Bulk Operations
Marking as duplicate.