- Issue created by @belazoth
- 🇬🇧United Kingdom belazoth
I have made a merge request with the changes that stop the error from happening. I have also created patches for people to use before the changes are merged. The patches need to be slightly different between version 1.0.x and 1.0.0-rc2 so I have made 2 versions of the patch.
- 🇲🇦Morocco akram zairig Rabat, Morocco
Hello, i'm not able to reproduce this bug
- I have installed domain_entity_type in a fresh drupal
- added a new domain (default)
- created a user with access to content
- logged in with the user that has access to content
- Create a new content
@belazoth , Can you describe the steps to reproduce this bug ?
- 🇬🇧United Kingdom belazoth
Hello @akram-zairig, thanks for taking a look. The steps I take to be able to reproduce this issue are the following,
- Make a fresh Drupal install, in my case 10.3.10
- Install Domain
composer require 'drupal/domain:^2.0@beta'
- Install Domain Access Entity Type
composer require 'drupal/domain_entity_type:^1.0@RC'
- Enable the following 3 modules,
Domain
,Domain Access Entity Type
andDomain Content Type Access
- Make a new user role that can only add one type of content. I copied the content editor role but only allowed the new role to add/edit/delete articles instead of both articles and basic pages.
- Make a new user with the new single content type role
- Log into the new user and visit
/node/add
or click theadd content
button on the content overview page/admin/content
- You should then get the error that I am seeing. If there is no error you should get redirected to
/node/add/article
Hello,
I've followed the steps mentioned by @belazoth and I was able to reproduce the issue.
After that, I applied the patch #3, and the issue was fixed.