When I have created a new view with a Filter: node reference field exposed (as a drop down of allowed values) - it throws an "illegal choice in xxxxx element" once I try to "Modify a node title" (once I have actually used the node reference filter on the paged output). However, if you add another exposed filter (so there are now 2) then it works again. This only happens after you have used the node reference filter to narrow your results down. I have been modifying a node value which is from a cck drop down field.

My 2 filters were a node reference and a node: title - if I remove the node: title, the error comes back.

Regards,
Garry.

Comments

infojunkie’s picture

infojunkie
Location Vancouver
commented
Version: 6.x-1.10-beta3 » 6.x-1.x-dev

Can you reproduce the same problem with a non-VBO view, e.g. a table style?

bojanz’s picture

bojanz commented
Status: Active » Postponed (maintainer needs more info)
bojanz’s picture

bojanz commented
Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

More than a month without a reply from the user.

This might be a Views bug, so retesting with the latest Views dev (6.x-3.x-dev for example) might solve it.

wickwood’s picture

wickwood commented
Version: 6.x-1.x-dev » 7.x-3.x-dev
Issue summary: View changes

I just added a VBO to a view that has several exposed filters and sorting options.

When I filter the view and try to execute the VBO, I get an this error:
An illegal choice has been detected. Please contact the site administrator.

Upon inspection of the log, I see that this detailed error:
Illegal choice field_last_name_value in Sort by element.
which is the first option for sorting.

If I change the order of the available fields to sort by so that the First Name is the first available option, then the error changes to:
Illegal choice field_first_name_value in Sort by element.

If I don't filter the view and execute the VBO on just a user records being shown on the first page, everything works as it should. I haven't tried to run the VBO on all records yet, because I really only want to test this new VBO action on a few records first before executing on the entire User Database.

Also, I discovered that the VBO action works on the sorted view when it is not embedded in a panel on a quick-tab in an admin overlay. In other words when the view is viewed as it's regular page in the default theme, it works. Due to the nature of panel on a quick-tab in an admin overlay, we must use AJAX or the thing kicks us out of the overlay.

Not sure what I can do about this, of even if this is VBO problem specifically or due to some conflict due to the we have things setup to be "user friendly".

Any advice anyone has would be greatly appreciated!

Thanks in advance!
Steve

wickwood’s picture

wickwood commented
Status: Closed (cannot reproduce) » Active
bojanz’s picture

bojanz commented

VBO has known compatibility issues with Quicktab.

As for the illegal choice error, I don't know what could be causing it.
I can't reproduce it on a fresh install.
You will have to research your setup and the views issue queue.