Reported to me by danlinn.

I think this may be related to #1597846: drush bp command fails when using drush parameters

Investigating now.

CommentFileSizeAuthor
#2 boilerplate-drush-profiles-custom-1890418-2.diff1.74 KBtwardnw

Comments

twardnw’s picture

twardnw commented
Title: drush command does not work when theme is in /profiles directory » drush bp does not place theme in correct folder, when boilerplate is in /profiles

The drush bp command is finding the path to the theme wherever it lives. When in sites/all/themes (/contrib too), it properly creates the new theme in that directory structure. However, if bolerplate is in a profile, it creates the new theme in /profiles/<profilename>/themes/<newtheme>.

twardnw’s picture

twardnw commented
Status: Active » Fixed
StatusFileSize
new boilerplate-drush-profiles-custom-1890418-2.diff1.74 KB

Here's a patch that makes the command aware of boilerplate existing in the profiles directory, as well as still checking to see if the theme should go directly into themes or themes/custom

Also committed to -dev

Status: Fixed » Closed (fixed)

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