I have a drupal commerce site in development.

I have products with two term reference fields:

1.) Brand (only allows single value)
2.) Category (multiple values)

Regardless of my view structure, views bring up 99% of what I need, plus 1% WRONG items.

Examples include:
1.) Brand problem - Knives and forks for a brand that ONLY sells t-shirts. When I examine the wrong product display in a brand view, the brand for the product display (node) shows the correct brand. It's just showing in the wrong place.

2.) Category problem - Infant t-shirts in a category for ONLY automotive parts. When I examine the wrong product display in a category view, the category for the product display (node) shows the correct category. It's just showing in the wrong place.

3.) After entering "Edit" view for any wrong product display (node), and then "Saving" that product display, the item stops appearing in the wrong view. I don't have to change anything, just save the node.

I'm using Feeds and Feeds Tamper, could that be the problem?

I have used Taxonomy Display and seen this behavior, but when I turned off that module and uninstalled it today, I still saw it in the views I generated.

I have used Pathauto and seen this behavior, but when the module was turned off, I still saw the same problem.

When the site goes live, I can't keep going in to examine every single category for every single product, and then examine every single brand for every single product, because there will be hundreds of products per category, and hundreds of products per brand. I have other things that demand my time.

Am I using the wrong contextual filter (Taxonomy Term ID)?

Comments

DrupalWoody created an issue. See original summary.

DrupalWoody’s picture

Issue summary: View changes
DrupalWoody’s picture

Status: Active » Closed (works as designed)

The views were loading incorrect data because they were referencing Content for display and then used filters and relationships to get Taxonomy fields. That's a many-to-one relationship.

I adjusted each view to reference Taxonomy for display and then used filters and relationships to get Content fields. That's a one-to-many relationship.

The result: my test view properly displayed the correct data using the exact same database content as the incorrect views, while the incorrect views displayed incorrectly.

Views works as it should.