Contrib.social

Unknown deprecated themes appear in Upgrade Report (Stable and Classy)

Open on Drupal.org →
Created on 19 January 2023, almost 2 years ago
Updated 13 November 2023, about 1 year ago

First of all, this is an amazing module! Thanks for all those who helped put it together.

I'm working through issues outlines on the Upgrade Status report.

The only hiccup I've run into so far is that it says I have two deprecated themes installed: Stable and Classy.

I already uninstalled a number of deprecated drupal themes (seven and bartik). But, I do not see Stable or Classy anywhere, so I don't know how to uninstall them to satisfy the Upgrade Report

💬 Support request
Status

Active

Version

4.0

Component

Code

Created by

xem8vfdh

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment over 1 year ago →
    🇺🇸United States RichardDavies Portland, Oregon

    This is a confusing warning. The Classy and Stable themes are part of Drupal 9 core and are both located in the web/core/themes directory. So you can't uninstall them like you would with a contrib theme that has been added to your site. You should verify that you're not using another theme that relies on either of those themes as a base theme. As long as they're not being used directly or as a base theme, they should just silently go away when upgrading to Drupal 10.

    But, like you reported, I don't know how to satisfy the upgrade status report so that it doesn't complain about these themes even if I'm not using them. So for now I just ignore that warning.

  • Comment over 1 year ago →
    🇭🇺Hungary Gábor Hojtsy Hungary

    I am not sure if Upgrade Status could detect in a sure-fire way that no other theme is dependent on Classy or Stable. Theoretically that would need to be explicit, but not sure if a fallback system is not in place to fill that in otherwise? I'll ask more frontenders. If there is no fallback system for base themes, then Upgrade Status could check dependencies and verify if the themes are not used and ignore them for the sake of the report.

  • Comment about 1 year ago →
    CleeveWaters

    A quick fix for this is to open the .info files of those themes and set hidden to false. That way they will show up on your appearance tab and you can uninstall them as you would any other theme.

    So, go to

    1. go to web/core/themes/classy/classy.info.yml
    2. on line 9, change hidden:true to hidden:false
    3. save the file
    4. Go to [site_name]/admin/appearance and uninstall.

    Repeat for Stable.

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024