I have a Drupal 7 site with 3 themes enabled:
- Foo
- Adminimal
- Shiny
Foo is a custom theme for the front-end, located in /sites/foo/themes/
and set as the default.
Adminimal and Shiny are both installed via drush make
into sites/all/themes/contrib/
.
Running drush pm-updatestatus
disables the default 'Foo' theme.
$ drush pm-updatestatus
Checking available update data ... [ok]
Failed to check available update data for Foo settings. [ok]
Checked available update data for Administration menu. [ok]
...
Checked available update data for Adminimal. [ok]
Checked available update data for Shiny. [ok]
Failed to get available update data for one project. [error]
Checked available update data for 64 projects. [status]
Name Installed Version Proposed version Message
Administration menu Adminimal Theme (adminimal_admin_menu) 7.x-1.6 7.x-1.7 Update available
...
Adminimal (adminimal_theme) 7.x-1.21 7.x-1.24 Update available
Shiny (shiny) 7.x-1.6 7.x-1.7 Update available
The Failed to check available update data for Foo settings.
& Failed to get available update data for one project. [error]
lines from the output clearly look relevant, but I'm struggling to identify the underlying cause.
With the Drush's -d
debug flag enabled the output includes this line before the Failed to get update data for on project [error]
:
Undefined index: foo theme.inc:100 [1.78 sec, 35.7 MB] [notice]
drush pm-list
has the same effect.
Presumably there's something wrong with the declaration, or location of the Foo theme?
Checking the status report via the Drupal admin does not disable the Foo theme.
Why would drush pm-list
& drush pm-updatestatus
disable the default theme?
Failed to get update data for on project [error]
. So this is normal for custom modules or themes. It should however not disable the theme. – Neograph734 May 20 '16 at 11:14