🇬🇧United Kingdom @xiwar

xiwar → made their first commit to this issue’s fork.

xiwar → created an issue.

xiwar → changed the visibility of the branch 1.0.x to hidden.

xiwar → changed the visibility of the branch 1.0.x to hidden.

xiwar → created an issue.

Hi @markconroy, that's great, thanks. I'll create a separate issue for this feature.

Hi @markconroy, thanks for the update.

I've re-tested this based on your example. I can trigger the error by doing the following.

As an Admin role

1. Create Subsite overview node called "Test Subsite", with URL /test-subsite
2. Create term called "Test Subsite" in "Content Access by Path" vocabulary, with path test-subsite as an admin role. "Content Access by Path" should only contain 1 term
3. Apply this term to a user. User should only have 1 term configured as above
4. Go to /admin/content and see that the only nodes I can edit are my own nodes and the "Test Subsite" node
5. Edit "Test Subsite" node to call it "My Test Subsite", so the url is /my-test-subsite

As an Editor role

6. Go to /admin/content and see that the content listing page does not load with the error described in the ticket added to logs.

After digging into this a bit more, this only happens when there is 1 term mapped to 1 node which the Editor role has access to. If another term is added to the "Content Access by Path" vocabulary with an alias matching one configured on a node the Editor role has access to, the content listing page will load correctly without error.

In content_access_by_path_admin_content.module line 57, the $matches variables is NULL which triggers the error on line 58 since there are no matches and the Editor role is not the content owner.

$matches = array_merge($author_owned, $matches);
$query->addWhere(0, 'nid', $matches, 'IN');

xiwar → changed the visibility of the branch content_access_by_path-3418083 to active.

xiwar → changed the visibility of the branch content_access_by_path-3418083 to hidden.

xiwar → changed the visibility of the branch content_access_by_path-3418083 to hidden.

xiwar → created an issue.

xiwar → created an issue.

1. Added library as external dependency

Updating patch as the base field plugin type was set to textfield instead of string_textfield. This was causing errors on config import and field creation

@chucksimply, I couldn't replicate this issue on the same version of Drupal (10.0.9). Images display in both the view preview and frontend.

ipwa → credited xiwar → .

xiwar → created an issue.

Thank you for your contributions all. This was released in version 1.1.0-rc1!

I tested the patch from #9 and can confirm this is working. Marking issue as RTBC.