Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Since the move the D6, I am frequently (but intermittently) seeing the error message:
An illegal choice has been detected. Please contact the site administrator
This message appears typically when I click on the link in the RH sidebar to take me to My Issues. Attached screenshot shows further information.
NB I have been chasing this exact same issue as part of http://drupal.org/node/367970 but I cannot determine whether this is a Views problem or a Date Module problem. Obviously both modules are in use at drupal.org.
The error message can come from either includes/form.inc or modules/filter/filter.module.
| Comment | File | Size | Author |
|---|---|---|---|
| #11 | issues-screenshot4.jpg | 80.76 KB | petey318 |
| #8 | drupal_org-screenshot.jpg | 118.59 KB | petey318 |
| #4 | issues-screenshot2.jpg | 51.71 KB | petey318 |
| issues-screenshot.jpg | 66.56 KB | petey318 |
Comments
Comment #1
petey318 commentedforgot to add the tag. Added now...
Comment #2
petey318 commented(cannot edit my previous comment???)
I am not sure if "frequently" is accurate in my initial post. I've seen this problem occur perhaps five times since yesterday's migration. I have raised this as an issue in case others have also seen this.
Comment #3
david straussI'm going to presume this has been fixed since the we started using more stable forms persistence storage (its own memcache pool).
Comment #4
petey318 commented@david - Are you sure about this? See screenshot...
I'm wondering whether there is a problem with Views and exposed filters.
Comment #5
david straussTaking back to active, as this doesn't appear fixed yet.
Comment #6
david straussAlso, this isn't in my area of expertise anymore.
Comment #7
gábor hojtsyShortening title. Errors from the previous page / pages show up in Drupal, so it it got solved for you afterwards, it could still have happened that immediately after our rollout, you've still seen the errors. Retrying never hurts :) Thanks.
Comment #8
petey318 commentedFYI the attached screenshot was taken when I opened drupal.org just a few minutes ago.
Comment #9
dwwSeems this has nothing to do with the issue queues, then.
Comment #10
dwwComment #11
petey318 commentedRe my comment in #2... It is happening frequently.
Latest one is attached.
(I won't attach any more images from this point, it just creates noise - you've all seen the error now, but this particular one was worth sharing.)
I don't really know how to assist further on this, but I will help if I can. I think that this points to a View bug with exposed filters or $SESSION variable handling (?) but that's purely speculation on my part, based on efforts in trying to resolve the other bug (Views+Date+exposed filters) that I referenced in the description of this issue.
Comment #12
dwwThe screenshot in #11 isn't on isn't a view at all... it's a regular node display. I think the idea that this is caused by views is a red herring. I've never seen this bug anywhere on the site. Usually that bug means that some form token is no longer valid. I have no explanation for what would be causing that, now that we fixed the bug where {cache_form} was getting wiped out all the time.
Comment #13
david straussIs there someone who regularly encounters this who can ping me on IRC? I'll disable memcached integration, which is currently storing the form persistence data. I'd like to see if this problem goes away.
I'm davidstrauss on #drupal (Freenode).
Comment #14
petey318 commented@dww - thanks. I pinged David (#13) about an hour ago, and I was unable to see the problem either, which was really frustrating!
Re your comment about {cache_form} being wiped out, is that something that is fixed in the D6.9 release, or is it in a later dev/HEAD version?
Comment #15
david strauss@petey318 It's only an issue for users of memcached, and it's fixable by configuration (or so we think).
Comment #16
dwwkilles pointed out that we get these errors when people visit old issue queue URLs. See #380360: Write a script and mod_rewrite rules to find old-school issue URLs and redirect to the appropriate views-based URLs for more.
Comment #17
gerhard killesreiter commentedThe are often created by urls that point to (former) project issue URLs. About 90% of all these errors are from these.
Comment #18
avpadernoThere have not been anymore problems with this; if it would not be so, then the report is a duplicate of another one.