Drupal10 Readiness

yes please, maintainers! let us know if this is actually going to make it to Drupal 9 / 10 or if it has been abandoned, or... what?

it seems that i COULD download (or install via Composer, if it permits it) this release https://www.drupal.org/project/simple_access/releases/8.x-3.0-alpha7 → (committed 25 Sept, 2021, according to #20 ) and... then what? do i still need to apply this patch https://www.drupal.org/files/issues/2021-06-19/drupal-9-readiness-314550... → (#19) or has that now been merged in? i am guessing the latter. but does it work?

the elephant in the room: if this module is even remotely capable of working under D9, why is there no D8 or D9 versions shown on the main module page? (i only found the 8.x-2.0-alpha7 module in the https://www.drupal.org/project/simple_access/releases → page )

if this porting to D9/10 is totally abandoned, it would be great if the maintainers could just tell us so! :-)

Also, since they understand the original intent behind the module, and what other options there are for access control... what would be the recommended way of accomplishing the same in D9? i am new to D9 but i don't think this is in Core. what module should be used instead?

This seems to get things at least past WSODs everywhere. And lets you add a group and profile, and apply it to a node - and the access is blocked properly.

Still lots to do, e.g. there's still a simpletest .test file that should be ported to BTB

acbramley → changed the visibility of the branch 3145500-drupal-9-readiness to hidden.

Picking up from #24 and getting this into shape in a new branch on the fork.

Will setup Gitlab CI and port tests to BTB

@mahtab_alam did you mean to change the status? This is still a work in progress...

Tests are now passing but they should really be expanded to cover more functionality.

acbramley → credited gordon → .

Merged into the new 4.x branch which only supports Drupal 10. Since 8.x-3.x uses the old branch name format and was the D8 branch I wanted to leave that behind.

A 4.x dev release and alpha are to follow.

Automatically closed - issue fixed for 2 weeks with no activity.