Unable to install the base theme since it does not exist. [#3121874]

This doesn't make any sense. Drupal/base is in the lock file...

composer.lock for drupal/base:

  {
            "name": "drupal/base",
            "version": "2.3.0",
            "source": {
                "type": "git",

composer.lock for lightning...

{
            "name": "acquia/lightning",
            "version": "4.1.3",
            "source": {
                "type": "git",

base does install on import...

  views: 10
  paragraphs: 11
  lightning: 1000
theme:
  stable: 0
  classy: 0
  seven: 0
  base: 0
  elevenfeat: 0
  adminimal_theme: 0
  collegegoalny: 0
profile: lightning

BLT Error on Acquia pipelines run:

  Unable to install the <em class="placeholder">base</em> theme since it does  
   not exist.

drush updb error locally:

  [notice] Update started: webform_update_8186
>  [error]  Base theme base has not been installed. 
>  [error]  Update failed: webform_update_8186

composer.lock for webform:

 {
            "name": "drupal/webform",
            "version": "5.9.0",
            "source": {
  .....

Oddly, there is no folder for base theme in the core/themes or docroot/themes/contrib folders. There seems to be zero articles about this project. There does seem to be a base profile, but that has no theme in it and we're indicating Lightning. I am very confused and would love some help in this matter. Thanks.

Comments

Comment #1

24 March 2020 at 00:30

loopy1492 created an issue. See original summary.

Comment #2

phenaproxima

he/him

English

Massachusetts

commented 24 March 2020 at 02:57

Category:	Bug report	» Support request
Status:	Active	» Postponed (maintainer needs more info)

I'm sorry, I do not understand how you came to this state of affairs. Snippets of composer.lock aren't super helpful, I'm afraid.

To find out why drupal/base is installed, I recommend trying composer why drupal/base. That should explain what is imposing the requirement. It's not Lightning, that's for sure; I never even heard of a theme called "base" until I opened this issue, and neither Lightning nor any of its components requires it. Not directly, anyway.

If you can put the output of composer why drupal/base here in this issue, I can look at it and see if anything jumps out to me. But I can't promise I'll be able to give any real help with this one; it seems like it might be a project-specific issue.

Comment #3

loopy1492 commented 24 March 2020 at 12:15

I was able to confirm, at least, that the theme called "base" is created and enabled by the drupal/base module. Even though it's not listed in the "Appearance" section of the site UI, it's certainly there.

When I remove base from the core extensions config, I get this when I try to drush cim...

 Configuration <em class="placeholder">base.settings</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                                  
  Configuration <em class="placeholder">block.block.alertbanner</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                        
  Configuration <em class="placeholder">block.block.base_account_menu</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                  
  Configuration <em class="placeholder">block.block.base_branding</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                      
  Configuration <em class="placeholder">block.block.base_breadcrumbs</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                   
  Configuration <em class="placeholder">block.block.base_content</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                       
  Configuration <em class="placeholder">block.block.base_footer</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                        
  Configuration <em class="placeholder">block.block.base_help</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                          
  Configuration <em class="placeholder">block.block.base_local_actions</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                 
  Configuration <em class="placeholder">block.block.base_local_tasks</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                   
  Configuration <em class="placeholder">block.block.base_main_menu</em> depends on the <em class="placeholder">base</em> theme that will not be installed after import.                     
  
.... et cetera ...

So now the question is why blt is having such a hard time finding this theme. I guess I'll have to pose this question in the drupal/base project. I wish I could switch projects in an issue.

Comment #4

loopy1492 commented 24 March 2020 at 12:10

Project:	Lightning	» Base
Version:	8.x-4.103	» 7.x-1.0

Comment #5

loopy1492 commented 24 March 2020 at 12:11

Version:

7.x-1.0

» 8.x-2.x-dev

Comment #6

loopy1492 commented 24 March 2020 at 12:11

Looks like I managed it.

Comment #7

loopy1492 commented 24 March 2020 at 12:11

Status:

Postponed (maintainer needs more info)

» Active

Comment #8

loopy1492 commented 24 March 2020 at 12:34

Version:

8.x-2.x-dev

» 8.x-2.3

Comment #9

loopy1492 commented 24 March 2020 at 12:45

Am I missing something? Should the drupal/base profile have a theme in the filesystem that isn't getting created in my installation for some reason?

Output from blt run, starting from cim attempt...

|            | block.block.bartik_page_title                                         | Delete    |
|            | block.block.bartik_local_tasks                                        | Delete    |
|            | block.block.bartik_local_actions                                      | Delete    |
+------------+-----------------------------------------------------------------------+-----------+
 [debug] Calling Drush\Drupal\Commands\config\ConfigImportCommands::doImport(Drupal\Core\Config\StorageComparer) [11.76 sec, 41.79 MB]
 [error]  Drupal\Core\Config\ConfigImporterException: There were errors validating the config synchronization.
Unable to install the <em class="placeholder">base</em> theme since it does not exist. in Drupal\Core\Config\ConfigImporter->validate() (line 755 of /var/www/docroot/core/lib/Drupal/Core/Config/ConfigImporter.php). [12.87 sec, 49.71 MB] 

In ConfigImportCommands.php line 261:
                                                                                          
  [Exception]                                                                             
  The import failed due to the following reasons:                                         
  Unable to install the <em class="placeholder">base</em> theme since it does not exist.  
                                                                                          

Exception trace:
  at /var/www/vendor/drush/drush/src/Drupal/Commands/config/ConfigImportCommands.php:261
 Drush\Drupal\Commands\config\ConfigImportCommands->doImport() at /var/www/vendor/drush/drush/includes/drush.inc:223
 drush_call_user_func_array() at /var/www/vendor/drush/drush/includes/drush.inc:214
 drush_op() at /var/www/vendor/drush/drush/src/Drupal/Commands/config/ConfigImportCommands.php:211
 Drush\Drupal\Commands\config\ConfigImportCommands->import() at n/a:n/a
 call_user_func_array() at /var/www/vendor/consolidation/annotated-command/src/CommandProcessor.php:257
 Consolidation\AnnotatedCommand\CommandProcessor->runCommandCallback() at /var/www/vendor/consolidation/annotated-command/src/CommandProcessor.php:212
 Consolidation\AnnotatedCommand\CommandProcessor->validateRunAndAlter() at /var/www/vendor/consolidation/annotated-command/src/CommandProcessor.php:176
 Consolidation\AnnotatedCommand\CommandProcessor->process() at /var/www/vendor/consolidation/annotated-command/src/AnnotatedCommand.php:302
 Consolidation\AnnotatedCommand\AnnotatedCommand->execute() at /var/www/vendor/symfony/console/Command/Command.php:255
 Symfony\Component\Console\Command\Command->run() at /var/www/vendor/symfony/console/Application.php:1005
 Symfony\Component\Console\Application->doRunCommand() at /var/www/vendor/symfony/console/Application.php:255
 Symfony\Component\Console\Application->doRun() at /var/www/vendor/symfony/console/Application.php:148
 Symfony\Component\Console\Application->run() at /var/www/vendor/drush/drush/src/Runtime/Runtime.php:118
 Drush\Runtime\Runtime->doRun() at /var/www/vendor/drush/drush/src/Runtime/Runtime.php:49
 Drush\Runtime\Runtime->run() at /var/www/vendor/drush/drush/drush.php:72
 require() at /var/www/vendor/drush/drush/drush:4

config:import [--preview [PREVIEW]] [--source SOURCE] [--partial] [--diff] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-d|--debug] [-y|--yes] [--no] [--remote-host REMOTE-HOST] [--remote-user REMOTE-USER] [-r|--root ROOT] [-l|--uri URI] [--simulate] [--pipe] [-D|--define DEFINE] [--notify [NOTIFY]] [--druplicon] [--xh-link XH-LINK] [--] <command> [<label>]

[Acquia\Blt\Robo\Tasks\DrushTask]  Exit code 1  Time 58.993s
[error]  Failed to import configuration!
For troubleshooting guidance and support, see https://docs.acquia.com/blt/support/ 
[error]  Command `drupal:config:import ` exited with code 1. This most likely indicates a problem with your configuration, and is not a BLT bug.
For troubleshooting guidance and support, see https://docs.acquia.com/blt/support/ 
[error]  Command `drupal:install ` exited with code 1. This most likely indicates a problem with your configuration, and is not a BLT bug.
For troubleshooting guidance and support, see https://docs.acquia.com/blt/support/ 
10:04 total time elapsed.

Comment #10

loopy1492 commented 24 March 2020 at 12:53

I wonder if this issue has to do with us using the lightning profile, but referencing the base theme which comes from the base profile.

Comment #11

loopy1492 commented 24 March 2020 at 13:31

It seems that switching versions has cause drupal/base to download into a different folder.

"drupal/base": "dev-develop" resolves as a contrib theme
"drupal/base": "^2.3" resolves as a contrib profile

Comment #12

loopy1492 commented 26 March 2020 at 17:14

Yep. Somehow, and for some reason, numbered releases are installing to the profiles folder while the develop branch is installing to the themes folder. This is a theme. Is this a bug?

Comment #13

brunosouza commented 4 May 2020 at 08:05

I can confirm this issue. In my case I was trying to upgrade my drupal site from 8.6 to 8.8 and in the process I enabled the claro module in development and set my custom theme base to claro but when I deployed the changes to UAT I got the same error:

> [notice] Update started: webform_update_8186
> [error] Base theme claro has not been installed.
> [error] Update failed: webform_update_8186

So I changed my base theme back to bootstrap, ran the updb again and re-changed it back to claro.

Comment #14

Antoine Lafontaine commented 27 January 2021 at 19:24

Sorry to be late on this, but this is not a theme, this is just a dead simple install profile I use to get a bare minimum drupal core install without any modules enabled, then do a config import to get all the modules and theme installed and leverage what is provided by drupal core to load configs packages in a profile.

If you look at the 8.2.x Readme, I also have a rough drush command to help symlink a config folder you would have outside of you profile folder.

This is a very narrow use case, but I think some people do like to use this to get started. It does speed up my own workflow when instanciating new projects.

Comment #15

Antoine Lafontaine commented 30 June 2021 at 15:08

Status:

Active

» Closed (works as designed)

Comment #16

loopy1492 commented 12 July 2021 at 19:43

Oh right. Never mind.

Unable to install the base theme since it does not exist.

Comments

Comment #1

Comment #2

Comment #3

Comment #4

Comment #5

Comment #6

Comment #7

Comment #8

Comment #9

Comment #10

Comment #11

Comment #12

Comment #13

Comment #14

Comment #15

Comment #16

News items

Our community

Documentation

Drupal code base

Governance of community