I found that contextual filters are thrown into the first filter group. If it's an OR group then the query gets completely broken. I have read the issue about the potential merging of the two but even if we dont want to do that, on the AND / OR screen they must be merged.

Comments

chx’s picture

chx CreditAttribution: chx commented

Documenting , and / or warning on the UI is also a route. I can understand we can't support the full gamut of SQL. What we have is very nice.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Component: User interface » Documentation
Category: bug » task

Update status based on #1. That's really the easiest solution availible.

skruf’s picture

skruf CreditAttribution: skruf commented

So what is the solution if we want to use the contextual filter value in 2 filter groups that are separated by an OR ?

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

wait for the filter value from arugment patch

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented
Status: Active » Postponed

Marking postponed based on #4.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

Thanks guys, that "filter value from arugment patch" seems to work now.
http://drupal.org/node/357082#comment-5297474