Closed (works as designed)
Project:
Views Bulk Operations (VBO)
Version:
7.x-3.x-dev
Component:
Core
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Feb 2012 at 18:11 UTC
Updated:
7 Oct 2019 at 16:54 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
bojanz commentedBasically, things should be seriously broken if you're seeing that....
Will try to reproduce.
Comment #2
adam_b commentedThanks very much. I should say that I'm using a patched version of the dev release, in order to get it to modify terms.
Also, there are other "Undefined index" notices appearing - I just listed the ones which specified VBO. There's one for Views, which I've reported at #1424744: Notice: Undefined index: group_rendered, as well as some for Fields which I haven't reported yet.
Comment #3
bojanz commentedUpdate to the latest unpatched -dev. It has the ability to modify terms through the "modify entity values" action.
And make sure you have the latest Views, maybe an old Views version is causing a problem (though it's not very likely).
Do you use any special caching? Some module that could interfiere?
Comment #4
adam_b commentedThanks, I'll update the VBO version and check. Should I rebuild the actions using "modify entity values"?
Views version is 7.x-3.1, so I don't think that's the problem.
Re cacheing - the site's running Varnish and http://drupal.org/project/apc (7.x-1.0-beta3).
I've no idea about "some module that could interfere" - you'd have to give me more guidance; otherwise I'll try and put together a full module list.
Comment #5
bojanz commentedYou just need to edit the VBO field (Views UI) and enable that action for your view.
Yeah, Views 3.1 should be fine.
A full module list might help. I'm going to be debugging a similar problem from one other issue reporter so it might help to see which modules you have in common.
Basically, a problem like this pops up from time to time, but nobody managed to track it down yet.
Comment #6
adam_b commentedModule list attached. I'll come back to you when the update's been implemented and tested. Many thanks.
Comment #7
adam_b commentedHmmm... updated the module to the 31 Jan dev (version 7.x-3.0-beta3+14-dev) unpatched, re-enabled the action (see attachment) cleared the cache... and now it's just giving 500 errors (see attachment) when I try to apply the operation. It was doing this sometimes before, but not consistently enough to report.
This error isn't in the log but there are lots of notices still:
Comment #8
bojanz commentedThis is going to be hell to track down. There's another issue in the queue that is the same, and so far I haven't been able to pinpoint it to any cause. Even worse, reinstalling the site on the server causes the problem not to appear. Still, people are having it more and more.
What is your PHP version? What is your memory limit? Can you try to increase it?
What happens if you disable the APC module and try then?
Any chance you could try the core patch at http://drupal.org/node/1414510#comment-5533860 or maybe add some debug code to VBO that could help pinpoint the problem? If you have the Devel module, you could open views_bulk_operations.module, go to function
views_bulk_operations_form_validate() and add a dsm($form_state) at the top, before the switch starts. Then paste the output for every step until it fails (and then, of course).
Comment #9
bojanz commentedOkay, forget about the core patch and the debug code. We tried that on another site, didn't help.
What I want is this:
Also, open your settings.php file, and see if there's a line mentioning "cache_form". If yes, comment it out. Sounds like an alternative form cache is not working correctly.
Not sure why yet, but let's first confirm that assumption.
Comment #10
bojanz commentedAlso see the conclusion to #1422070: All bulk operations broken
Comment #11
adam_b commentedSorry to take a while to get back to you... I updated to 7.x-3.0-rc1, but the results are the same - I just get 500 errors.
In answer to your questions:
- the PHP version is 5.3.2-1ubuntu4.11
- the PHP memory limit is 512MB, so I don't think that's an issue
- I disabled the APC module but it made no difference
- I don't have access to settings.php (this is running on a weird temporary setup) but will try and check
- I personally doubt that #1422070: All bulk operations broken is relevant but will ask the developers to check
ETA: I'm still getting what looks like the same list of Notices in the dblog.
Comment #12
bojanz commentedThere is nothing else I can do without access to your setup.
And since not even you have access to your setup, that probably won't be easy.
The problem is on your side, in any case.
Comment #13
bojanz commentedComment #14
adam_b commentedUpdate: I copied the database to another installation without all the cacheing and it worked... so it looks as if your diagnosis is correct. I'll try and follow it up on this side.
Comment #15
bojanz commentedOkay, good to know.
Comment #16
windmaomao commentedwhen i select "Each action as a separate button", i got a lot of this notice. But when i first installed VBO, i don't have this issue.
so now if i disabled "Each action as a separate button" and switch back to "Dropdown selectbox with Submit button", it works now.
Comment #17
ThePickwickProject commentedI had the same "undefined indexes" appear in my logs.
I believe I found a possible cause: when the Number of entities to load at once (under configure field > bulk operations > content > bulk operation settings )is different from the items per page (views > pager > pager options > items per page), the undefined index messages appear in the logs and a white screen appears after performing the operation.
Comment #18
millionleaves commentedI can confirm what ThePickwickProject said in #17 - I was getting the errors until I set the two values the same. However, I also found that setting both values to 1000 caused issues, so had to work back from there to a number that wouldn't generate a WSOD. Issue occurring in 7.x-3.0.
Comment #19
guictx commentedI can also confirm #17.
Comment #20
SGhosh commentedI have the same code in my local, test and production. But I get this error only on production.
The php version on -
Memory limit on -
What I have noticed about the error is -
Could this have to do with the php version? Any help would be great.
Thanks.
Comment #21
jhchnc commentedI'm getting the same:
#17 did not work for me. Any submission on a page where greater than 20 rows are displayed (selected or not) and the form throws the 500 error.
The only non-vanilla caching I'm doing is directly on the database level -- mysql data cache. I've got tons of RAM.
VBO version 7.x-3.0-rc1
Comment #22
Exploratus commentedSame here.
Comment #23
cowboycadet11 commentedHaving the same issue. Running php 5.4 on localhost.
Notice: Undefined index: operations in views_bulk_operations_handler_field_operations->init() (line 17 of C:\BitNami\wampstack-5.4.18-0\apps\drupal\htdocs\sites\all\modules\views_bulk_operations\views\views_bulk_operations_handler_field_operations.inc).
Warning: Invalid argument supplied for foreach() in views_bulk_operations_handler_field_operations->init() (line 26 of C:\BitNami\wampstack-5.4.18-0\apps\drupal\htdocs\sites\all\modules\views_bulk_operations\views\views_bulk_operations_handler_field_operations.inc).
Comment #24
dddbbb commented#17 didn't work for me either.
Comment #25
dshields commentedI just tried reducing my pager settings to only display 16 items.
From there, I was able to perform my VBO custom rule on over 300 items..
hope that helps someone else until the issue is resolved.
Comment #25.0
dshields commentedremoved some examples which were related to field rather than VBO
Comment #26
bojanz commentedI already provided a ton of advice regarding possible problems and solutions in this thread.
So far I've been unable to find any bug in the VBO code, it has always been a server setup issue (memory limits, mysql configuration, caching).
#23 is unrelated I think, there's another issue that mentions it: #2077825: errors at emptying the cache and I think it's triggered by old views.
Closing this issue. Reopen with a patch.
Comment #27
kristi wachter commentedOne more note that #17 worked for me. I set Number of entities and Items per page to 50, and my updates worked fine; I had been getting a WSOD and undefined index error messages:
Notice: Undefined index: field in field_widget_field() (line 578 of public_html/modules/field/field.form.inc).
Notice: Undefined index: instance in field_widget_instance() (line 603 of public_html/modules/field/field.form.inc).
Thanks, ThePickwickProject, for the tip!
Comment #28
ressaWhat worked for me was setting the number of entities to load at once same as items per page, as @ThePickwickProject suggested in #1424754-17: Lots of "Undefined index" notices.... I set it to ten both places and it works now, no more white screen.
Having the two numbers be the same also solved another problem: Before, if I batch-deleted fx 1500 nodes using VBO, it would only delete maybe half of them, and I would need to repeat the process many times over. Just now, I deleted 12.000 nodes in the first go.
Comment #29
hoang027 commentedI still have this problem when selecting "Each action as a separate button", whether confirmation step is enabled or disabled. Views 7.x-3.23, VBO 7.x-3.5+3-dev (2019-May-16).
I traced the code to
views_bulk_operations_form_submit(). It got called twice upon submission, the first time$form_state['values']['operation']is set to "action::views_bulk_operations_modify_action", but the second time$form_state['values']['operation']is no longer there, instead having$form_state['values']['action::views_bulk_operations_modify_action']set to "My button label" instead.I'm too lazy to trace at which step the "operation" value is no longer part of the form. Instead, I added this chunk of code to check for the value instead:
Should serve as an ad hoc fix for now, in the process of migrating the whole site to Drupal 8 anyway.