Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Populate changes based on last edition
jojosan
Hi,
I need to make some changes to one of the created presentation template and populate the changes.
Making changes to the presentation template is quite straight forward but how do I propagate changes to generated html files in the production?
One problem is the generated html files in the workarea or DCRs may not be identical to the production even though they may be bearing the same file names as changes been made since the last submission.
By right I should re-generate the html files based on the last edition created so as to ensure I do not populate immature files to production but the problem is that DCRs were not included in previous edition.
Does anyone has a solution to overcome these problems and is there some generic procedures/processes to follow in propagating changes to generated html files? Tks.
Jo
Find more posts tagged with
Comments
Adam Stoller
Make sure your DCTs, DCRs, and PTs are versioned in TeamSite - it is pretty easy to ensure they don't get deployed to your website if you don't want them to, so there's no reason not to version them (and, as you've discovered, may reasons to do so).
Without having the above, it is pretty muc impossible to regenerate pages from DCRs based on an older version of a PT - because you don't have it.
If you're trying to re-generate pages from pre-existing DCRs using a new PT - you're faced with the same problem if the DCRs were not versioned.
If the DCRs were versioned but you wish to generate pages from them using a *new* PT - you can use the command line tools iwgen and/or iwpt_compile.ipl - which allow you to specify a vpath / file system path (respectively) to a PT to use for processing the DCR.
Not sure if I answered your question - but please - make sure you start versioning these assets as soon as possible - they are, in essence, the *source* of your website and as such should always be versioned.
--fish
(Interwoven Senior Technical Consultant)