Magento

I get that error whenever I click the check requirements button.  All of my configuration info is correct, and I have Magento running on the exact same server and same instance of php/apache/mysql as my osCommerce store.  I tried accessing the osCommerce DB directly as well as making a copy like the wiki suggests.  Am I doing something wrong or is there a problem with the tool?  I have attached screenshots to illustrate.  I tried using both ‘localhost’ and ‘127.0.0.1’, and yes 3307 is the correct port for me.  I also tried using 3306 just for drill.  And I’ve triple checked the password to make sure it’s correct.  I even copied it straight out of my osCommerce configure.php file.  I am running osCommerce RC2a and it is heavily modified, although there are very few DB changes, and no table prefix.

Click thumbnail to see full-size image

Hi,

I’ve got exactly the same problem. Ideas? Anyone?

Hi everyone

Same for me, checked DB data on OSC + on hosting Cpanel

Had also to turn off SEO to be able to make “oscommerce import tool” create and save a profile.

If anyone found the problem ?
Please Post

Best Regards
Patrick (France)

i got same problem.
At first, my db setting was

IP or Hostname : localhost
# of course i tried 127.0.0.1

and I run Magento on my same PC with virtualhost http://magento.local.

Then I changed “IP or Hostname” to “magento.local” and it work.

Ok, I figured out the problem and hacked up a solution but somebody better qualified than me should put in a fix to oscommerce migration tool. The problem is that the right connection isnt being used and here is why:

The connection is called oscommerce_foreign and it is a child of resources. core_read is also a child of resources. in app/code/core/Mage/Core/Model/Resource.php getConnection() the connection will use the parent resources if it has already been set. and since core_read is always used before oscommerce_foreign, the connection resources is always set before oscommerce_foreign, and since resources is a parent it is always used instead of oscommerce_foreign. I hacked up a workaround but I dont know the actual correct solution.