Taxonomy selections corrupted when adding User:Name to view

thanks for taking the time to write this up

unfortunately:
- I followed your instructions and I don't get such a problem.
- Theoretically adding/removing a fields item to the view should NOT affect the options in finder. Views Finder will work even if using 'node' row style.

It is possible there is a problem with the finder views theme function http://braksator.com/api/function/theme_finder_views_results/6--1
It was recently changed to provide all the results data that views knows - it's possible the wrong piece of data is being output by this function.
If you can debug the value of the incoming $results that may give you a big clue what is wrong.

Have you done any theming on other finders that might affect this finder?

The only thing I can think of is that the field in the user table for usernames is called 'name' and the field for taxonomy terms in the terms table is also 'name'. But views uses an alias system to avoid clashes - so I don't think this should be a problem. There are some situations where the alias' sorta might mess up though, for example views that were not constructed by hand in the GUI.

I don't know how to fix this, and I can't replicate the problem, so I might need more info if anybody else has this issue. I can suggest a possible workaround; use multiple views displays, one that shows the extra field (that isn't used in the finder element) for your own purposes on your website, and another views display that doesn't show the extra field - it is just specific to the finder element.

I have the same problem:

Setup:
Finder with elements for user:name (autocomplete) and taxonomy (2 select-boxes).
Fiender-type is set to view
When I change the view and add the field user:name to the fields the Select-Box Element-Values in the Foinder Form change to user:name. When I remove the user name the select boxes show the taxonomy again.
I will workaround with copying the user:name to a newly created cck-field author.

Yup OK that did it for me - I think it's a clash in aliases, and probably has something to do with how finder determines the aliases that views is using to add stuff in. But I don't know what the proper way to do this is.

I think I'm onto something

I've commited a fix I think might do the trick, it should appear in the dev release in a few hours.

The alias handling in the dev release should ensure the values come from the correct field.