nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Re-generate all of templated files

har

We have made a change to one of our include files and we now are looking for a way to re-generate all of our templated files(well over 1000 located in 40 diffrent workareas) on TS5.5.2. Has anyone done this? Have you encountered any problems? Thanks.

Find more posts tagged with

Comments

herald10

We have done something similar to this.. we didn't face any major problems.. with the exception of some small glitches like permission settings... Apart from that everything should work fine... You can write a perl script that browses to each directory with in a particular WA and regenerates all the templated files(those files that have EAs set on them)....

Edited by herald10 on 10/06/03 11:57 AM (server time).

Joost

We use a homemade script too. Works fine. At this time we are regenerating over 30000 pages. Just takes al LOT of time ;-)

Joost

waldemar

Indeed we encountered some problems generating a whole bunch of output pages. (Actually we use iwgen and not iwregen.) Two issues seemed to be the key to reliability:

1. For stability reasons our script generates a batch file containing all the iwgen commands
2. iwperl.exe seems buggy when called over the teamsite gui (probably a collision between the "wrapper"-cgi-environment and the actual generation iwperl.exe). Running the upper mentioned batch file directly from the shell solved the problem.

Migrateduser

But will you generate in the workareas (thereby potentially picking up changes to DCRs that have not been approved, or never even workflowed), or get latest into a temporary workarea and regenerate there, submit (for deploy/editions) and cause submit conflicts for every templated page that references the include?

Better would be to use dynamic includes, iw_include just causes problems like these.

IMG_0716N.jpg

waldemar

john, I guess this is why iwlock.exe provides an option -f (force 'get latest' before lock) that could be used prior to the actual (re)genereation...

waldemar
argo-tec

Migrateduser

I am not sure what you mean. You will be locking the DCRs (with -f to get latest) or skipping regeneration of files that have DCRs that are locked? If you get latest on the DCRs, wouldn't that override work in progress (which is possible even if the file is not locked)?

Another option would be to have your regeneration script generate from the DCRs in staging and submit only the output files, then regenerate based on the DCRs in the workarea and not submit.