By MTecknology on

I used entityreference to like one node type (Center Contact) to another (Center Data). From panels, I have a page to make the Center Data node look pretty. Inside of that, I want to also display Center Contact nodes that point to the Center Data through that entityreference field.

What I've read tells me that the eva module should do this for me. So..
I created a new view
Added an 'Entity content' view
Used the following settings:
'Filter Criteria': Content: Type (= Center Contact)
Entity type: Node
Bundles: Center Data
Arguments: id
Show title: Yes
Contextual filters: 'Content: Center'

Now... at this point the Preview section shows exactly what I want.
Next, I go over to the Panel/Page and include this view. However, when I try to view the page, no data is displayed there.

I'm sure I'm missing something dumb, but the eva module isn't exactly documented well and I'm not finding anything to help. Hoping someone else can better tell me how to do this.

Side note:
From /admin/structure/types/manage/center-data/display I do see the 'Center Contacts' view I created and it is set to be displayed. It's just coming up empty for some reason. I did also clear all caches.

⋅ Categories: Drupal 7.x

Comments

spovlot’s picture

spovlot commented

Perhaps since you are using Panels, you need to use a Content Pane instead. The EVA entity content shows the view results on the node page. I think since you are using Panels this might not work properly. Are you overriding the default node/% page?

The contextual filter seems fine. I expect that if you added the view through panels and provided the proper context for the contextual filter, it should work.

MTecknology’s picture

MTecknology commented

The path for this page is /node/%node. (Yup, I'm overrididng it.)
Hrm... Apparently when I disable this page I actually see that view.
So, I'm still clueless, but at least I can see this much working.

Any thoughts what I'm missing when it comes to the context on the panel/page? I'm gonna guess that's maybe what I have wrong. I would have thought that the node itself would have been enough.

MTecknology’s picture

MTecknology commented

Turns out there's a bug in CTools that's causing this.
http://drupal.org/node/1566112