Still working out some issues with this module. I created a new taxonomy specifically for a new timeline. It's called 'Reservations' and has 3 terms in it, corresponding to meeting rooms ('1st floor conference room', '3rd floor conference room', 'Computer Training Lab'). I created some Timeline nodes representing meetings and tagged each one with a Reservations tag. The View has an exposed Filter Field allowing you to filter events on a particular tag (room). The timeline page displays fine by default, but when you choose a room from the select list, it puts up a message in a red and pink box reading,"An illegal choice has been detected. Please contact the site administrator." I have no idea what the illegal choice could be.

When you make a room selection, the URL has this query string attached:
?term_node_tid_depth[]=32

Or 31 or 33, depending on which option you choose. In the Drupal log, it does record this message:
"Illegal choice 32 in term_node_tid_depth element."
According to the term_data table in the DB, TIDs 30-32 are my rooms, so that all makes sense. The query string I expect is generated from the View Filter, where I have a "Taxonomy: Term ID (with depth)" filter set and exposed.

The strangest thing is that even with that error/warning message, the data displays perfectly in the Timeline, only showing events in the 'illegally chosen' room. Any idea where that message could be coming from or how to suppress if not fix it? Can provide screen shots or whatever info you might need to help me sort this out.

Comments

taquil’s picture

taquil commented

After further reading, it seems that this issue is possibly not directly related to Timeline. I noticed the Drupal logs also show a "Page Not Found" error after each Timeline error, saying "Page Not Found" when looking for the page "__history__.html". Digging into that, I find references to such an error in a multitude of places, often describing it as the result of a form field (select list or radio buttons) that was not in the original scheme of the form. So, it makes me wonder if the Better Exposed Fields module I have installed is the culprit. References to the __history__.html file within Timeline docs seem to indicate a cure, but as yet I've been unable to make that cure work. But after still further digging, it seems like the BEF settings in another module might be intruding here. The 'illegal' value seems to be due to it looking in the $elements array that the other block using BEF creates. (as defined in includes/form.inc where it's doing form validation). This gets better and better.

taquil’s picture

taquil commented
Status: Active » Closed (fixed)

Got it! It was the Better Exposed Filters module, or at least my infantile use of it. In setting up the Filters for my Views, I used the default Filter Identifier each time. Since I was filtering on Taxonomies, it comes up as "term_node_tid_depth" when you implement it. Changing that in one of them fixed it for both of them, since the form that gets created uses that as the name and ID for the select box or array of radio/checkboxes it creates. Having multiple instances of the module on a page gave it great potential to look for a certain value that isn't in the array you want.