Hello,
I am a volunteer running a website for a soccerclub. I am preparing an upgrade of Drupal 6.22 to 7.0
I
- installed the latest DRUSH for windows today. It works on upgrade modules on Drupal 6.22
- have a site on "D:\xampp\htdocs"
- execute DRUSH while in d:\xampp\htdocs
- have a file "aliases.drushrc.php" in d:\xampp\htdocs
- made a map in htdocs called "waspik7" where I want the upgraded site to go"
The file "d:\xampp\htdocs" has the following code:
$aliases['onward'] = array(
'root' => '/waspik7',
'uri' => 'http://127.0.0.1/vvwaspik7',
)
$aliases['from'] = array(
'root' => '/',
'uri' => 'http://127.0.0.1',
'db-url' => 'mysql://pvo:waspik@127.0.0.1/vvwaspik_drup1'
)I use the command: drush @from site-upgrade @onward
I get the following output:
D:\xampp\htdocs>drush site-upgrade @onward
$aliases['onward'] = array(
'root' => '/waspik7',
'uri' => 'http://127.0.0.1/vvwaspik7',
)
$aliases['from'] = array(
'root' => '/',
'uri' => 'http://127.0.0.1',
'db-url' => 'mysql://pvo:waspik@127.0.0.1/vvwaspik_drup1'
)$aliases['onward'] = array(
'root' => '/waspik7',
'uri' => 'http://127.0.0.1/vvwaspik7',
)
$aliases['from'] = array(
'root' => '/',
'uri' => 'http://127.0.0.1',
'db-url' => 'mysql://pvo:waspik@127.0.0.1/vvwaspik_drup1'
) Project Titel Installed Available Status
acl ACL 6.x-1.4 7.x-1.0-rc1 Supported
list of all modules etc. ending with a link to http://drupal.org/node/1013034.
$aliases['onward'] = array(
'root' => '/waspik7',
'uri' => 'http://127.0.0.1/vvwaspik7',
)
$aliases['from'] = array(
'root' => '/',
'uri' => 'http://127.0.0.1',
'db-url' => 'mysql://pvo:waspik@127.0.0.1/vvwaspik_drup1'
)$aliases['onward'] = array(
'root' => '/waspik7',
'uri' => 'http://127.0.0.1/vvwaspik7',
)
$aliases['from'] = array(
'root' => '/',
'uri' => 'http://127.0.0.1',
'db-url' => 'mysql://pvo:waspik@127.0.0.1/vvwaspik_drup1'
)Site alias not found: @onward. See example.drushrc.php. [error
]
D:\xampp\htdocs>
I do not know what to do about "Site alias not found: @onward"
I read the recommended file and searched for examples and help.
Althoug I am acquainted with computers and programming this is really not simple stuff. But Drush is an awfull tool as I know now from updating modules.
Please help me with my problem and I will describe step by step what I had to do to upgrade my local site.
By the way:
I also tried "drush @from site-upgrade @onward " but this did not even generate the list with modules.
Hope you will help me. I will give lessons learned back here or to be used in documentation.
Thanks in beforehand!!!
Comments
Comment #1
greg.1.anderson commentedTry putting a
<?phpat the beginning of your aliases.drushrc.php file. After you havedrush sa @onwardworking, double-check the paths you are using for 'root' in your aliases. There are some issues with Drush on Windows; you may have more luck at this point using it in a vm running Linux. If you do use Windows, make sure that you are using the installer from 23 November (yesterday).Comment #2
PvO commentedThanks. I 'll try
and close with. Yes i read about the last installer. I spent two evenings before that with the old one searching for what I did wrong. Happy to find the new installer yesterday. I will let you know my findings.Comment #3
greg.1.anderson commentedIt is recommended that you should not close your .inc or .module & c. files with
?>.Comment #4
PvO commentedI think the changes in the aliases.drushrc.php is a step forward.
So I start the upgrade but it almost immediately stops and returns this error:
First is the message about creating a directory.
What directory is DRUSH trying to create?
I do have 17.4 Gb free in my c:\drive.
What now?
Thanks
P.S. I understand it has nothing to do with my hd drive.
Meanwhile I changed the php.ini memory_limit to 500M in D:\Program Files\Propeople\Drush\Php and in D:\xampp\php.
Still the same message.
I read about a php.ini in a CLI directory on Linux systems, but can not find such a directory on my C: or D: drive.
Comment #5
PvO commentedComment #6
PvO commentedI managed to get the upgrade to start.
The "aliases.drushrc.php" file is now like this:
So the rootpath is a full path.
But ... the upgrade was still not succesfull. I will start a new support request as I managed to start it up now.
Comment #7
greg.1.anderson commentedMarking closed.