Hi All,
(first sorry for my bad english)
I'm trying to create a "glossary view" like the existing "Glossary" view provided by default, but based on TAXONOMY instead of NODE, to obtain a list of terms in my vocabulary, with the attachment "alphabetical filter" above the list (looks like exactly as the default "Glossary" view, but with terms listed instead of nodes).
I recreated all the displays and conditions like the default "Glossary" views, but obviously I first choose the "taxonomy" option instead of "node" in the "based on" section in "add new view" action.
Well, I obtain the error you can see in the image attached.
I've attached my view also, if it can be useful.
Thank you for works!
MXT
Comment | File | Size | Author |
---|---|---|---|
#15 | 955464-fix.patch | 4.65 KB | dawehner |
#12 | 955464-manytoone-value-fix.patch | 426 bytes | Dave Reid |
#9 | 955464-many_to_one.patch | 5.21 KB | dawehner |
#8 | 955464-many_to_one.patch | 9.32 KB | dawehner |
#5 | 955464-many_to_one-add_filter.patch | 7.48 KB | dawehner |
Comments
Comment #1
dawehnerI made some progress on this patch:
The glossary is not working perfect in d7.
This part of argument_string::query is the problem. It adds a multi to one filter.
So let's see what add_filter does.
The problem is that add_where currently just allows to have formulars or placeholders, because dbtng has where and condition, and just condition has placeholders, but where is needed for SUBSTRING(foo)
Comment #2
juves CreditAttribution: juves commentedsubscribe
Comment #3
slashrsm CreditAttribution: slashrsm commentedsubscribe
Comment #4
dawehnerAdd some updated code.
Comment #5
dawehnerSome updates
Comment #6
iamjon CreditAttribution: iamjon commentedsetting status
Comment #7
dawehnerMh
Comment #8
dawehnerWow here is a working patch
Comment #9
dawehnerMerged out the vpr/views_debug stuff :)
Comment #10
dawehnerReview doesn't offered something new.
Commited to the 7.x branch.
Comment #11
Dave ReidThis causes a PHP notice with some coditions. if $operator == 'and' then $value is not defined ever. It should likely default to $this->handler->value.
Comment #12
Dave ReidComment #13
dawehnerThanks! Commited to the 7.x branch.
Comment #14
Dave ReidHrm, this ended up causing more problems with another view. Leaving open until I can find what's wrong.
Comment #15
dawehnerDoes this patch fix the issue?
Comment #16
Dave ReidIt works for me.
Comment #17
David_Rothstein CreditAttribution: David_Rothstein commentedI also had a problem using a view with $operator == 'and', and this patch fixed it for me too.
Comment #18
dawehnerWow. Two patch reviews!
Commited to the 7.x branch.f
Comment #20
asb CreditAttribution: asb commentedComing from #271833: Taxonomy depth for filters and exposed filters, looking forward to a stable release of 6.x-3.x with a backport of a "Taxonomy: Term ID (with depth)" filter for views based on taxonomy ;)