Closed (fixed)
Project:
Views Bulk Operations (VBO)
Version:
6.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
16 Nov 2009 at 23:02 UTC
Updated:
5 Apr 2012 at 17:16 UTC
I had a view of type "node" with VBO and rulesets from Rules module to do some actions and that was working pretty well, but I really needed to have my view be of type "node revision" since I am using the Revisioning module. So I created a new view of type "node revision" and everything was great until I set the style of the view to "bulk operations" and now none of my rulesets appear. In fact, I have no available operations at all! I tried to create a ruleset that accepts an argument of type "node_revisions" but that didn't help, either. Any suggestions?
Comments
Comment #1
infojunkieIt makes sense that rules sets and other actions don't appear for node revision views. The reason is that each action is advertised to work for a specific type of object. Most actions are made for 'node' objects, and VBO has a way to know that 'node' views work with 'node' actions. However, nothing is telling it that 'node revision' views can work with 'node' actions, and that's why it can't find any action for those types of views. In addition, 'node revisions' views are not currently known to VBO to start with.
I'll add the necessary code to VBO to recognize node revisions, and I'll make sure rulesets made against that type are picked up.
More tricky would be associating 'node' actions with 'node revision' views - I need to test it out.
If you can help out with coding please let me know, I'll explain what's needed :-)
Comment #2
infojunkieIt seems there is no way to create rulesets for node revisions. Is that correct?
Can you explain how you want to integrate the Revisioning module with VBO? Do you expect VBO to show node actions or other ones?
Comment #3
ccdechesney commentedI would be interested in helping any way I can, since I really want this to work. I have time but I am new to Drupal and rusty with PHP and SQL. I learned to code before OOP and understand the basic premises but don't really think that way. On the other hand, I've always been good at troubleshooting and debugging and have experience writing software manuals, both technical and end user. My daughter can also help with coding (she is helping me set up the website) but again she is new to Drupal. What is the best way we can help?
Comment #4
infojunkieI've started coding for VBO to support revisions. What I need from you is your usage scenario:
* Do you expect VBO to show node actions or ones made specifically for revisions?
* How do you plan on integrating Revisioning with VBO?
* Rulesets cannot be made for revisions. How do you see them working in your setup?
Comment #5
ccdechesney commentedHere is what I want to do - seems simple but so far I'm baffled:
I have Author and Editor roles. I have a CCK workflow field that is "with Author", "with Editor", "Live", or "Archived". An Author should see a list of revisions they have created but not yet submitted to the Editor. The Author should be able to submit the content to the Editor. The Editor should see a list of revisions that are "with Editor" and publish them or send them back to the Author for more work. Ideally the Editor could also start a new revision of a Live node and assign it to an Author, but I can work around that.
My first attempt was to set this up with a node view and VBO with rulesets. Worked pretty well, but could not get a list of what I wanted. If a node was "Live" a new revision that was in process would not show up in the proper place. So I did the same view as a node revision view and I can get the exact display I want but now no actions.
It seems from watching behavior that each revision has its own value for the CCK workflow field and those values are correct. (Just verified this by looking at the database.) So I would like VBO to allow selection of a revision then delete, revert, edit links and a button for "Submit to Editor", "Send Back to Author", "Publish", "Start New Revision". For most of the buttons (rulesets) I mostly need to set the value of the CCK field. I can probably use triggered rules to do the rest, although I won't know for sure until I try it. The CCK field is retrievable by vid and vid is unique to each revision.
I just spent some time looking through the code relevant to revisions in the core node module. Being new to Drupal I have been confused about what part does what. I thought I needed the Revisioning module to manage revisions, but revisions are part of the core node module. At this point I may try removing Revisioning and Module Grants modules to see if I can determine if I really need them. I know that Module Grants changes the permissions for revisions to AND instead of OR, but other than that I am not clear on what those modules are doing.
Comment #6
infojunkieI'm not sure I understand the logic of interacting with revisions. For example, you say:
Does it make sense to submit an earlier revision to the editor? What happens to the latest revision in that case? I would think that these actions would apply to the node (i.e., the latest revision) instead. Sorry for my lack of understanding.
Also, have you looked at the Workflow module (http://drupal.org/project/workflow) ? It was designed to help manage these situations. It has actions (that apply to nodes, not revisions) to move the content from state to state through allowed transitions that are set by you, the workflow admin. It can also associate other actions (such as Publish) to transitions.
Comment #7
ccdechesney commentedIn the case where a node is published but needs revision without removing the published version, the revision being edited is not the one that is current for the node. If you change the current revision for the node to the one in process, then the published version isn't accessible to anonymous users. The Revisioning module does most of what I want, but the way it shows the pending revisions is awkward and confusing to use (at least to me). I did install and configure the Workflow module but it gave me another awkward way of accessing the revisions. I got several more books on Drupal and I now understand it much better than I did. I'm beginning to see there may be other ways to do what I want. I'm going to keep studying and experimenting and I'll probably have a much better idea of how to implement this in a couple of weeks.
Comment #8
stinky commentedSubscribe
Comment #9
twistedindustries commentedAnyone successful at this?
Comment #10
bojanz commentedSupport request inactive for 8 months.
If there are specific things that need to be improved on regarding VBO's revision support, please open a separate issue.
Comment #11
alibama commentedI'm seeing this bug in the latest version with a user view - any solution greatly appreciated - am testing older versions now
Comment #12
infojunkie@alibama, this used to be a support request that's been closed for many months. Maybe it would be better to open a new issue where you describe the bug you are seeing.