drushrc.php is no longer sourced from Drupal root; sites/all/drush is the new location

Note, drush cache-clear drush has no effect on this issue, the extra options are still missing.

More debugging:

If I replace the default sites/default folder provided by Drupal with a symbolic link to my site folder, the cache-clear options are found.

ie, this works:

# sites/default --> symlink to sites/example.com
#
# drush cc 
Enter a number to choose which cache to clear.
 [0]   :  Cancel         
 [1]   :  all            
 [2]   :  drush          
 [3]   :  theme-registry 
 [4]   :  menu           
 [5]   :  css-js         
 [6]   :  block          
 [7]   :  module-list    
 [8]   :  theme-list     
 [9]   :  registry       
 [10]  :  views    

The real issue here is that drushrc.php is apparently no longer being sourced from the Drupal root folder, as it was in drush 4.x

this excerpt from examples/example.drushrc.php explains the issue...

Configuration files are loaded in the reverse order they are
shown above.  All configuration files are loaded in the first
bootstrapping phase, but the configuration files stored at
a Drupal root or Drupal site folder will not be loaded in
instances where no Drupal site is selected.  However, they
_will_ still be loaded if a site is selected (either via
the current working directory or by use of the --root and
--uri options), even if the Drush command being run does
not bootstrap to the Drupal Root or Drupal Site phase.
Note that this is different than Drush-4.x and earlier, which
did not load these configuration files until the Drupal site
was bootstrapped.

We have been using drushrc.php in the drupal root, to *specify* which environment to load via the $options['uri'] = "http://example.local';.

We're looking into another way to solve this, but any suggestions are recommended. Thanks.

Fixed the long form --uri (was inadvertently specified as --url) I usually use the shorthand version.... -l (dash L).

For the moment, the only solution is to symlink sites/default/settings.php to the proper settings file in the multi-site folder.

eg

sites/default/settings.php --> symlink to: sites/example.local/settings.php (on local environment)
sites/default/settings.php --> symlink to: sites/stage.example.com/settings.php (on staging environment)
sites/default/settings.php --> symlink to: sites/example.com/settings.php (on production environment)

Anyone know of another way to do this?

Added Proposed Solution, and elaborated on Problem/Motivation.

Greg,

I've moved my symbolically linked drushrc.php out of drupal root into sites/all/drush and this worked perfectly. I've added this to the Proposed Solution above.

However, in my testing I wasn't actually ever able to get a drushrc.php to even *load* from the Drupal root with drush 5, even after putting the proper uri in sites/all/drush/drushrc.php

you should be able to re-enable the Drupal root as an install location for drushrc.php by setting $options['config'] = 'path'; in a drushrc.php file that is being loaded.

Right, ok... except example.drushrc.php claims that drushrc.php would be loaded in the drupal root, if --root or --uri would be specified:

...the configuration files stored at a Drupal root or Drupal site folder will not be loaded in instances where no Drupal site is selected. However, they _will_ still be loaded if a site is selected (either via the current working directory or by use of the --root and --uri options).

but this is clearly not the case.

So, ideally, there needs to be two changes:

- have Drush 5 check for drushrc.php in a Drupal root, even though it doesnt source the file, and provide a deprecated warning.
- update example.drushrc.php to explain properly how to get drushrc.php to be sourced from a Drupal root.

thoughts?

Ah, my bad. I missed comment #8.

Here's a patch for documentation examples/example.drushrc.php.

Also, I noticed that the column wrap in that file is not anywhere close to 80 columns, and sometimes varies widely. I wouldn't mind adjusting that and providing a patch, as long as it could get applied reasonably quickly, so as not to have to continuously re-roll.

UPDATE: There were two whitespace cleanups that snuck into the patch, because my editor is set to remove them by default. I can remove if needed.

Here's a general doc cleanup of the example.drushrc.php

I stumbled across one thing... there is an example for options to `drush core-cli`, but that command appears to have been removed from Drush 5 (is that correct?).

After this patch is applied I'd also like to reorganize a few of the entries and group them together more logically, for example, by putting the general Drush global options at the top, and then more specific but shared common commands' options below....

UPDATE:
e.g. --package-handler seems out of place between the --default-major and the --include options, which both apply to Drush's bootstrap itself.

^ that was a poor example.. heres a better one:

--self-update, --default-major, --package-handler which apply to download and update commands, seem out of place between the --config and the --include options, which apply to Drush's bootstrap itself. Also, the -v option could be moved up to the top along side -l and -r.

Fixed two more tiny mistakes in the first couple sentences.