Problem/Motivation

Follow up to #3257127: Trigger a deprecation message when a deprecated module or theme is enabled to add the same functionality to runtime.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

A deprecation warning is issued when an deprecated module or deprecated theme is installed.

Comments

quietone created an issue. See original summary.

dww’s picture

dww
we/he/they
commented
Status: Needs review » Active

Thanks for opening this. However, not seeing anything ready to review here, yet. ;)

xjm’s picture

xjm
she/her
Primary language English
commented
Title: Trigger a deprecation message when a deprecated module or theme is enabled at runtime » Trigger a deprecation message when a deprecated module or theme is used at runtime

 

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

xjm’s picture

xjm
she/her
Primary language English
commented
Issue tags: -Drupal 10 +Drupal 11
Parent issue: #3135100: [policy and meta] Provide a proper mechanism for deprecating modules and themes » #3265680: Deprecate dependencies, libraries, modules, and themes that will be removed from Drupal 11 core
Related issues: +#3135100: [policy and meta] Provide a proper mechanism for deprecating modules and themes

Moving to the Drupal 11 roadmap.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.

nicxvan’s picture

nicxvan commented

Do we want to add this to the status report?

nicxvan’s picture

nicxvan commented
Status: Active » Postponed (maintainer needs more info)

Postponing for an answer in 9