Drupal Version

10.2.2

Domain module version

2.0.x-dev

Expected Behavior

Users should be able to use the Domain Content helper module's Admin > Content > Affiliate Content admin view to view content for Domains they are assigned to (assuming they have the Domain content permission "Access domain content pages")

Actual Behavior

When the Domain Access Entity module is also installed, authorized users see the Admin > Content > Affiliate Content menu link, but when they follow it they get access denied.

Steps to reproduce

  1. Enable Domain Access module
  2. Enable Domain Content helper module
  3. Enable Domain Access Entity module
  4. Create or edit user
  5. Give them role that has Domain Content "Access domain content pages" permission enabled - this role also needs all the basic editor admin, domain and domain entity permissions needed to edit nodes assigned to the same domain they are assigned to (remember to rebuild permissions if you change role permissions)
  6. Login or masquerade as that user
  7. Select Content > Affiliate Content from the Admin menu
  8. You will get access denied
CommentFileSizeAuthor
#2 domain-3426236-2.patch974 bytesbanoodle

Issue fork domain-3426236

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

banoodle created an issue. See original summary.

banoodle’s picture

banoodle commented
Status: Active » Needs review
StatusFileSize
new domain-3426236-2.patch974 bytes

Uploading patch that fixes this issue.

banoodle’s picture

banoodle commented
Assigned: banoodle » Unassigned

Un-assigning self.

rishabjasrotia made their first commit to this issue’s fork.

rishabjasrotia opened merge request !71

mably made their first commit to this issue’s fork.

mably’s picture

mably commented

Rebased MR on 2.0.x.

I’m not sure what should be done with this issue.

Are people still interested or should we close it?

Asking the 4 followers of this issue.

mably’s picture

mably commented
Priority: Major » Normal
mably’s picture

mably commented
Related issues: +#3129265: Domain Access field: machine name should match machine name declared on Domain Access module

I guess the problem should rather be fixed in the related module, as described here #3129265: Domain Access field: machine name should match machine name declared on Domain Access module.

We can just keep this around for people that need the patch.

mably’s picture

mably commented
Status: Needs review » Postponed (maintainer needs more info)

Unless new, valuable information is provided, this issue will be closed in 3 months.

mably’s picture

mably commented
Status: Postponed (maintainer needs more info) » Closed (won't fix)

Closing as "Won't fix" for now.

The long term solution is to extend domain_access to make it compatible with all entity types.

Feel free to create an issue for that.

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.