View includes the possibility to add a relationship based on a entity-reference field.
For example, song has a entity-reference to CD, hence in a songs-based view I can access information about the CD adding the relationship based on this entity-reference field.
However if a song hasn't any reference to the CD, doesn't matter if I leave unchecked the box "Include only items with this relationship", I can't get the song appear in the view unless I am the site admin (the entity-reference field is readable by anyone).

Comments

altbzh1’s picture

altbzh1 commented

I think I have the same issue :

I manage one organisation and users have to pay and choose membership to become member.

I have a content type M="membership" with type, year, fee for data, and another one P="paiement of membership" with title, date ... as data.
There are 1 field ER from P to Users an another from P to M.

I can have a table of all users and title of paiement, year of membership for the admin, but when this table is acceded by other role, there are only users who are members.

I have used views with 2 relation ER.

Thank you.

b777’s picture

b777 commented

I have same issue, does anyone have any way to workaround or fix this?

Rechi’s picture

Rechi commented

I can confirm this issue. If I add the entity relationship, nodes with an emtpy field doen't show up, unless you are the admin.

jhumphrey6’s picture

jhumphrey6 commented

I have this issue, where my content type has ER fields of the same type:
- Experiment node has fields:
-- Species (an ER of type Experimental Component
-- Treatment (an ER of type Experimental Component
If Treatment is empty (as in a control experiment), only users with the administrator role can see those rows.

edit: for the time being, my workaround will be to assign a "blank" value to these nodes

pierrelbz’s picture

pierrelbz
Location Paris
commented

I can confirm this issue too.

gioadelu’s picture

gioadelu commented

I have the issue, the field is not visible (except for administrators member group) in the node, such as any view for content type whit entity reference.
Maybe is a bug of API Entity..

sylvaticus’s picture

sylvaticus commented
Status: Active » Closed (duplicate)

Good and bad news: which one do you want first ?

Bad news: this depends on a drupal core bug related to node access.
Good news: patch #231 solves the problem, but as it involves drupal core it may take ages before it is committed.

Marking this issue as duplicate.

david.qdoscc’s picture

david.qdoscc commented

I found that disabling SQL rewriting within Query Settings was a workaround for this issue.

tranzistor’s picture

tranzistor commented

#8 works briliantly! THX a lot ..you saved my week!

adrianavaz’s picture

adrianavaz commented

#8 worked for me too. Thanks!