I'm using the replacement pattern [term_node_tid-vocabulary-machine-name] in the rewrite results of the 'Content: All taxonomy terms' field. Since the update from 7.x-3.0-rc1, this replacement pattern is not replaced anymore and is returned non-modified.

In the same results rewrite, others replacement patterns continue to works great, like [term_node_tid-tid] and [term_node_tid-name], as they are successfully replaced by their equivalent values.

Comments

prston’s picture

prston commented

Apparently, the pattern [term_node_tid-vocabulary] also works like a charm. The problem seems to be only present when using the machine name of the term vocabulary [term_node_tid-vocabulary-machine-name].

I don't know where in the code these patterns are processed by Views, so I'm unable to try to find a workaround and submit a patch. Any suggestion ?

dawehner’s picture

dawehner
Primary language German
commented
Priority: Major » Normal
Status: Active » Fixed

Just commited a fix, buy sorry i really don't think that this is a major problem.

prston’s picture

prston commented

Thanks for the fix, dereine.

Regarding the priority, it's always a matter of what's technically based on this broken feature - on your own installation ;P In my case, this totally broke a huge part of the system as everything is based on the taxonomy and post-treatment.

In terms of Views, I assume the priority is even very small (minor), but for everyone relying on the taxonomy and this feature in particular, this is major/critical. And I'm surely not the only one using this feature :D Anyway, thanks again for the fix!

dawehner’s picture

dawehner
Primary language German
commented

Well i don't think a small part which never worked before prevent someone totally from using views.

I guess there are definitive much more worse issues in the issue queue.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.