Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I get this error when updating through drush:
The commons directory could not be found within the modules directory at /data/drupal/community/profiles/commons, perhaps the project is enabled but has been deleted from disk.
This seems to happen with distros sometimes, any ideas on how to solve it?
Comments
Comment #1
blacklabel_tom CreditAttribution: blacklabel_tom commentedHi,
Can you post up your Drush command and can you double check the directory permissions please (I feel bad for asking, but it could be something simple!)
Cheers
Tom
Comment #2
Gerben Zaagsma CreditAttribution: Gerben Zaagsma commentedHi, thanks and no worries about asking. Permissions are 755. The error also happens on my MAMP dev folder with similar permissions.
Not sure what you mean by post up the command?
Best,
Gerben
Comment #3
blacklabel_tom CreditAttribution: blacklabel_tom commentedSorry I meant to ask if you are running something like 'drush up commons' or anything different
Comment #4
Gerben Zaagsma CreditAttribution: Gerben Zaagsma commentedah i see, I use drush up (which gives me updates for modules in the commons as well as sites folder).
Comment #5
blacklabel_tom CreditAttribution: blacklabel_tom commentedCould you try 'drush up -v' and see what the output says
Comment #6
ezra-g CreditAttribution: ezra-g commentedMarking as postponed pending #5, however I suspect this may be related to this code in commons.profile:
Comment #7
Gerben Zaagsma CreditAttribution: Gerben Zaagsma commentedThis is the output of drush up -v:
Comment #8
ybabel CreditAttribution: ybabel commentedSame problem here when upgrading from 3 to 3.1
All the modules can be updated individually with drush up.
But "commons" cannot.
I think it's because it's not a module but a profile. And maybe drush don't know how to do it ?
Comment #9
tanius CreditAttribution: tanius commentedThis seems to be a Drush issue: Drush issue #1880362.
That issue also is in the "needs more info" state, so maybe somebody from here wants to provide necessary input there so we can get this fixed?
Comment #10
Johnny.Love CreditAttribution: Johnny.Love commentedI am running into the same problem - any solutions?
Comment #11
Johnny.Love CreditAttribution: Johnny.Love commentedI found this link - http://drupal.org/node/1476994
Then used drush dl commons - proceed to install - problems solved.
Comment #12
markbannister CreditAttribution: markbannister commentedThis just made a mess for me I had to roll it back.
Drush 6.0 Drupal 7.23
edit:
Any thoughts on a work around/fix?
Comment #13
markbannister CreditAttribution: markbannister commentedThe fix was fairly straightforward when I finally realized what was going on.
First drush (v6) had been duplicating modules into the sites/all/modules and not putting them into commons profile. Fixed duplicates then ran drush rr (registry rebuild)
Manually downloaded commons 7.x.3.x.dev, it duplicated a few modules in sites/all/modules so I moved all duplicates to profiles/commons. It also duplicated drush registry rebuild.
ran drush rr for all sites (this is multi-site)
ran drush updatedb for all sites, cleared all caches
ctools was duplicated and now giving issues. rebuild is not fixing it's new home -- updated to latest registry rebuild and it was fixed -- or maybe a cache issue....
Now oddly, links don't work on any page....this is weird, they are formatted...ok there is a them update I missed-- jquery error a.attributes is undefined... crap sounds obscure...
Comment #14
ezra-g CreditAttribution: ezra-g commentedPlease start your upgrade process again following the process at http://docs.acquia.com/commons and re-open the issue if you're still having problems.
Comment #15
markbannister CreditAttribution: markbannister commentedopened as new issue: https://drupal.org/node/2100175
Comment #17
robertgarrigos CreditAttribution: robertgarrigos commentedI have this error while trying to update commons (duplicate issue at #15 has nothing to do with this one).
I have a fresh install of commons 7.x-3.5 now trying to update to 7.x-3.8. This is a drush up -v:
Comment #18
lsolesen CreditAttribution: lsolesen commentedPlease reopen with exact commands you are using, if this problem still persists?