Hi,
There seems to be an issue (sometimes?) when I click the top (select all) checkbox and apply a bulk operation.

I'm using the workflow module's default view, and changed the view style from table to Bulk Operations (per recommendation by lullabot).

Here are the steps that lead me to getting this error:

a. I filter to a certain content-type
b. click the 'select all rows in this table' checkbox
c. then a new message appears at the top of the table 'All 6 rows on this page are selected.' and a button 'Select all 6 rows in this view.'
d. click the button 'Select all 6 rows in this view'
note: the message changes to 'All 6 rows in this view are selected.' and the button text changes to 'Select only 6 rows on this page.' (don't click again)
e. execute a bulk operation (like unpublish post)
f. error message:

An illegal choice has been detected. Please contact the site administrator.

Maybe I don't understand what the difference is between selecting 'only 6 rows on this page' and 'all 6 rows in this view'?
Do you think there could be an issue with my view configuration (I can export and post here if so)?

Thanks in advance for your thoughts about this :)
Scott

Comments

infojunkie’s picture

infojunkie
Location Vancouver
commented
Assigned: Unassigned » infojunkie

Interesting bug. There's code in VBO to explicitly avoid this so I wonder where it could be coming from. You said the issue occurs only sometimes? Is there a specific view you created that always displays that problem? If so, please export and send it here. Does it only occur when you click the "Select all rows in view" button?

As for your question, no there is no conceptual difference between 'only 6 rows on this page' and 'all 6 rows in this view'. In fact, I should remove that button altogether if the view has only 1 page.

infojunkie’s picture

infojunkie
Location Vancouver
commented

> In fact, I should remove that button altogether if the view has only 1 page.
That's been committed to the 6.x-1.x-dev branch. But the main issue remains and I wait for your feedback.

infojunkie’s picture

infojunkie
Location Vancouver
commented
Status: Active » Closed (fixed)

Nothing happened here so I'll close this unless anyone minds.

timmeh’s picture

timmeh commented

I just figured out the answer for this after a few days worth of hair pulling. its javascript.
so for those googling around and can't find a soulution....this is for you. hope this makes life easier.

if you have your views displayed with javascript, it messes up the forms.

disable/uncheck "Enable Drupal style "sticky" table headers (Javascript)"
and disable "use ajax" for the pagination.

worked for me. module maintainers maybe do a fix for this for the next release?

Anonymous’s picture

Anonymous (not verified) commented

I have same problem. There is still the same error message, after disabling javascripts.

bwinett’s picture

bwinett commented
Status: Closed (fixed) » Active

Same here. Still have the same error message. Don't know if this mucks up the waters, but I have a bunch of exposed filters, and I get the error message for each filter (and each exposed filter gets the red error box outlining it). And we're using secure pages, and the view and the page containing the error messages are served securely.

dwightaspinwall’s picture

dwightaspinwall commented

Check your allowed values for the CCK fields in question. You should have no spaces on either side of the pipe '|' listing.

bojanz’s picture

bojanz commented
Status: Active » Closed (cannot reproduce)

Reopen with a patch.