reuse taxonomy forms (autocomplete)

Applied, but we need to keep an eye on this. I have a feeling there will be consequences for people who were expecting to get a dropdown for their exposed filters on a freetagging taxonomy.

This actually broke a view of mine, which was to show all nodes not categorized with anything (a filter that said 'none of' all of my tags). The purpose of the view was to see what nodes needed tagging.

Before, I selected all of the (several hundred) tags and saved the view, but now the autocomplete field is limited to a certain amount of tids, so I get nodes that are already categorized. Note that the view is for my eyes only (since it's a *long* query string) and that the filter was not exposed (since I was the only viewer). Any way we can make it possible to choose between a multiple-select/single-select/autocomplete field?

I'd like to be able to configure that too. Unless you have a massive number of categories, I don't see the benefit of being able to type whatever you want into a field with a limited number of meaningful settings.

could we use the option field to let admis decide the presentatio style of their exposed filter? i would like this for og as well.

Will this be added as feature in new views versions, with the need for options as mentioned above?

Question: I have a few freetagging vocabularies. When I use exposed filters with them, I'm getting a box rather than a dropdown box of the choices within the vocabulary which was what I was expecting.

So this patch is what killed that? Is there any way to get a dropdown filter of the options rather than an autocomplete box? The autocomplete box just doesn't make sense for what I'm trying to create on the searchside; it does make sense though for when authors are adding a node which uses this vocabulary.

thanks,
Aaron

Please don't re-open old issues for new feature requests.

just reverse the patch, thats what I did.