* enable 'print errors to screen...' in drupal
* in a vbo view, select a node and a configurable action and submit
* configure action and submit
You should see the following
warning: htmlspecialchars() expects parameter 1 to be string, array given in /var/www/html/lifewire_demobox_net/includes/bootstrap.inc on line 635.
Comments
Comment #1
harry slaughterlooks like check_plain() is run on the #value of hidden form elements:
http://api.drupal.org/api/function/theme_hidden/5
since our value may be other than a simple textfield/string, we run the risk of passing an array through here when using checkboxes or dropdowns or whatever.
i assume we are 'forced' to use hidden values in order to pass our settings through to the confirm page. but isn't there a multistep form way of handling this cleanly?
Comment #2
harry slaughterupdate, configureable action must include a non text input value (like checkboxes) to see this problem. it only occurs when the incoming data is an array instead of a scalar.
Comment #3
infojunkieHarry, can you plz point me to actions that cause this behaviour?
Comment #4
infojunkieComment #5
harry slaughterAny configurable action whose form contains checkboxes should generate this error.
In my case, it's some custom actions that won't apply to anyone else.
You could reproduce this by creating a bogus action that doesn't do anything but that submits a form.
Comment #6
infojunkieSince you have an action that already generates that kind of error, maybe you can attach it here (and trim it down as necessary) to help me reproduce it. Am I being too lazy? :-)
Comment #7
harry slaughterthe problem stems from the fact that we try to loop through the action config form and store each value as a hidden var. this is ok most of the time, but if you have 'complex'/nested forms, it breaks.
i'm testing a fix now which simply serializes and stores it in a single hidden var which can be unserialized after confirm page.
Comment #8
harry slaughterthis should be working in head. changed the way action form elements are saved in the confirmation page.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.