Magento

Hello

i’m trying to moving my magento to another account in my host provider (I’m not changing host ....just accounts..)
so i restore the old database to my new account and copy my old /media/catalog folder to /media/ folder in the new account

if i check my frontend from the real path http://www.p.rimarydom.ain .co.m/magentofolder everything works fine

but this error is comming up when i test a category from the frontend with a new domain name that i bought earlier and assigned to the magento folder.. http://www.new domain.com
Do i have to configure it in the Configuration --> Web --> Base URL??? What is the correct format...??

thanks

For clean transfer:
Before dumping the database for new domain, set in Configuration > Web > (both Unsecure and Secure) > Base URL to {{base_url}}
After restoring the backup on new domain, do not forget to set the correct domain names there.

Alternatively, you could edit Magento database on new server, table core_config_data, and update records where path like ‘web/%/base_url’

thank you ..! 

elina - I’m trying to do this too and was just wandering how you restored your old database.

thanks

I did that and here is my error after importing all my database…

how did you import your database?

I imported my database just through a sql tool and am getting a similar error:

Fatal error: Call to a member function getAttributeCode() on a non-object in /home/onlyecom/public_html/magento/app/code/core/Mage/Catalog/Model/Product/Type/Configurable.php on line 326

jimmypalmer - 03 June 2008 06:41 AM

how did you import your database?

Hi jimmypalmer,

I went into phpmyadmin, export all the database (structure and data) and import the .sql file in ssh by a dump command…

when i go in my phpmyadmin of my new hosting, I see everything has been imported well…

hello

first i created a new database name with the same name as before and
to restore my old database i went into phpMyAdmin , in the new empty db and import the .sql

Don’t forget to go to admin-->configuration and refresh all the cache areas.  It does wonders.  If you don’t, you’ll be seeing a mix of cached and new URLs on the front end.