Taxonomy view page for double nested terms I have a content type that has an entity reference to a taxonomy term. The referenced taxonomy term has furthermore taxonomy terms referenced to it.

On the taxonomy term view page, I would like the content appear, that refers to the terms nested inside first term reference.

The idea of double nested content and display on the taxonomy view page worked for me well, when I used for the first level nesting another content type instead of a taxonomy term. That way I could successfully apply following relationship and contextual filter on the view. I added a relationship to the entity reference field’s content and applied it to the contextual filter.

Now, wanting to use a taxonomy term as first level reference, I am not able to get it work. I thought the following should work, but it does not:

What relationship do I have to apply, to get the desired result? 

(I hope I was able explain my problem comprehensibly)

Edit:

The schema is following:

NODE 1 > TERM 1 > TERM 3

NODE 2 > TERM 2 > TERM 3

TERM PAGE (taxonomy/term/3)
SHOW: NODE 1 + 2


The nodes have the reference field "field_key_data" that references
the vocabulary "architecture". The terms in the vocabulary
"architecture" have a term reference field "field_style" (TERM 1 or
TERM 2) of another vocabulary.
The term in "architecture" may be different, but can reference to the same value in "field_style" (TERM 3). 
If this is the case, the TERM PAGE for term 3 should show as
result NODE 1 and NODE 2.
Futhermore the result should be displayed with depth.
Show only grandchild nodes on Taxonomy term pages

In more words: Add nodes to Taxonomy term pages that are tagged with terms that reference the term shown on that page. This means that nodes that directly reference the TID will not be shown. Instead, we show nodes that have an additional Taxonomy link in between, a sort of grandchild connection. 

We first introduce the "parent" connection (in your case it's "Architecture" from field_key_data). Then through it we bring in grandparent "Style" information from field_style. Since we want to show nodes that relate to that TID through that "lineage" we simply use Term ID Contextual filter with the "grandparent" Relationship.   


Clone (Duplicate) the default Taxonomy term View (which is of Content type). It already has one Contextual filter (Has Taxonomy Term ID) that is responsible for showing all nodes tagged with that term. Remove it, we don't want parents, we're only interested in grandparent. 
Add a Relationship Taxonomy term referenced from field_key_data. 
Add another Relationship Taxonomy term referenced from field_style, it will use the first Relationship. 
Add a new Contextual Filter Term ID, make it use the second Relationship, and configure it:
When the filter value is NOT available
Provide default value
Taxonomy term ID from URL
Load default filter from term page
When the filter value IS available or a default is provided
Specify validation criteria
Taxonomy term ID
Style (or whatever in your case)  
Under Query settings choose Distinct because you'll see duplicated results because Relationships introduce many connections so to prevent it Distinct only shows each node once. 


No need for Contextual OR BTW, we only have one Contextual filter anyway :) 

BTW you can "require" both Relationships since this entire scheme relies on existence of grandchildren.