Hi,
on my Debian machine i wanted to use DM to create a Multisite in a new empty dir that is within the apache htdocs folder but got the following errors, whatever version i pick at the end, following exactly the steps described on your website

dir with these rights:
Debian:/my/root$ drwxr-xr-x 2 something something 4.0K 2010-06-06 15:30 multisite

ERROR v1:
Debian:/my/root$ sudo drush multi-create /multisite --core=6.x
Missing argument 2 for drush_multi_create_validate() [warning]
multi.drush.inc:605
Invalid argument for destination, /multisite is no directory. [error]
Aborting
An error occurred at function : drush_multi_create_validate [error]

ERROR v2:
Debian:/my/root$ sudo drush multi-create /my/root/multisite --core=6.x
Missing argument 2 for drush_multi_create_validate() [warning]
multi.drush.inc:605
Missing argument for major-version. Aborting [error]
An error occurred at function : drush_multi_create_validate [error]

ERROR v3:
Debian:/my/root$ sudo drush multi-create /my/root/multisite --core=6.17
Missing argument 2 for drush_multi_create_validate() [warning]
multi.drush.inc:605
Missing argument for major-version. Aborting [error]
An error occurred at function : drush_multi_create_validate [error]

ERROR v4 (a bit different):
Debian:/my/root$ sudo drush multi-create /my/root/multisite --core=7.x
[sudo] password for myrootusername:
Missing argument 2 for drush_multi_create_validate() [warning]
multi.drush.inc:605
Undefined variable: core multi.drush.inc:625 [notice]
Missing argument for major-version. Aborting [error]
An error occurred at function : drush_multi_create_validate [error]
Command dispatch complete [notice]

Is there something not documented about the correct version that has to be put in at "7.x" or why does it got this way:

function drush_multi_create_validate($destination) {

else if (!is_dir($destination)) {
return drush_set_error('MULTI_INVALID_DESTINATION',
dt('Invalid argument for destination, !destination is no directory. Aborting',
array('!destination' => $destination)
)
);
}

Best Regards
Torsten Zenk

Comments

fl3a’s picture

Category: bug » support
Priority: Critical » Minor
Status: Active » Closed (fixed)

Trying to reproduce that...

Error v1 is very easy:

Invalid argument for destination, /multisite is no directory. [error]
Aborting
An error occurred at function : drush_multi_create_validate [error]

Please look at the above output, as you wrote, your pwd is /my/root but you have supplied multisite as an absolute path.

Invalid argument for destination, /multisite is no directory. [error]

Error v3 and v4 are easy too:
v3:

drush multi-create /tmp/ --core=6.17 -vd
[...]
No release history available for drupal 6.17.x. [1.8 sec, 4.14 MB]                                            [error]
[...]

You have supplied a release not a core compatibility (5.x, 6.x),
according to this one, drush multi tries to request http://updates.drupal.org/release-history/drupal/6.17.x which is does'nt exist.

v4:
According the fine manual, Drupal 7 is not supported yet. (Since http://updates.drupal.org/release-history/drupal/7.x does'nt contain <recommended_major>7</recommended_major>).

Can not reproduce Error v2, please make sure, that you use the latest version from cvs be more verbose, please use verbose and/or debug option for your messages.

Regards
Florian

pimok3000’s picture

Ups , sorry, about the wrong paths, didn´t recognize that. After updating drush to the latest version all went well but the version error remains. It works when i leave away the .x in --core=6.x.

Best
Torsten

fl3a’s picture

Title: Missing argument 2 for drush_multi_create_validate() » multi-create --core=6.x -> multi-create --core=6
Assigned: Unassigned » fl3a
Category: support » bug
Status: Closed (fixed) » Needs work

Thanks for pointing me on this one, this is definitely a bug while the others above were layer 8 mistakes :D

Will fix it asap.

fl3a’s picture

Assigned: fl3a » vitaminless
Priority: Minor » Major
fl3a’s picture

Assigned: vitaminless » fl3a
Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.