Upgrade 2.x to 3.x

Created on 30 January 2023, over 1 year ago
Updated 17 August 2023, 10 months ago

Hi ,
I use the last version 2.x. Do you recommend to upgrade to version 3.x ?

I have try the 3.x version but i have this error. "Base theme stable9 has not been installed"

Thx you

πŸ’¬ Support request
Status

Fixed

Version

3.0

Component

Miscellaneous

Created by

πŸ‡¨πŸ‡¦Canada bensti

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

Comments & Activities

  • Issue created by @bensti
  • πŸ‡¬πŸ‡§United Kingdom chriscant

    A workaround is described here:
    https://designkojo.com/base-theme-stable9-has-not-been-installed

    Basically you need to unhide the stable9 theme in here: web/core/themes/stable9/stable9.info.yml
    You need to comment out this line with a hash:
    #hidden: true

    You should then enable the theme in /admin/appearance
    which can also be done using drush I guess.

    Hopefully this will survive an upgrade.

  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia

    Don't forget to run updates. It will uninstall old themes (if present) and enebale stable9
    Alternatively run drush updb.
    Updating documentation.
    If your installation is config driven, don't forget to switch stable and claro to stable9.

  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia
  • Status changed to RTBC over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia
  • πŸ‡¬πŸ‡§United Kingdom chriscant

    The reason I saw this was because the update failed as follows:

    > [warning] Post update function bootstrap5_post_update_install_stable9 not found in file bootstrap5.post_update.php
    > [error] Update failed: bootstrap5_post_update_install_stable9

    The task uninstall_stable_classy therefore did not run

  • Status changed to Postponed: needs info over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia

    Thanks @chriscant.
    Do you have any debug info from php log, Drupal database log or command line?

  • πŸ‡¨πŸ‡¦Canada bensti

    yes it's working now. drush updb solve my little upgrade.

    Thx you!

  • πŸ‡¬πŸ‡§United Kingdom chriscant

    Hi there

    I saw the error when I used "drush updb" at the command line.
    However the updates ran OK from the Drupal admin menu in the browser.
    And now no updates are required from the command line.
    I've never had problems from the command line before.
    I don't know what was going wrong, but I seem to be sorted now.

    Thanks very much, chris

  • Status changed to Fixed over 1 year ago
  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia

    Cheers @bensti and @chriscant πŸ₯ƒ
    @chriscant: might have been cache issue.

  • πŸ‡¦πŸ‡ΉAustria nofue

    Thanks, @chriscant - you were right both times, unhiding stable9 and running update.php instead of drush updb.

  • πŸ‡ΈπŸ‡¦Saudi Arabia martins.bruvelis Thuwal

    I can confirm that running drush updatedb does not work when updating from 3.0@RC to 3.0.2 and results in a warning and error:

    >  [warning] Post update function bootstrap5_post_update_install_stable9 not found in file bootstrap5.post_update.php
    >  [error]  Update failed: bootstrap5_post_update_install_stable9

    .

    However, running updates from the Drupal Admin menu in the browser works without any warnings or errors (same as it was reported by @chriscant ).

    Clearing caches does not help to resolve the issue with drush updatedb.

  • πŸ‡©πŸ‡ͺGermany stefan.korn Jossgrund

    In my case the issue was with drush 10. Using drush 11 the update worked.

    Probably related to: https://github.com/drush-ops/drush/pull/5120
    and https://www.drupal.org/project/drupal/issues/3259188 β†’

  • πŸ‡©πŸ‡ͺGermany diqidoq Berlin | Hamburg | New York | London | Paris

    Just some small recommendations:

    If your installation is config driven, don't forget to switch stable and claro to stable9

    @VladimirAus you should probably declare for follow up readers what you refer to by "config driven" and "switch" - The context isn't obvious. Just a thought.

    Apart from that: @all remember that making stable9 visible is a "hack" and not intented. There is surely a reason for that core has it hidden by default. If sth is not working with stable9 being hidden and if it is a bug, then it should be proper reported depending on where this bug has been caused, maybe core, maybe Bootstrap5 or somewhere else. But this work around here is not a fix of an issue, it is just a work around hiding an underlying problem.

  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia

    @diqidoq
    Thanks for suggestion.
    It is part of help now: https://www.drupal.org/project/bootstrap5#upgrade3 β†’

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

  • Status changed to Fixed 11 months ago
  • πŸ‡ΊπŸ‡ΈUnited States bajah1701

    I'm getting this error when running drush updb on a fresh instance of Drupal 10.1.2. I'm using drush 12.1. As mentioned before unhiding stable9 should not be the correct way to fix this issue.

  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia

    @bajah1701
    Do you have error log? Please share if you do.

    1. Clear cache
    2. Run drush pm:list | grep -E "stable|classy" should result something like

      Core                                Stable 9 (stable9)                                                                      Enabled    10.1.2          
      Core                                Classy (classy)                                                                         Disabled   1.0.2           
      Core                                Stable (stable)                                                                         Disabled   2.0.0
    

    3. If now, uninstall classy and stable and enable stable9.

    drush theme:install stable9
    drush theme:uninstall stable classy
    
  • πŸ‡ΊπŸ‡ΈUnited States bajah1701

    @VladirmirAus

    I don't have an error log but going through the steps you provided solve the issue. Thank you

  • πŸ‡¦πŸ‡ΊAustralia VladimirAus Brisbane, Australia

    @bajah1701 anytime πŸ₯³
    Glad it worked.

Production build 0.69.0 2024