Folder dilemma - original store in root, new upgraded shop in subfolde

[RoPey]

Hi
So I'm in the last stages of my upgrade and I have my upgraded shop in a subdirectory on the live server having the finishing touches put to it. The live store is in the root directory of the site. Can anyone advise me on whether I should keep my new store in the subdirectory and just remove the old store or whether I should remove the existing store files and put the new store into the root?

If I keep it in a subdirectory, how does someone visiting http://www.mystore.com/ get sent to http://www.mystore.com/subdirectory? Do I have to use htaccess?

Thanks

[gilby]

Hi
So I'm in the last stages of my upgrade and I have my upgraded shop in a subdirectory on the live server having the finishing touches put to it. The live store is in the root directory of the site. Can anyone advise me on whether I should keep my new store in the subdirectory and just remove the old store or whether I should remove the existing store files and put the new store into the root?

If I keep it in a subdirectory, how does someone visiting http://www.mystore.com/ get sent to http://www.mystore.com/subdirectory? Do I have to use htaccess?

Thanks

First I would backup both file systems....
Move the old file system from the root to a (different) subdirectory
Then move the new filesystem into the root

Keep the old files in the subdirectory until you are sure the new file system in the root works.

This of course assumes that the new file system has a complete working up to date database
If not you would have to copy the old database to the new and then run zc_install to upgrade the database
or
you edit the 2 new configure.php files to point to the old database and also run zc_install to upgrade.

[RoPey]

Thank you Gilby, that was what I thought was probably best.

The new store has already got an upgraded version of the database and the current store is offline while we upgrade so that there are no changes.

[DrByte]

This is worth a read, to make things simpler for you: http://www.zen-cart.com/entry.php?3-...d-of-upgrading

[DivaVocals]

and to add to this.. I would KEEP the test shop in place post upgrade so that you can use it as a place to stage/test new add-on installs and future upgrades..

[RoPey]

and to add to this.. I would KEEP the test shop in place post upgrade so that you can use it as a place to stage/test new add-on installs and future upgrades..

Excellent advice DivaVocals and also thanks to Dr Byte for the link. I'm delighted to say that the transition went smoothly and I have left the sub folder in place, password protected and disallowed to search engines. One question though - is there any reason why I should not leave it attached to the live database?

Thanks again for all the good advice

[RodG]

This is worth a read, to make things simpler for you: http://www.zen-cart.com/entry.php?3-...d-of-upgrading

Nice blog entry, pretty much identical to my own upgrade technique.

I loved the tip:
TIP: You *could* do a "trial run" of this whole upgrade process by making ANOTHER copy of your live site and doing
this upgrade to that site. Then you'll have either a checklist of additional things you'd missed, or you'll have simply the peace-of-mind of knowing that your live upgrade will go smoothly.
In fact, this is what I always do!

How come it only seems to be developers that make backups of backups of backups? :)

Noobs are so innocently trusting aren't they ;)

Cheers
Rod.

[RodG]

Excellent advice DivaVocals and also thanks to Dr Byte for the link. I'm delighted to say that the transition went smoothly and I have left the sub folder in place, password protected and disallowed to search engines. One question though - is there any reason why I should not leave it attached to the live database?

Yes. If you use this site for further testing/development you DON'T want it connected to your live database.

Cheers
Rod

[DivaVocals]

Excellent advice DivaVocals and also thanks to Dr Byte for the link. I'm delighted to say that the transition went smoothly and I have left the sub folder in place, password protected and disallowed to search engines. One question though - is there any reason why I should not leave it attached to the live database?

Thanks again for all the good advice

Yes. If you use this site for further testing/development you DON'T want it connected to your live database.

Cheers
Rod

Took the words RIGHT out of my mouth Rod!!!

and the reason is this, some add-ons include SQL files which modify the DB. The purpose of a dev/staging site is to TEST upgrades, modifications, etc BEFORE "going live". So you want these changes to take place in it's OWN database before moving these DB changes to your live site.. and as Rod has said you need to backup your test site (files AND the DB) before applying changes to it so that you can roll back when things go horribly wrong..

[RoPey]

Fair enough - hadn't really thought that through when I typed it. Don't worry about the backing up. When I upgrade anything I have a checklist next to me. It is liberally interspersed with - backup again, backup again, backup again.

Thanks again to all.