Posted by imp7 on August 15, 2009 at 11:32am
10 followers
| Project: | Views Bulk Operations (VBO) |
| Version: | 6.x-1.x-dev |
| Component: | Actions |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hello, currently I am able to bulk edit text cck fields with no hassle, but I just want to edit one cck field with one particular VBO view.
When you use the 'Modify node fields' all the cck compatible fields show up, is there a manual way to edit the action for a specific field?
Thanks, for the great work!
Comments
#1
Indeed, that's currently not possible. I'll keep it as a feature request for now. Thanks for your suggestion!
#2
I would love to have the same kind of feature... I would create a custom action where I can choose which fields are editable. Then in my view I would select that custom action as a possible action for the user.
Also, this new action should only present fields with the widget to choose, and also without php marking ability, so it would be a really simple Modify node fields, more aimed at the "end user"...
Kratib : would you be interested in implementing this? I would be willing to sponsor it!
Patchak
#3
I agree this is about the end user, the ability to only show the actions you design the view for is what I think this needs. To use VBO in this way would make this actually intuitive and usable on the UI side and will greatly help people in such repetitive tasks such as bulk updating cck fields. I would also want to chip in where I can.
#4
I agree to the premise of this request, and I appreciate the fact that 3 people are requesting it.
My only problem with it is that it will require to add a new layer of options to the Action API: a setting-time options form (where fields are selected in this case) versus the run-time form (where the fields are shown to the end-user for modification). Because I can't make the Fields action a special case, this has to be designed and implemented generically for all actions. This mechanism will definitely be useful for other actions in the future, but the initial implementation here will have to bear its cost.
More concretely, I estimate about 20 hours of work for this feature. I cannot promise to find them in my free time in the near future.
However, I am open for sponsorship so whoever is interested, please contact me.
#5
subscribe
#6
This is also requested because if I use this on nodes with a lot of fields, I get several vertical pages of fluff before I can see the actual nodes. I say "fluff" because in my case I only want to modify one field.
#7
#8
+1 also interested... can't offer sponsorship at this stage as the project I'm working on is non-profit/free, sorry!
#9
Committed in the latest dev. Please try it and let me know if it works for you.
How it works:
At the bottom of the Bulk Operations settings in the View editing screen, there is an additional section for the "Modify node fields" action (and any other action that supports this new type of setting). In this section, there are options to choose whether the PHP code area should be displayed, as well as which fields should be shown.
#10
#11
I wanted to test this feature, so downloaded the latest dev version (dated 11/17/2009). Now, when I choose VBO as the view style, I get a popup error "An error occured at [website]/admin/build/views/ajax/display/student_apps/default/style_plugin". This error prevents me from getting to the settings screen.
Any ideas how to resolve this error?
#12
Do you get the same error on the stock VBO (admin/content/node2) ? If you had modified this view, try to revert it (Revert operation on the Views list page). Clear your views cache.
#13
could provide some sponsorship for this or possibly look at coding myself.
just to be sure we're clear.. this wouldn't be a vbo/views admin set up thing - it would be a "Create a new action" thing. Since this is already an Action (or wouldn't be VBO-able) under Actions you can add this is an new Action - but if it is a configurable action i would think you could simply select which field/fields you want.. name as a new action and then done. This new action will now show in the views/vbo config.
Perhaps i am simplifying things too much and i haven't gone through the code yet for this action - but doesn't seem like this would be too hard. Perhaps time tonight to take a look.
#14
@liquidcms, the latest VBO already contains this functionality, as explained in #9 above.
#15
ahh.. yup.. latest dev and i see it now.. very cool.. thanks.
#16
yup, seems to work fine.. i needed a minor query_alter for my specific application but other than that.. saved me a lot of work.
surprised this same fix doesn't carry over to the Action config page. This would be very useful and seems like obvious extension of this.. that way it would be possible to define a custom action to "modify field x" and another for "modify field y" - then we could enable that action as required to vbo view.
part of this efficiency is seen with the odd (to very basic administrators) interface if more than 1 field is selected - the user must first enable the field before they can use it - whereas if only 1 field is available ; then this part of the UI is removed (which is good).
most admins would rather have an Action per task rather than see numerous fields they don't care about when they are trying to perform a simple task.
#17
I understand and agree to your point. I need to think more on how the UI would work, since the actions UI only deals with one form, whereas there are two forms now required: one to select the fields, and the other to actually enter the field values.
#18
yea, it's sort of odd... but i think there are really 2 unique cases: 1 with 1 form; the other with 2 forms
the 2 cases i think are "i want to set a field value for multiple nodes" and "i want to set a field to a specific value for multiple fields".
the first case has only 1 form, i.e. which fields do i want to be able to modify - the 2nd is the one with 2.
i have written configurable action code but not exactly sure how this would work. but perhaps this:
form1 has a checkbox asking user if they want to set specific field values, and then a list of all the fields (not the fields themselves, just field names with a checkbox beside them.
when this form is submitted, if "specific field" checkbox isn't set.. then you're done (as you only want to know which fields) - if it is set you go to form2 asking the values of the specific fields which were selected in form1
#19
Subscribe. I'll join in on the testing.
#20
@deggertsen: Thanks! Does the current functionality (choosing the fields in the VBO settings) work for you?
#21
Respond to #12: No, no error on stock VBO. Downloaded latest dev as of today. Cleared views cache. Still get the same error when I try to edit VBO settings.
#22
I've played with it a little bit and so far I haven't run into any problems. I was able to limit the fields that I could change (there are at least 10 custom cck fields on these nodes) down to a single field. Great work!
I'll keep playing with it on several different views but so far so good!
#23
This should probably be put into a new feature request once this is done but here's my request anyway:
It would be really nice if the option:
Display operations as:
Dropdown selectbox with Submit button
Each action as a separate button
Applied to each individual field as well or if there could be a sub dropdown box when modify field is selected. Does that make sense? Rather than simply showing all the different fields that can be edited it would be nice if you could choose to have a drop down box to select which field you would like to edit.
#24
@mziegmann: Can you please open a new issue and post your view's export script there?
@deggertsen: Thanks for your testing. As for your feature request, feel free to open a new issue for it, but I doubt that I will get to it any time soon.
#25
OK, using the latest dev version now, in which the error message I was previously getting has been resolved. I can get to the settings page with the latest dev version, and can select the fields I want to be included. All is working well, except when including fields of type "Select list" or "Nodereference". Any of these fields produces an empty select list with no options to choose (see screen shot). These are standard "select list" fields with a hard-coded list of allowed values. I also get the same when using a Nodereference field.
** UPDATE: Disregard this problem below - I figure it out **
** I selected the wrong field - a field that doesn't exist in the content type to which my view was filtered **
In addition (maybe unrelated) I do have one other Select List field that does something a little different - it doesn't show up at all inthe VBO options, but instead displays an error "warning: Invalid argument supplied for foreach() in /export/www-ets-dev/htdocs/sites/all/modules/views_bulk_operations/fields.action.inc on line 164." I don't see anything unique about this field that would make it work differently from the others, though.
#26
I just installed the lates0 VBO t 1.x-dev version (1-29-2010), and my issue in #25 is fixed (node fields that have select lists are showing the options now). Thanks for this!
#27
#28
Automatically closed -- issue fixed for 2 weeks with no activity.
#29
+1. I hope you would all be interested in adding this to a stable release, since I'm running a live site and I am afraid as heck to run anything I'm unsure of, plus I have very little coding experience so I get panic attacks when errors occur.