After Upgrading, What Can I delete?
Permalink 1 user found helpful
This is the first time I've upgraded a C5 site. Now that I've upgraded to 5.4.0.5, the whole new site seems to be in the updates file and my overall site file has doubled to 83mb. To speed up my upload time from my localhost and simply get rid of what is not needed, can I delete all the old files below the root (except updates), take the new version and its files out of updates>concrete 5.4.0.5>"all the files" and put them in the root folder? (in the structure of the old site) or would that create a mess with the links and database?
I know this is old, but I have the same question. I have one site with 5.4.0.5, 5.4.1 and 5.4.1.1 in the updates folder. Can I trash them all?
Once you've updated, C5 will add a line to your site.php file telling it which core to use. So if you want to trash everything in the Updates folder, you must first copy the latest version over your existing concrete folder and then delete the line from your site.php. Old versions in your updates folder are always safe to delete - just be careful with the latest one as it is in use!
Jon
Jon
I have an add-on question to this...here is my scenario:
-I am running on an intranet where I cannot access the Internet spell checking
-So, I switch the spell checker in the /concrete/js..... directory to use a local spell checker
-upon updating, that is no longer in use because it is no longer using /concrete but now /updates/concrete.5.x.x.x
...are all of those changes no longer in effect? It seems so! If the update just overwrite the files it needed to change then that would be great...but it would make rollbacks harder to do, obviously.
I guess, now that I think about it, my site is one that would qualify for the "overwrite /concrete" installation method, rather than the "use the /updates directory" method....is that the only way to preserve my changes from upgrade to upgrade?
Thanks!
-I am running on an intranet where I cannot access the Internet spell checking
-So, I switch the spell checker in the /concrete/js..... directory to use a local spell checker
-upon updating, that is no longer in use because it is no longer using /concrete but now /updates/concrete.5.x.x.x
...are all of those changes no longer in effect? It seems so! If the update just overwrite the files it needed to change then that would be great...but it would make rollbacks harder to do, obviously.
I guess, now that I think about it, my site is one that would qualify for the "overwrite /concrete" installation method, rather than the "use the /updates directory" method....is that the only way to preserve my changes from upgrade to upgrade?
Thanks!
I know this is a bit old but I thought I would throw my thoughts in here. I have had issues with using the upgrade folder and as a result I have for the most part done my upgrades manually. The best way I have found to do this and have the ability to roll back if anything arises in the process is to maintain the old and new core folders... writing over the old core leaves you without a quick fix if anything goes wrong. Name the new core concreteN and upload (without overwriting) and, back up the db, name the old one concreteO (or whatever) and then rename the new core as just concrete. This way if something happens during upgrade then you can just reverse the process to go back to the original core and you have the db backup if that is needed as well. If everything runs as it should after all is said and done then you can delete the old core.
and pendragn... i'm no guru in c5 but I have extensive talents in messing it up... mostly when messing with the core. after many such episodes i came believe in the c5 motto... never mess with the core.
and pendragn... i'm no guru in c5 but I have extensive talents in messing it up... mostly when messing with the core. after many such episodes i came believe in the c5 motto... never mess with the core.
