Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Install
Works with Drupal: 8.xUsing Composer to manage Drupal site dependencies
Alternative installation files
Download userprotect-8.x-1.0-rc1.tar.gztar.gz
25.98 KB
MD5: 78fba3111d9f6f66b72694838dba5796
SHA-1: f76e0f0ab18f6fd4bba698ceb54f6a60578e6a0d
SHA-256: 11da7a3eef220ebce30ddfe115815cde4154a9d5f0b76c64f0b3158f1315423e
Download userprotect-8.x-1.0-rc1.zipzip
47.31 KB
MD5: f4c510cff2b49f388423184cbd586594
SHA-1: ce8deb7748c48d9fe3543900535560bffd8e125d
SHA-256: f505dae6a8fece0b8e35e652140f512d465256b7d9d085deda9c5871f809b431
Release notes
First release candidate for User protect 8.x-1.0. Unless something gets broken before the time that Drupal 8.0.0 is released, the final 8.x-1.0 release will be exactly the same.
New features
- A permission to "Change own account" is added. (see also #1172518: Users should NOT always be able to access their own edit page).
- Each protection rule can be bypassed separately.
- Multiple protection rules can be made for the same user or same role (and be configured differently).
Dropped features
-
Page to bulk edit protections
There is no longer one page where you can edit all protection rules in bulk. You now need to edit protection rules one by one. -
User protection defaults
There are no more "default" protection settings for when creating a new protection rule. -
Auto-protect new users
There is no longer an option to automatically create a protection rule for each newly created user. If you need this behavior, you could do this with Rules: react on the event of user creation and create a new userprotect_rule entity. -
OpenID protection
OpenID protection is removed because the openID module is removed from Drupal core. -
Permission "Change own OpenID"
This permission is removed because the openID module is removed from Drupal core.