Closed (fixed)
Project:
Omega
Version:
7.x-4.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Dec 2012 at 03:35 UTC
Updated:
14 Jan 2013 at 22:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
realityloop commentedusing Drush 5.8 on OSX as per configuration in post here:
http://realityloop.com/blog/2012/07/03/nginx-mariadb-php-aegir-mac-os-x-...
Comment #2
fubhy commentedShould be --destination="sites/realityloop,com". In 4.x we also support profiles or parent themes as destination (e.g. --destination="profile/standard" or --destination="theme/foo" (put's it UNDER the parent theme named "foo")).
Comment #3
fubhy commentedNote: You can use "drush help | grep omega" to get the list of omega commands and "drush help omega-subtheme" to get a detailed description of the omega-subtheme command.
Comment #4
realityloop commentedAh, that makes sense, unfortunately I've tried all the iterations I can think of and I'm still getting the error..
Comment #5
fubhy commentedPlease try the latest dev (4.x-dev) preferably directly from git or apply the attached patch and see if that fixes it for you. If it doesn't, then please read http://drupal.org/documentation/install/multi-site ... The drush script only allows you to choose valid /sites destinations which have to be registered in /sites/sites.php (@see that documentation page that I linked).
Comment #7
realityloop commentedhave drush cc drush, drush cc all, and still getting the same errors.
content of my sites.php file
Comment #8
fubhy commentedThis:
realityloop.ldis your --destination then! So you would go --destination="sites/realityloop.ld". I will probably add some better error reporting code for when the destination is invalid (e.g. show all available "sites" when "sites/" is used or show all available profiles when "profile/" is used or show all available base theme when "theme/" is used.Furthermore I am wondering if we should use the array value instead of the array key for $sites.... Does that make more sense? I thought going with the array key was saner. Thoughts?
Comment #9
fubhy commentedCan you confirm that this works? I just tagged alpha3 which includes the fix for this. I will add more verbose error messages later.
Comment #10
fubhy commentedAlright, I added verbose error messages (user prompt) when an invalid destination is given... The destination syntax was changed to look like this:
--destination="site:example.com" / --destination="theme:bartik" / --destination="profile:standard"