Trustmaster |
|
---|---|
That's quite a tedious path you follow every time :) It might be fine for a one-off action like Genoa2Siena migration, but there's no need to do it with regular updates. First, let's repeat the rule #1: don't copy entire database and datas from localhost to production, it breaks things. Apart from that login issue, you loose all the data that has been added by users on the production site from the period you made a dump of it for your localhost. Then, let's make it clear that there are different kinds of updates that you make to the production site:
Now comes the rule #2: these kinds are handled differently. Cotonti updates These are described here. Shortly, after downloading another cotonti update, just overwrite the old files and run install.php to update the database. I apply the same procedure to localhost first and if it is fine, I apply the same procedure to the production site (without copying stuff to localhost and back again). Theme updates Edit and test on localhost, then upload to production. Extension updates This gonna be the trickiest part. If you add new functions to your site and want to make them work on localhost first, then:
This is it. Content updates OK, here comes the rule #3: don't use localhost to update production site's contents. Really, use localhost to play with extensions and templates, but contents should be edited on the production site directly. Use Drafts, Validation queue and Permissions to hide stuff from visitors' eyes unless you want them to see it. Ah, and the rule #4: make backups of the production site from times to times. Just in case it all goes absolutely wrong one day. May the Source be with you!
|