We want to move a Domain (ex. www.abc.com) to another Magento Installation. For this Domain, there is a Shop running with products and already sales.
My question is:
When we move the domain (only the domain, no sales or products), does this have effect on the old magento installation?
No there will be no issue when you move your existing domain to new Magento Installation. If you want to connect your old Magento installation to any other domain, you need to change base url from core_config_data table in database.
Related
I downloaded a old magento site and installed it on my local server.
My admin panel is working perfect but products are not listed in frontend.
Links on the front end page are also not working.
When you say that you 'downloaded an old magento site', do you mean that you just copied down the folder structure?
If so, this won't have copied the product database, which is an entirely separate entity to the php/js/html/css that comprises the file structure.
Try reindexing and clearing the cache. Also, did you make sure the Base urls were updated in core_config_data database table?
THis is probably a dumb question, but I am currently moving to a new install of Magento. I'm on a Ubuntu server with nginx. The current installation is at /var/www, but I moved it to /var/wwwOLD so that the new site could be at /var/www. Is there a way to access the old site without renaming the new directory one to something else and the old one back to /var/www?
Sorry if this doesn't make much sense or is a common sense question that I should already know.
You setup a duplicated version of Magento in a separate folder by doing the following.
Configure a subdomain that points to the old folder. Example: oldsite.yoursite.com
Duplicate the Magento database to a new database
Edit the core_config_data table in the duplicated Magento database and edit the records with the path values web/unsecure/base_url and web/secure/base_url to the oldsite.yoursite.com domain value.
Edit the app/etc/local.xml file to point to your duplicated database (the one with your updated urls in the core_config_data table)
Delete everything in the var/cache folder.
I intially had an instance of magento installed that was using a databse, then i intalled another intance of Magento Using the same database, but the problem that occured is that now my old website is getting redirected to new website.
I had configured my old Website's url from localhost to somethingElse.
So, is there a method such that both the websites use the same Database. If so then how to configure it to do so?
You don't need to install another Magento in order to create a new Website, Magento already supports multiple websites on the same instance.
Here is a detailed explanation on Magento websites,stores and store views: http://www.magentocommerce.com/knowledge-base/entry/overview-how-multiple-websites-stores-work/
I bought after the installation of magento template, uploading demo database and a few time later, the site URL / work160.com / domain name is directed. I delete and re-install again I have to. Magento is in line with our demo pages bring our own? This problem can be solved with a regulation or in?
If your magento is redirected on another website (that is how i understand your question), you can do those steps:
check your basic secure and unsecure URL configuration, there should be your server adress
if you cant not login to admin during redirect, fo to the database to table named core_config_data and make sure there is right set up web/unsecure/base_url and web/secure/base_url both will have to value http://www.something.ok/ the last "/" is important
Reindex / fush cached data (delete magento/var folder if you cannot pass admin)
Refresh data in your browser (or use another one / anonymous mode)
and ... thats all
I am using latest magento 1.7.0.2.
I have two different stores in my site.
customer from first store should not be able to login to second store.
So,Want to set up store wise login for customers.How to set ?please help.
Unfortunately Magento only allows you to set "customer sharing" across the global and website scopes. The (maybe not so simple) solution would be to move your other store to a separate website instead of a separate store.
Found in System > Configuration > Customers > Customer Configuration: