![]() ![]() json file for composer by removing the lines for drush and then running composer global update which then finished the job by removing the actual drush files. I updated Yosemite, where Drush, Mamp and everything was working fine, to El Capitan. I have decided for better or worse to try again. Update #įirst off, thank you for the folks who commented on the original issue. ![]() Little Snitch 3.6 (mentioning this because of this thread).Sometimes I just want to switch to Ubuntu full time and say goodbye to the Mac OS. Normally I wait at least a month or two before upgrading to Apple's latest release but I got reckless and now this is the price. Has anyone else come across this behaviour?įortunately, I made a full bootable backup of Yosemite so I will 'simply' roll my Mac back to how it was setup prior to the so-called upgrade of El Capitan. I've updated Composer and made sure that stable Drush 7.0.0 is running. This is now happening on all my Drupal sites locally, and yes, I am at the root of the Drupal install directory where this command would normally work. Wrong or the php-cli may have no access to it in a jailed shell. ![]() Working database setup by specifying the URI to use with the -uri In this case you can select another site with a * bootstrap a site that has not been installed or does not have aĬonfigured database. Hint: This may occur when Drush is trying to: ĭrush was not able to start (bootstrap) the Drupal database. The drush command 'status-report' could not be executed. Will need to invoke drush from a more functional Drupal environment Doing a simple: drush status-reportĬommand core-requirements needs a higher bootstrap level to run - you After updating my Mac from Yosemite to El Capitan, I am noticing drush does not run properly on any of my sites. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |