question about going live with new version

ok finally after about 3 weeks of tweaking my 1.3.8a version of dev server, I am about ready to go live....

I have a few questions to make sure I don't mess anything up....

so once I am ready - run a backup, then....

1. put old cart in disable mode
2. export old db
3. run upgrade db from zcinstall on new site
4. (not sure about this) copy all files/folders in new site and drop into our root folder
5. change config settings
6. re-enable via admin

is this all right? or am I missing anything? like any files that I have to change the permissions to make sure the new files will overwrite correctly?

Thanks a million...

BTW - I am now a ZC monthly donater because you guys are the BEST!

anybody? any suggestions?

can anyone tell me if this is right?

:( can someone please confirm this for me?

anyone out there?

boo! :eek:

Almost right ...

1. put old cart in disable mode

<insert here>
Backup old site before moving anything ...

2. export old db

<insert here>
IMPORT OLD DATABASE to NEW DATABASE
It is well worth while to make a NEW database for the NEW site and load a copy of your backup of the OLD database ... so, if you totally screw up ... you can compare what went wrong in a much easier manner ...

3. run upgrade db from zcinstall on new site
4. (not sure about this) copy all files/folders in new site and drop into our root folder

<insert here>
Move all of the OLD SITE to /old_site before moving all of the NEW SITE to the root ... or if you use subdirectories ... rename the /catalog (or what have you) to /old_site and rename the NEW site (example: /new_shop) to /catalog (or what have you)

5. change config settings

<insert here>
test ... test ... test ...
if all is working from create account to ordering to email etc. etc. etc. then you are good to go ...

NOTE: some payment and shipping modules may not work when set to Down for Maintenance ...

6. re-enable via admin

ok, about to do this... but 1 question...

if I export old db, import old one, then run uppdate db in zcinstall... but I have added lots of mods and added sql from them into the new site, if I import the old db, won't it be missing the new sql stuff for the new mods? or do I just import old db, run update db and then do I have to install the sql for the new mods?

thanks,

Eric

All of the add-ons are on your OLD database?

By exporting it then importing it you will be Upgrading it ...

If, however, you have all of the add-ons already on your new database, you will need to add those sql files that may have come with the add-on or update the setting etc.

Perhaps listing the add-ons that you have will prompt others to chime in and let you know of their experiences ...

Usually the differences are in the configuration and configuration_group tables ... with differences in the layout_boxes table to match any changes you made with your template ...

If you built your template yourself then this should not be horrible ...

I would recommend making a 3rd, truely NEW database to start with for your new Live site and import your OLD Live database into it then compare it to your existing database ...

sorry, I think you misunderstood me... the mods are on the NEW site and DB.... so I think if I overwrite the new with the old one, then reinstall the sql statements from the new mods it should be good.... what do you think? thanks

That is what I was telling you to do ... so we are on the same page ... :smile:

Just be sure to backup everything ... you can always recover with a good backup ...

ok, did it all but having a slight glitch...

page loads from here with new site... http://midwestapplianceparts.com/index.php?main_page=down_for_maintenance

but... from the main site:
http://midwestapplianceparts.com/

it is getting a 404 and saying:
The requested URL /midtest/index.php was not found on this server.

midtest was our development folder.... it should not be looking in there... the config files are all straight... any ideas?

Were you able to fix this?

It appears to be working now ... :smile:

yes, it was something in the .htaccess