Closed (fixed)
Project:
DraggableViews
Version:
7.x-2.x-dev
Component:
Miscellaneous
Priority:
Major
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
19 Jul 2011 at 00:28 UTC
Updated:
14 Jul 2013 at 13:46 UTC
Jump to comment: Most recent file
Comments
Comment #1
bojanz commentedThe VBO field just adds a checkbox that points to the entity id, so it should work if DraggableViews works.
Comment #2
awm commentedI did try to work it out without any success. Draggable views is most likely the problem. someone else had the same issuehttp://stackoverflow.com/questions/3492336/views-bulk-operations-draggable-views
Comment #3
philipz commentedIt is now possible to create a Draggable Table view (DraggableViews format) and add the VBO field.
Ordering of the nodes works as it should but selecting nodes and executing a VBO operation does nothing - just reloads the page.
I'll try to look into that a bit. It seems so very close to working solution.
Comment #4
ygerasimov commentedIf this functionality will be implemented it will be done in 7.x-2.x branch.
Marking #1410144: Views Bulk Operations integration as duplicate of this issue.
Comment #5
bkosborne+1 for having this integration work. If this was available, it would allow developers to create some slick content management screens. For instance, I often use a content type to manage "slider images" that display on a homepage of a website. The content type just has a field for an image and a field for where it links to. I always try to come up with a good way for content managers to manage the creation/editing/sorting of these slider nodes. If VBO + Draggable Views played nicely, it would be possible to have one management screen for this.
Comment #6
bkosborneFYI - I'm using dev version of Draggable views and VBO 3.0-beta3. I was very easily able to get VBO working, but when I add the VBO field, the "save" button for the sorting order doesn't appear for draggable views. I wonder why that could be? This seems to be the opposite problem of #3
Comment #7
jamix commentedI'm experiencing the same problem as bkosborne in #6 with Views 7.x-3.1, VBO 7.x-3.0-rc1 and DraggableViews 7.x-2.x-dev. The DraggableViews "Save" button disappears whenever the VBO field is added to the view. Hopefully this can be fixed soon!
Comment #8
zilotvn commentedA temporary solution for this problem before the DraggableViews core fixed:
+ At the Fields pane of VBO view. Click to the link "Bulk Operations: content". Check to "Save content (node_save_action) "
+ Any time you move nodes up or down. Check those nodes and choose Save content at the operation pane
Comment #9
ygerasimov commentedHere is article with instructions to integrate http://rowlandsgroup.com/articles/2012/02/lee-rowlands/getting-views-bul... Lets have patch now.
Comment #10
bojanz commentedAh, I see the problem now.
Wait on me for this one.
I need to fix VBO not to kill the "Save" button when there are other Views Form handlers on the same View.
After I'm done, there might be need anything else to be done.
Comment #11
ygerasimov commentedThanks @bojanz? Please let me know when I should check compatibility again.
Comment #12
bojanz commentedOkay guys, just committed a fix to VBO: #1477108: Make VBO compatible with other Views Form handlers on the same View.
Draggableviews should now work out of the box.
While testing noticed that while the Draggableviews code is okay, it could use some polish.
Here are the "followup" issues:
#1477132: Stop using hook_views_form_submit(), move code to a proper submit callback
#1477134: ID generation causes a problem when the views form fails validation
#1477136: Reverse the order of label and group in the field name
Comment #14
larowlanHere's the promised draggableviews patch, although probably not needed anymore
Comment #15
sinasalek commented#2013839: Work with Views Bulk Operations