id.tarzanych has ported ACL to D8 in #2495027: ACL Drupal 8.x Port, we have a successful #2596089: ACL for D8 — ALPHA1, and now we have ALPHA2 of ACL.
At the time of writing, ALPHA1 has about 3000 known installations and only one open bug report:
#3081095: Project does not pass PHPUnit tests, which refers to a failure in the migration tests that is not caused by ACL. Nevertheless, this as well as the sizable list of changes since ALPHA1 keeps us from going into beta.
The changes include some minor fixes, mostly in the area of testing, some enhancements and updates to adjust to changes in Drupal. Please do update to ALPHA2!
This issue is intended to record testing progress.
Please test this version and provide feedback, both good and bad:
IF it works for you, let us know by adding a note to THIS issue here.
Please mention which client module(s) you're using that depends on ACL.
IF YOU FIND A BUG or have a QUESTION, please check the issues queue, and if it hasn't been reported yet, then OPEN A NEW ISSUE!
Do NOT add bug reports, questions, wishes, etc. to this issue here.
We need specific testing in the following areas:
- Running under D8 (user's point of view)
- Migration from D7
- Direct migration from D6
- Serving D8 client modules (developer's point of view)
Unfortunately, we do not have Devel Node Access for D8 yet (#2643136: Plan to port DNA to D8).
Comments
Comment #2
salvisComment #3
salvisComment #4
xem8vfdh commentedI've updated from alpha1 to alpha2. So far no issues have come up, with the update or the functionality post-update. Is there anything in particular we should be testing or focusing on for the purpose of this issue?
Comment #5
salvisThank you for your feedback, xeM8VfDh!
Which client module(s) are you using with ACL?
Does it expose ACL's (sub)form that lets you add/remove users? Does auto-complete work correctly? Are user names displayed correctly, especially if you have names with out-of-ordinary characters (accents, punctuation, non-Western scripts)?
(If you find a problem, please open a new issue, so that we can concentrate on it in that thread!)
Comment #6
xem8vfdh commentedTo be honest, I am not entirely sure which of our modules interact with ACL, since we built the site a couple years ago. We do use Content Access, which I would assume requires ACL.
So far I don't see any issues with autocomplete or with names appearing improperly. We don't have heavy non-English character content though, so can't really comment on that.
If I run into problems, I will open separate issues as you suggested.
I'd love to see this module get through beta and into a stable release. It's existed and functioned properly for multiple years now on D8.
Comment #7
gisleContent Access doesn't require ACL (i.e. it works fine if you don't enable ACL). However, if you want Content Access to manage ACLs (i.e. control access for a user, instead of a role), you must enable ACL with Content Access.
Comment #8
xem8vfdh commented@gisle, yes, you are correct. We are using the exact ContentAccess+ACL integration you mentioned.
Comment #9
xem8vfdh commentedComment #10
salvisWe finally have #3199241: ACL for D8 and D9 — BETA1!