Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drush doesn't pick up on modules it downloaded in 8.x #104

Closed
brianV opened this issue Sep 13, 2013 · 5 comments
Closed

Drush doesn't pick up on modules it downloaded in 8.x #104

brianV opened this issue Sep 13, 2013 · 5 comments

Comments

@brianV
Copy link

brianV commented Sep 13, 2013

drush dl downloads the project to the correct folder in d8, but drush en doesn't find it.

brian@brian-MS-7599:~/Workspace/drupal$ drush dl devel 
Project devel (8.x-1.x-dev) downloaded to modules/devel. [success] 
Project devel contains 3 modules: devel_generate, devel_node_access, devel.   
brian@brian-MS-7599:~/Workspace/drupal$ drush en devel
devel was not found. [warning] 
The following projects provide some or all of the extensions not found: [ok] 
devel 
Would you like to download them? (y/n): y 
Install location modules/devel already exists. Do you want to overwrite it? (y/n): y 
Project devel (8.x-1.x-dev) downloaded to modules/devel. [success] 
Project devel contains 3 modules: devel_generate, devel_node_access, devel. devel was not found. [warning] 
The following projects provide some or all of the extensions not found: [ok] devel     
Would you like to download them? (y/n): 
@mgifford
Copy link

Why is it getting downloaded to modules/devel ?

I ran into this problem too. I then created sites/default/modules and Drush downloaded it there.

I also created sites/all/modules/contrib but even when installing from sites/all the module was installed in sites/default/modules

The change is a bit confusing.

@weitzman
Copy link
Member

I can say that the expected behavior in D8 is to default to /modules as sites/all is deprecated.

Sounds like there is a bug here though.

@seanr
Copy link

seanr commented Oct 27, 2014

This bug still stands, I think, but in my case it's downloading it to ~/.drush/, not the modules folder like it should.

@bradjones1
Copy link
Contributor

I can vouch for the original bug report. Drush will download the module (or, in my case, theme) to the proper directory in the present install, however when it goes to enable the module it doesn't discover the just-downloaded files. If you ctrl-C out of the operation and then do a drush en -y just-downloaded, it works as expected.

@jonhattan
Copy link
Member

@bradjones1 It seems you're suffering #5. The issues reported in the other comments above are already fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants