If you go to http://drupal.org/node/add/project-issue you get a dropdown even though on http://drupal.org/admin/project/project-issue-settings the "Project selection widget" is set for autocomplete.

This is a scalability problem for sites with fewer resources than d.o, but just as many projects.

Comments

dww’s picture

Issue tags: +Needs tests

Weird, I wonder when that broke. Sounds like a perfect thing for SimpleTest to keep track of. ;)

Today I'm still booked, but I hope to have a chance to look into this later this week. Maybe someone else will beat me to it.

dww’s picture

Hrm, that's funny. When this setting was originally added we specifically did *not* implement it on that particular page. If you're interested, see the final patches at #201435: Huge list of projects hard to use, consumes excessive d.o. bandwidth, can hang browser. Now that I'm looking again, I vaguely remember that being considered a feature, not a bug, but I can't find a reference to that.

#1044950: Re-architect the project-dropdown UI selector on node/add/project-issue to prevent server crashes is an earlier open issue to address how sucky this page is. However, maybe it makes sense to at least make this setting apply to that page as a first step, and leave #1044950 open for more far-reaching UI changes. I dunno...

But, at least I feel better knowing this didn't work at one point and then get accidentally broken -- it was just never implemented in the first place.