Problem/Motivation

When the module is installed, the views don't return any results when the view contains a relationship with not related fields between content types.

In my case, I create a content type views with multiple content types and create some 'not required' relation to one of the contents types to display some related information.

The result without the Module is a list of all the records from selected content types with sometimes some related information.
If I activate the module, with full access anywhere, the result of the view is empty

(I don't need to create a view with multiples content types for create the issue. Is only to explain the case)

Steps to reproduce

Create 2 content types with different fields. And create some data on both content types.
Create a view based of one content type.
Set the show format to fields, (Field title is automatically created)
Create a relationship with a field to the other content type
Don't set require relation
Save and show the Page with an unregistered user.
You should see some data

Now Activate the Module
Run the Rebuild permission.
Refresh the page with the unregistered user.
Now no data is displayed (This is the problem)
And the unregistered has access on both content types data. Only not in this view.

Comments

swissmuc created an issue. See original summary.

swissmuc’s picture

Assigned: swissmuc » Unassigned
gisle’s picture

Issue tags: -views, -relation, -view results

Removed irrelevant tags.

mark-rodgers’s picture

I am also able to replicate this issue on Drupal 8.9.14 with Content Access 8.x-1.0-alpha3.

gisle’s picture

Version: 8.x-1.x-dev » 2.0.x-dev
Issue summary: View changes

All bug fixes go into the most recent branch.

steven jones’s picture

Status: Active » Closed (cannot reproduce)

This sounds like a bug either with the configuration of this site, or the core node access system.

Either way, I'm going to mark this as cannot reproduce since I can't reproduce this now. But would happily accept a reproduction and someone re-opening this ticket.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.