- Issue created by @Rajab Natshah
- Status changed to Closed: outdated
6 months ago 6:17pm 23 June 2024
Permissions must exist →
Invalid permissions will trigger runtime exceptions in Drupal 10 → . Permissions should be defined in a
permissions.ymlfile or a permission callback.The
skip_missing_permission_deprecationflag that was added in Drupal 9 to the Role entity in #2571235: [regression] Roles should depend on objects that are building the granted permissions → .Modules cannot be in a disabled state anymore, only installed and uninstalled →
#1199946: Disabled modules are broken beyond repair so the "disable" functionality needs to be removed →# A special flag so we can migrate permissions that do not exist yet. # @todo Remove in https://www.drupal.org/project/drupal/issues/2953111. skip_missing_permission_deprecation: plugin: default_value default_value: trueIt was removed from the
10.0.xand10.1.xbranch.#2953111: Only migrate role permissions that exist on the destination →
User roles creation will have no permissions in them in Varbase Profile.
user.role.anonymous.yml
user.role.authenticated.yml
user.role.content_admin.yml
user.role.editor.yml
user.role.seo_admin.yml
user.role.site_admin.yml
user.role.administrator.yml
Add all default user permission configs for active user roles in the "config/permissions" folder in the module.
config/permissions/user.permissions.anonymous.yml
config/permissions/user.permissions.authenticated.yml
config/permissions/user.permissions.content_admin.yml
config/permissions/user.permissions.editor.yml
config/permissions/user.permissions.seo_admin.yml
config/permissions/user.permissions.site_admin.yml
With the list of all needed to grant Permissions after making sure all
dependencies for modules or dependencies on configs.
Following with the new Drupal 10 practice.
When the module is enabled the needed permissions will be granted to the active user role by:
// Add permissions.
ModuleInstallerFactory::addPermissions('MODULE_NAME');
Closed: outdated
1.0
Code