Closed (fixed)
Project:
Drush
Version:
8.x-6.x-dev
Component:
User Commands
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
6 Jun 2013 at 14:41 UTC
Updated:
1 Jul 2013 at 13:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
moshe weitzman commentedCommitted to 6.x in bb9bfd8. I'm gunshy about backporting to 5.x so I'm calling this Fixed.
Comment #2
greg.1.anderson commentedThis is totally awesome! I think that the call to drush_get_option is spurrious, though; it worked when I ran with --browser, but failed trying to do a local dispatch with --browser undefined. I think that the attached patch is what was intended.
Comment #3
moshe weitzman commentedthanks.
Comment #4
greg.1.anderson commentedPushed to 8.x-6.x.
Comment #5
moonray commentedI'm not sure if this is on related to this issue, but with remote uli I get the following
Should I be getting that kind of output?
Comment #6
greg.1.anderson commentedWhat version of Drush do you have on the remote side? You could try updating the remote Drush to the latest dev -- although I'm pretty sure that I've used this feature with an older Drush without trouble. Are you using the latest dev on your local machine? That's the most important thing; won't work otherwise.
Comment #7
moonray commentedI'm using latest dev on local.
I'm using an older (probably 5) on remote.
drush uli works (it opens the browser and everything), I just get a lot of extra data spit out by the CLI when running on a remote site, which I don't get when running it on a local site.
Comment #8
greg.1.anderson commentedYou should be able to get rid of the output from #5 if you update your remote host to the latest Drush-8.x-6.x-dev. For the uli command, this output should be innocuous.