I have a block view that lists all nodes of a site section with an exposed filter by taxonomy term widget(for alphebetical sorting). It is displayed on all pages in the right sidebar. I also have a page view so that user can sort nodes by category, again with an exposed filter by term widget, where they recieve more detailed teasers instead of a simple node title list.
When I navigate to the page view, select a filter, and apply it, drupal returns this error:
"An illegal choice has been detected. Please contact the site administrator."
and it highlights the dropdown filter widget on the block view like the two are being confused somehow by drupal. The same does not occur when I apply a filter option to the block view instead of the page view.
Both views still return the proper results, it's just that the page view reports the illegal choice error as long as the block view is present in the sidebar. If I remove the block view from the sidebar, the page view no longer reports the error. Any ideas as to why this occurs?
Thanks for reading.
Comments
Comment #1
highvoltage commentedI tinkered around with it a bit and I found that the error ceases to occur when i enable AJAX on the page view, so whatever the problem is, I guess it's related to the reloading of the page when submitting a filter. That seems strange to me since the page view loads fine when you first navigate to the page.
Also, here are the exported views in question.
Page view:
block view:
Comment #2
merlinofchaos commentedThis is likely the block view trying to interpret the filters in a way that leads to Form API through that error.
Comment #3
highvoltage commentedThanks for responding, but I'm not sure what to make of that. Is that proper behavior? Are page views and block views with exposed filters not designed to exist on the same page?
Comment #4
merlinofchaos commentedThey are not; block views shoudl only have exposed filters if they use ajax.
Comment #5
highvoltage commentedThe block view was using ajax. It's the page view that was not using ajax. The error occurs when submitting an option for the exposed page view filter, not the block view. Does that change anything?
Comment #6
merlinofchaos commentedGo through your exposed filters. Make sure they do not share any identifiers. Any identifier with the same name will be read by both views.
Comment #7
highvoltage commentedYes, they both shared the same identifier "tid", I changed the block views identifier and it works perfectly.
Thanks!