Please reply your thoughts

1)
Don’t forget to change configured URL of origin shop to the URLs of new shop in the table core_config_data. You can also use Search-Tool of phpMyAdmin and identify every record where old URL is used – but outside of core_config_data table they are not so important and could be changed later in the Shop interface.”
2) I think, in that case you also have to modify redirection rules in your .htaccess files. Look on both of them. I the root and in new sub-folder.

However it’s not a best idea to copy magento into sub-folder of another installation.

Solution is duplicate downloader file and replace the path with a usual software like ultraedit netbean and upload th new donloader … enjoy it’s work
AlfaG

While we were able to get much of our Magento installation duplicated using the excellent tips here, I was never able to get Magento Connect working properly (a major objective of duplicating an installation).

We eventually abandoned 6 moths of fighting with Magento and now use a Drupal-based cart called Ubercart, which is faster, simpler, more flexible, and broadly supported by the community. Much frustration and anger was relieved by this change.

i m reading the last one and i think i m in this case. Anybody could confirm please :

original path : /home/clients/client7/web9/web
duplicat path : /home/clients/client26/web28/web

i understand that this commands can’t run :

find . -type f -exec grep -q “/home/clients/client7/web9/web” ‘{}’ \; -print

find . -type f -print | xargs sed -i -e ’s//home/clients/client7/web9/web//home/clients/client26/web28/web/g’

Correct ?

CDL

A

Therefore the above mentioned command only works if the old path and the new path have exactly the same length.

If this is not the case you have to read in the configuration inside php unserialize the structure, change the configuration and rewrite the file with the new serialized string.

_http_://magento.novosoftwares.com/magento-installation/magento-installation-requirements/

Kind Regards,

Team Novo

For some reason hand editing that file corrupts the ini file.
The system seems to work without it and extensions install to the new installation directory instead of constantly trying to use the old directories.

However… it seems that there are many hundreds (maybe thousands) of references to fully qualified domain names (FQDN) in the data itself. And they are in any number of different forms — “http://mySite.com”, “http://mysite.com”, “http://www.mysite.com” and then the ones for https, and ones with or without the trailing slash.

So … I am getting up to speed with an organization that has little technical experience, so am wondering — shouldn’t it be the case that all URLs should be relative references? Is there some macro that pulls on the correct secure or unsecure URL from the core data table?

Any ideas about where I can look (source code or otherwise) to help me understand how things should have been done would be greatly appreciated!

Tom

It’s a little disheartening for me, as a new Magento user to see that there’s not an automated process for building a test or staging or development platform. One would think this is a pretty key function of an e-commerce platform (and especially one that’s open-source!)

But that’s just me whining. Thank you for saving me a great deal of work. And I hope I can return the favor by automating it in a script, and post it somewhere.

Tom

Btw, great blog!
Thanks,
Erwan

Anyway I have new experiences how to copy Magento instances so my plan is to rewrite this article. I’ll try to find time for it in next days, I promise.