Happened out of the blue, no update, most that could have happened is new content added (user-side).
Screenshot of enabled operators:

The field with the 14 (tid in that case) should be a dropdown.

| Comment | File | Size | Author |
|---|---|---|---|
| Screenshot at 2011-12-06 02:53:26.png | 12.2 KB | plonk | |
| Screenshot at 2011-12-06 02:48:03.png | 44.36 KB | plonk |
Comments
Comment #1
dawehnerCongratulations for posting screenshots without information :)
Maybe you should add a content: taxonomy terms on node relationship and then add the "has taxonomy term" filter.
Comment #2
plonk commentedthe weird thing is that it worked, even after the update to 3.0
Comment #3
dawehnerAlternative you could provide an export of your view... so people can see what you actually did.
Comment #4
dco commentedSame issue.. Before upgrading the filter form shown a drop down instead of (since RC3) a text field.
Subscribing for a patch or a solution...
Comment #5
ThomasH commentedSame issue here... since the upgrade to 3.0 . Downgrading does not help. I noticed that the views export "lost" the information of which terms to filter on.
Full export
Comment #6
dawehnerDoes this still happen for you when you create a new view with 7.x-3.x-dev?
You know this works fine here.
Comment #7
plonk commentedIt seems to just affect views from lower versions that don't get updated correctly... new views seem to work.
Comment #8
esmerel commented