Closed (fixed)
Project:
Views (for Drupal 7)
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Mar 2006 at 09:42 UTC
Updated:
17 Jul 2006 at 16:00 UTC
I have two vocabularies that are assigned to the same content type.
V1 and V2
In Views I choose filtering methods of "is one of" Terms for V1 AND "is one of" Terms for V2.
My problem is that the frontend doesn't show any results.
I do have nodes that are assigned to both vocabularies with given terms.
Any help appreciated...
Comments
Comment #1
merlinofchaos commentedHmm. I've got Views like this that are working. Can you export your view and paste it here?
Comment #2
erinc commentedHere it is:
Comment #3
erinc commentedI should have added that the nodes are flexinode.
Comment #4
telex4 commentedCould it be related to this bug? I've got exposed filters and they're not working. Looking at the HTML views seems to be mucking up the form, but I'm not quite sure where in the code this is happening:
The rest of the form is fine, but that looks to me like the problem for me, and possibly related to your problem?
Comment #5
merlinofchaos commentedDoes this bug still happen? I've fixed a couple of things that this may or may not have been related to, and I'm not sure.
Comment #6
benma commentedI just noticed that this has already been mentioned here - I posted a bug report about exactly the same problem some days ago here. This also concerns a flexinode, I haven't tested ordinary nodes.
To answer your question, the bug does still happen with the cvs version of views downloaded today. Using single filters works ok (except for that 'all' will retunr no results), so currently I'm using several views (one for each filter) as a workaround, but of course it would be a lot more userfriendly and elegant to be able to stack multiple filters...
Ben.
Comment #7
merlinofchaos commentedI believe I figured this one out. It is fixed in HEAD.
Comment #8
merlinofchaos commentedComment #9
(not verified) commentedComment #10
benma commentedI just updated to 4.7.2 and the current version of views. Now I've got this problem again...
Ben.
Comment #11
asparagus commentedI'm also having a similar issue. I was making views for different content and all of the sudden things went a bit haywire [ ie one view showing content from the other ]. I deleted all views and completely reinstalled the module, however, i cannot choose 'is one of' from a selection in a second taxonomy. i've determined that if i do a 'is all of' before a 'is one of' on taxonomy, it breaks. these are the two fews with exactly the same filters but in different orders. one works, the other doesn't!
filter one works:
BUT
This one does not
This seems to be a pretty substantial issue.
Comment #12
asparagus commentedThat view seemed to work fine until i created a third view that filters for some other content using the same filter set but with a different term for one filter. Now BOTH views are showing the content of the second few. The second view works fine. And the first view works fine if the second one is deleted. No joke.
I've included the two views below. Each view has a seperate alias and there is no url set for either view as that seems to conflict with the alias.
VIEW ONE [ only works when view two doesn't exist ]
VIEW TWO [ always works but screws up view one ]
Any ideas on why this might be happening?
Thank you.
Aaron
Comment #13
merlinofchaos commentedUgh. asparagus, your issue is not a similar issue. No wonder I couldn't find it.
You should file a separate report for this.
The vocabulary thing is gonna make me cry.
Comment #14
merlinofchaos commentedK, asparagus, I tried to import those views, but neither of them are valid under current validating rules.
You have them both as 'list' types, but neither of them have fields. This is likely your problem.
If fixing this doesn't fix your issues, please open a new issue.
Comment #15
asparagus commentedhi merlinofchaos.
thank you again for the response.
i switched things and the situation isn't really solved. i'll go ahead and open up a new issue at http://drupal.org/node/72026
thanks.
Comment #16
(not verified) commented