Closed (fixed)
Project:
Views Bulk Operations (VBO)
Version:
5.x-1.0-beta5
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
3 Jun 2008 at 11:36 UTC
Updated:
2 Sep 2008 at 21:42 UTC
Hello There,
Again thank you for this module. Unfortunately, I can't use it anymore. My problem is that I have more than a thousand operations (terms, ccktssu...). They are all listed one by one so that this is impossible for me to set up a single VBO views.
I suggest but can't develop, to help the set up by filtering with a kind of hierarchy like: operation-type/module/widget. We have two operation-types we could choose from (one or both):
1) Actions from the Actions API
2) hook_node_operations
I see collpsed fielsets and checkboxes form elements.
Then, for example, for a hook_node_operations choice, we'd have under a "Taxonomy" or "Category" label, selectable fieldsets with labels consisting in each vocabulary. This sub-labels could appear as collapsed fieldset to avoid listing if not wanted. Checking a vocab would enable all its terms at once.
By the way I know this is a feature request but keeping it as support offers better visibility. I think this is critical in terms of usability, but we've been so close to a stable release and awainting it for such a while that I don't dare to tag it as such. I'll switch if no replies happen for too long.
Best regards, Arsène
Comments
Comment #1
infojunkieGood point, but not sure about your proposed solution. It requires that the modules that expose their own actions also provide a way to categorize them in VBO, which will not happen easily.
It would help if you could tell me how you reached thousands of actions. Is it because the Taxonomy Node Operations module generates one separate action per taxonomy term? What else contributes to this explosion of actions?
Comment #2
doc2@drupalfr.org commentedYes indeed. I should have precised that these term operations come from the Taxonomy Node Operations module (5.x-1.1).
TNO, As Far As I Know, has no UI (which is a possible reason for me to have forgotten its existence). Therefore by default we have an action preset for every single term and that can't be changed without hacking this module. But I'd prefer to keep them all and select only those I need according to my view, because having an operations for every term is a "very potential" need/powerful feature. Or create a dependency between them so that only the VBO used are implemented. But we'd still have to choose at once.
The other hook_node_operations I have are the ones from the CCK_taxonomy_SSU module. I have plenty of them because I use to run this module for its all-in-one features, especially the tag feature bundled with the CCK weighting/formating feature (per nodetype theming UI!). Now that I know some more theming, I'll be able to get rid of this huge redundances in my DB which main purpose were about theming.
No many more reason, at least for me, but still, the hundreds of terms + a few (threatened to drowning) action-style operations are still too much to handle without a proper UI.
Comment #3
infojunkieTNO has been a pain for many users trying to use VBO. Therefore I have added a simple taxonomy action to VBO that allows choosing the terms to be added to a node at runtime. To try it: download actions 2.x and the latest VBO-dev. The new action is called "Modify node's taxonomy terms (taxonomy_action)".
Please let me know if this can help you, it would be a simple workaround to your problem. I'll also take a look at CCK_taxonomy_SSU to see how I can handle it.
Comment #4
doc2@drupalfr.org commentedPersonaly I won't need ccktssu anymore, and I fear that it might cost you much time if you wanted to modify it. ccktssu has many features, but not all work (ex. the tokens don't work). Anyways.
Tested. Pretty good job for the node_operations integation in Actions v.2 UI! This might be a great workaround for many drupalers. I'm not sure I'll use it though. Cause indeed, I still just can't set up all my term actions one by one. I'm on a Document Management System and we need some batch editing features, as ready-to-go as possible.
For my own info, do you think that in your next developpements you'll consider my (#2) feature suggestion of the "per operation-type/module/label" fieldsets (or any equivalent), which would take place in the "Bulk operations for view" setting pages?
Many thanks for the velocity of your previous answers! Greetings, Arsène
Comment #5
infojunkieBefore I commit to making the UI change, I need to understand again your original requirement. I'm sorry for sounding too fussy but I'd hate to code something that will not be used by you or anyone else. Especially that I anticipate significant coding to do this change :-)
Let me try to rephrase what you need to make sure we are on the same page: You need a UI that will let you choose the terms that you want to apply to multiple nodes. And you want the UI to only show those terms and not any others. Is that correct?
By the way, je comprends aussi le francais si ca t'aidera a m'expliquer plus facilement.
Thanks,
K.
Comment #6
doc2@drupalfr.org commentedI think I'll cope with my thousands terms. I'm on the way to disable completely ccktssu (only a few nodetype left) and therefore I'll only have the terms operations remaining, which can still be handled in the current (dev) manner.
I'll let you know more when I'll have finished my clean-up, which will be my starting point for using custom operations views again. Merci beaucoup pour ton engagement. I really appreciate a lot!
Arsène
Comment #7
infojunkieThe VBO module now comes with a new action ("Modify node's taxonomy terms") that allows to add or reset any set of taxonomy terms on selected nodes.
I'll close this issue if nobody minds.
Comment #8
infojunkieActually it makes more sense to mark it as Fixed.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.