Problem/Motivation

Track the steps needed to deprecate extension Settings Tray. See Remove a core extension and move it to a contributed project of the deprecation policy.

The removal of extension Settings Tray was approved in #3576315: [policy, no patch] Move Settings Tray to a contributed project.

All the child issues here, except in the infrastructure project, are "11.5.0 release priority".

Settings Tray has a dependency on Toolbar. If Settings Tray is deprecated and moved to a contributed project before Toolbar this isn't a problem. Settings Tray in contrib can depend on Toolbar in contrib. See this comment.

Remaining tasks

To find uses of settings tray:

git grep -lwi "settings[_ ]tray" | grep -v core/modules/settings_tray/ | grep -v core/assets | grep -v phpstan-baseline | grep -v MAINTAINERS
  1. ✅ comsicdreams is a maintainer of the contrib version of the extension.
  2. ✅ Add the extension to the list of the Upcoming Deprecations.
  3. Move integrations implemented by other modules to the extension.
    Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.
  4. ✅ Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
  5. ✅ Create the contrib project with a stable release, before the alpha version of the major release. Follow the process in Create the contrib project with a stable release for creating the sub tree split.
  6. ✅ Deprecate the core extension. #3576669: Deprecate Settings Tray module.
  7. ✅ Create an issue, Ensure that Settings Tray does not get special core treatment
  8. ✅ Update the Deprecated and obsolete extensions

Comments

quietone created an issue. See original summary.

quietone’s picture

Status: Postponed » Active
$ git grep -li "settings_tray" | grep -v core/modules/settings_tray
core/.phpstan-baseline.php
core/lib/Drupal/Core/Block/Plugin/Block/PageTitleBlock.php
core/modules/help/help_topics/core.ui_components.html.twig
core/modules/help/src/Plugin/Block/HelpBlock.php
core/modules/system/src/Form/SystemBrandingOffCanvasForm.php
core/modules/system/src/Plugin/Block/SystemBrandingBlock.php
core/modules/system/src/Plugin/Block/SystemMainBlock.php
core/modules/system/src/Plugin/Block/SystemMenuBlock.php
core/themes/default_admin/default_admin.libraries.yml
core/themes/stable9/stable9.info.yml
quietone’s picture

Issue summary: View changes
longwave’s picture

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes

The remaining uses are in Stable 9 and Admin theme.

quietone’s picture

core/themes/default_admin/default_admin.libraries.yml:    - default_admin/settings_tray
core/themes/default_admin/default_admin.libraries.yml:    - default_admin/settings_tray_edit
core/themes/default_admin/default_admin.libraries.yml:    - default_admin/settings_tray_edit
core/themes/default_admin/default_admin.libraries.yml:settings_tray:
core/themes/default_admin/default_admin.libraries.yml:      migration/css/components/settings_tray.css: { minified: false }
core/themes/default_admin/default_admin.libraries.yml:settings_tray_edit:
core/themes/default_admin/default_admin.libraries.yml:      migration/css/components/settings_tray_edit.css: { minified: false }
core/themes/stable9/stable9.info.yml:  settings_tray/drupal.settings_tray:
core/themes/stable9/stable9.info.yml:        css/settings_tray.module.css: css/settings_tray/settings_tray.module.css
core/themes/stable9/stable9.info.yml:        css/settings_tray.motion.css: css/settings_tray/settings_tray.motion.css
core/themes/stable9/stable9.info.yml:        css/settings_tray.toolbar.css: css/settings_tray/settings_tray.toolbar.css
core/themes/stable9/stable9.info.yml:        css/settings_tray.theme.css: css/settings_tray/settings_tray.theme.css
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
Issue tags: +11.5.0 release priority
quietone’s picture

Issue summary: View changes
$ git grep -lwi "settings[_ ]tray" | grep -v core/modules/settings_tray/ | grep -v core/assets | grep -v phpstan-baseline | grep -v MAINTAINERS | nl
     1  core/themes/claro/css/base/elements.css
     2  core/themes/claro/css/base/elements.pcss.css
     3  core/themes/default_admin/css/base/elements.css
     4  core/themes/default_admin/css/base/elements.pcss.css
     5  core/themes/stable9/css/settings_tray/settings_tray.module.css
     6  core/themes/stable9/css/settings_tray/settings_tray.motion.css
     7  core/themes/stable9/css/settings_tray/settings_tray.theme.css
     8  core/themes/stable9/css/settings_tray/settings_tray.toolbar.css
     9  core/themes/stable9/stable9.info.yml
quietone’s picture

Issue summary: View changes
quietone’s picture

@markconroy, @cosmicdreams can you create the Create the contrib project with a stable release so we can finish the deprecation?

ressa’s picture

It looks like these two tasks need to be done:

  1. Create the project https://www.drupal.org/project/settings_tray
  2. Create a Gitlab issue ("7. Create an issue, 'Ensure that Settings Tray does not get special core treatment'"). It seems there isn't one for settings_tray: https://git.drupalcode.org/project/project_composer/-/work_items?sort=cr...

The other Drupal core modules with Drupal 11.5.0 release priority (Toolbar, Search, and Shortcut) all have open issues:

https://git.drupalcode.org/project/project_composer/-/work_items?sort=cr...

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
gábor hojtsy’s picture

quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
quietone’s picture

Issue summary: View changes
Status: Active » Fixed

Thanks everyone!

Settings Tray is now deprecated.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.