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

[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]

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.

[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.