actually you should have an mysql root user – this user you have to use.
for one mysql server you can have multiple dbs.
I’m experiencing a similar issue. I have the same setup as LizardSF, and when I try to connect, I get the following error:
Warning: mysql_connect() [function.mysql-connect]: Can’t connect to local MySQL server through socket ‘/usr/local/mysql-5.0/data/mysql.sock’ (2) in /home/content/c/o/p/copythatsixfour/html/blog/wp-content/plugins/joomla-to-wordpress-migrator/joomla2wp-mig.php on line 1244
I’m sure the database username and password are correct because I just logged into it. :-/
Thanks so much for the work on the plugin – I look forward to hearing back!
– Jeff
can you please read the following and look if something may solve your problem?
maybe you have to provide a different server name instead of “localhost” please try the mysql host name your web hoster provides.
on godaddy you have a different mysql server then localhost.
I ultimately gave up on the wizard and used someone else’s PHP script along with some manual SQL to get enough of my content across. “Localhost” isn’t the issue. Godaddy will put all of your Joomla stuff in a database called something like “L123456789” and then put your WordPress stuff in a database called “W987675432”. Each database has only one user, but the user’s name is the same as the database name. Thus, you need to log in to the Joomla database with one User ID and PW, and into the WordPress database with a different User ID and PW. You cannot create a new user for either database, or change the user name. (You can change the password, but that’s not really the problem for the plugin.)
The plugin needs to have a “Source User” “Source Password” and a “Destination User”, “Destination Password” feature for it to be usable in these circumstances.
LizardSF,
Yeah, that’s what I see, too. Christian, if you’re interested, users of GoDaddy can’t use your plug-in. As LizardSF mentioned, GoDaddy puts Joomla content in one database, WordPress content in another, and besides having separate usernames and passwords for both databases, GoDaddy actually uses separate IP addresses for every database. Your plug-in, for GoDaddy users, should have “Source IP,” “Source User,” and “Source Password” as well as “Destination IP,” “Destination User,” and “Destination Password.” Everything else is fine, it seems.
Whoops. Don’t know why I posted the IP stuff – that doesn’t matter. Basically, what LizardSF said is all good – I didn’t need to repeat it. I guess I like to hear myself talk.
– Jeff
will integrate it in one of the nect releases – I think release 1.3.10 will have this feature
thanks, christian. i look forward to using it!
I am working on this – I saw on a customers godaddy account that they have a mysql connection like:
dbname.db.accountnumber.hostedressource.com
or similiar.
That means they have for each in the mysql server name the db name and account number included.
that means that the have for each db a seperate mysql server name.
Is it with your goddady account simliar? Can you provide me an example of the mysql server connection data you have from your webhoster for those two dbs?
please try the latest release.
christian,
works great! thank you for your hard work!
all the best, and happy holidays,
jeff
