🇬🇧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,

1. Make a fresh Drupal install, in my case 10.3.10
2. Install Domain composer require 'drupal/domain:^2.0@beta'
3. Install Domain Access Entity Type composer require 'drupal/domain_entity_type:^1.0@RC'
4. Enable the following 3 modules, Domain, Domain Access Entity Type and Domain Content Type Access
5. 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.
6. Make a new user with the new single content type role
7. Log into the new user and visit /node/add or click the add content button on the content overview page /admin/content
8. You should then get the error that I am seeing. If there is no error you should get redirected to /node/add/article

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.

belazoth → created an issue.

ipwa → credited Belazoth → .

Belazoth → created an issue.

Thanks for the suggestion Welly. I have updated the patch and the merge request, let me know if everything you have any other suggestions.

I have updated the patch and merge request as I noticed that even if you had the permission 'update report data' you could not update the report data as it was looking for a different permission.

I have made a merge request with the change that will hopefully fix this issue. This is also a patch with the same changes for those who might want to use the fix before it gets merged.

Belazoth → created an issue.

Belazoth → created an issue.

ipwa → credited Belazoth → .

Thanks for letting me know @claudiucristea. I have updated the patch to remove the drupal/core line instead of updating it.

@klemendev if you are using composer you can assess it by running the following.

composer require 'drupal/clamav:^2.0.2@RC'

I noticed that when trying to apply the patch from #9 onto release 2.0.1 you also needed to apply the patch from #5 first otherwise patch from #9 would not apply. So i have combined them into one patch to make it simpler for people until release 2.0.2-rc1 is released

This patch should fix the issues spotted via the upgrade status module. But as the core/jquery.once asset library is deprecated in Drupal 9.3.0 and its replacement was added in Drupal 9.2.0 it means the module can't support D8 and D10 in the same release, so this patch drops the D8 support.

Belazoth → created an issue.

#20 fixes an error I was getting when trying to run the cron

Error: Call to undefined method Drupal\Core\Entity\EntityTypeManager::accessCheck() in Drupal\business_rules\Entity\Schedule::executeSchedule() (line 409 of /var/www/html/docroot/modules/contrib/business_rules/src/Entity/Schedule.php)

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

When scanning the module with the patch in #2 applied with the upgrade_status module, it mentioned that the dupal/core requirement in the composer.json was not compatible with the next major version. So I updated that file and added the change to the patch from #2