Closed (fixed)
Project:
Drush
Version:
6.x-1.0
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
22 May 2008 at 22:22 UTC
Updated:
28 Apr 2009 at 17:40 UTC
Jump to comment: Most recent file
If a Drupal installation has a theme that can be updated, drush pm update lists that theme and tries to update it the same way as it does with modules. This fails when trying to create a backup directory, as the $project['path'] obtained through the update module is apparently empty for themes. If drush fails because of this, it might mean that other modules cannot be updated unless the theme has been updated manually.
I understand that drush currently doesn't handle theme updates, but IMHO this shouldn't break the update process for regular modules.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | drush_theme_support-v2.patch | 1.12 KB | marquardt |
| #3 | drush_theme_support-v1.patch | 1.13 KB | marquardt |
| #1 | skip_theme_updates-v1.patch | 718 bytes | marquardt |
Comments
Comment #1
marquardt commentedI've attached a simple workaround for the problem which simply skips themes in the update loop in drush_pm.module and prints out a warning saying that a theme has been skipped.
In the long run, it would be nicer if drush could also handle themes, of course... How can I obtain the installation path of a theme - or why does update not put it into the $project array for themes as it does for modules? Apologies if that's a stupid question...
Comment #2
marquardt commentedUpdating status...
Comment #3
marquardt commentedSorry - it was a stupid question (on the installation path of themes). They are are constructed in drush_pm_get_project_path(), of course.
I've attached an alternative patch which obsoletes the first one. Now, paths to themes are found correctly, and they are backed up and updated properly. Could someone test if this minor modification does indeed enable drush to update themes?
Comment #4
moshe weitzman commentedLooks good to me. Anyone available to test?
Comment #5
marquardt commentedRerolled patch from comment #3 against 1.0 release. No changes, just two lines offset, really...
Comment #6
moshe weitzman commentedfixed elsewhere.