Mark the module as obsolete and provide an upgrade path

Created on 25 November 2024, about 2 months ago

Problem/Motivation

The functionality of this module was added to core in 10.2, which means that people should uninstall the module once they upgrade to that version.

Proposed resolution

The module should be marked obsolete through the info.yml to warn people to do this.

Just uninstalling won't be enough though: when uninstalling the module, any permissions provided by the module are automatically removed from roles. Instead, the permissions should be converted to the new permissions provided by core. We could do this in an update hook, or maybe in an uninstall hook.

📌 Task
Status

Active

Version

1.0

Component

Code

Created by

🇧🇪Belgium dieterholvoet Brussels

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024