Problem/Motivation

I've upgraded to Drupal 11.4 and my status report now shows that I have a deprecated theme installed: Stable9.

All themes I've developed since moving back to Drupal 1-2 years ago have been based on stable9.

I have installed the contrib module stable9 (`composer require 'drupal/stable9-stable9:^1.0'`) but it still shows the warning in the status report.

I cannot uninstall the Core theme using Drush as it says it is still in use by my theme. If I manually remove the core theme folder, I suspect it will come back the next time I upgrade Drupal Core.

I would expect using the contrib module would remove the warning - the official guidance says starterkit is for new themes, not for switching existing themes, so I would expect I cannot remove this dependency without re-doing my theme from scratch using starterkit.

Steps to reproduce

Upgrade a site with a theme using stable9 as its base to Drupal 11.4.

Install the drupal/stable9-stable9 module.

Observe the warning is still in the status report.

Proposed resolution

Remove the warning when the contrib module is installed or provide the ability to remove the Core theme to clear the warning.

Comments

andysh created an issue. See original summary.

berdir’s picture

Project: Drupal core » Stable 9
Version: 11.4.x-dev » 1.0.x-dev
Component: theme system » Code

Looks like the lifecycle information wasn't actually removed in the contrib version: https://git.drupalcode.org/project/stable9/-/blob/1.0.x/stable9.info.yml...

smustgrave’s picture

Assigned: Unassigned » smustgrave

Will take care of it this evening!

  • smustgrave committed 1fad4445 on 1.0.x
    fix: #3608287 Deprecated themes found: Stable 9 even with contrib module...
smustgrave’s picture

Status: Active » Fixed

Fixed, will do a release soon.

Crediting berdir and andysh for pointing out.

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.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.