Developing and deploying sweeping changes for an existing Umbraco site
I need to make massive changes (macros, doctypes, content additions and modifications) to an existing site. To do this for content nodes is quite easy. Just reseed some tables. ie:
I am currently rebranding one of my Umbraco sites. I have created alternative templates for each of the templates required. For most of the pages I can leave the doctypes and macros as they are and just restyle using CSS (as the functionality isn't changing much - just the look). Any new macros can be created as required by the new design and as long as you're not deleting/editing existing data type properties there shouldn't be a problem adding new properties.
When the time comes I will be able to flick over to the new templates. As there are only a couple of macro and datatype changes I will perform them manually on the live server whent he time comes.
That is entirely what I'm trying to avoid. As a developer, my first goal is to do as little manual work as possible :)
Automate or make mistakes!!!
I need to do a hell of a lot of additions and deletions in doc type properties, some macros will go from xslt to .net, some datatypes will be introduced (some removed), new content (while migrating the client's content)....the whole shabang!
Correct. If you're doing sweeping changes you don't want anything that's automated to that extent.
What's wrong with the package engine, it can pack up doc types, data types, macros, templates, etc. Sure it doesn't do deleted but i wouldn't want to install anything into a CMS that automatically deleted stuff
Developing and deploying sweeping changes for an existing Umbraco site
I need to make massive changes (macros, doctypes, content additions and modifications) to an existing site. To do this for content nodes is quite easy. Just reseed some tables. ie:
http://www.farmcode.org/post/2009/09/09/How-to-sync-data-across-multiple-Umbraco-environments.aspx
I'm just wondering if anyone has tried this with macros, doctypes etc?
As you know that above solution didn't really work that well.
Courier 2 should solve many of those problems too, otherwise there's the packaging engine.
Anthony,
I am currently rebranding one of my Umbraco sites. I have created alternative templates for each of the templates required. For most of the pages I can leave the doctypes and macros as they are and just restyle using CSS (as the functionality isn't changing much - just the look). Any new macros can be created as required by the new design and as long as you're not deleting/editing existing data type properties there shouldn't be a problem adding new properties.
When the time comes I will be able to flick over to the new templates. As there are only a couple of macro and datatype changes I will perform them manually on the live server whent he time comes.
Cheers
Paul
Hey Aaron
Yes I remember that situation. The cmsPropertyData table was not indexed high enough.
In my case it's currently at 300,000 in only 2 months. So I in my case I reseeded to 10,000,000.
Was there something else that we missed at the farm? Data corruption?
Would you not go down this path again?
Hey Paul
That is entirely what I'm trying to avoid. As a developer, my first goal is to do as little manual work as possible :)
Automate or make mistakes!!!
I need to do a hell of a lot of additions and deletions in doc type properties, some macros will go from xslt to .net, some datatypes will be introduced (some removed), new content (while migrating the client's content)....the whole shabang!
CSS is the least of my worries :(
Correct. If you're doing sweeping changes you don't want anything that's automated to that extent.
What's wrong with the package engine, it can pack up doc types, data types, macros, templates, etc. Sure it doesn't do deleted but i wouldn't want to install anything into a CMS that automatically deleted stuff
is working on a reply...