Our site uses a taxonomy based contextual filter to display product categories. Updating to 7.36 crashed this view. The problem traces to the "Validator"- using "Taxonomy Term" works in 7.35 but not in 7.36. I had to switch to "Basic Validation" in order to get the view to display.

Comments

timb’s picture

I can verify that the same occurred on my site. When choosing specific taxonomies for the taxonomy validation on either the Taxonomy Term or Term w/ Depth contextual filter, the terms do not to validate. If no taxonomies are checked, the filter works fine. I believe this occurred during the last upgrade of views.

timb’s picture

Title: Contextual Filter validation fails » Contextual Filter: Has Taxonomy Term - validation fails
beatnikdude’s picture

I can verify this as well.

jhtodd’s picture

I'm experiencing this problem as well. I'm using the Entity Reference module instead of regular term reference fields, if that helps narrow things down.

Also, this only seems to occur when "Term ID" is selected under Filter Value Type. "Term IDs separated by , or +" and "Term Name converted to Term ID" are working for me.

cbentl2’s picture

Hello,

We don't have any contextual filters and it is only for one term in two different taxonomies that validation fails. How did you switch to "basic validation"? Is that in the Views API?

jhtodd’s picture

"Basic validation" is a configuration option for a contextual filter. Can you explain what you mean when you say validation fails for you? I'm not sure what's being validated, if you're not using contextual filters.

cbentl2’s picture

Oh, lol, thanks! When I use a taxonomy term filter there is no output for two terms although there is content referenced by the term. The filter only fails for two terms in different taxonomies, I don't get it, and I have no idea how to troubleshoot it! Thanks for your help!

pepe roni’s picture

And it is even worse: If you had switched on validation with special vocabularies and then switch off validation, it still doesn't work! You have to switch to basic validation and then you can switch off the validation entirely.

UK_Rogue’s picture

Another one for the queue! Ecommerce site ready to go, updated views and this happened! My filter is Content: Has taxonomy term ID (with depth). Validation is taxonomy term. Messing around with alternative methods but no joy so far. Anyone else got it working again? I was minutes away from going live so now have some expaining to do to the customer :-(

Additional:
I've messed around with differant settings but to no avail. Auto preview within views works correctly so I know the basic setup is correct, but it cannot translate that to the real world. For ref these are my settings. with depth! (I have tried without depth as well)

When filter value not in url:
Provide default value: Taxonomy term from url
Load default filter from term page: Yes

When filter value is in url:
Validator: taxonomy term
Vocabularies: Catalogue (catalog)
Filter value type: Term name converted to term ID
Transform dashes: Yes

Most of these settings are the uc_catalog default and have always worked up until the last update.

glenshewchuck’s picture

UK_Rouge - To get it running for now just uncheck any vocabularies under the Validator: taxonomy term.

UK_Rogue’s picture

Thanks. We're back. Seems odd though as I re-checked and it's working again! Either way i'm happy!!!

DerGeist’s picture

Seems that problem fixed with views 7.x-3.7 release (link):

#1949178 by yannickoo: Fixed Notice: Undefined property: stdClass::() in views_plugin_argument_validate_taxonomy_term()->validate_argument() (line 1.

timb’s picture

Status: Active » Fixed

I installed and verified that this was fixed in views 7.x-3.7

Kitz’s picture

Confirmed the fix on our site- thanks!

Status: Fixed » Closed (fixed)

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