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 pages

TeamSite_Smasher

Is there a way to re-generate all pages within TS?

We are going to make some layout changes which will affect all files.

Which will then require them to all be re-genearated and re-submitted...

is there any easy way to do this?

script? or automated process?

TS6.7.1
W2k3 servers

Find more posts tagged with

Comments

Evani20

To me the easiest way to do this, by writing a script which will go through the entire directory and create a filelist along with the filepath. Then create a batch file which will re-generate all the files listed in the filelist.

nipper

There is the easy way and there is the right way.

Either way you will write a script to do it.

You can find all .html (or what ever type of file you generate) and run iwregen on each. That may not give the expected results in all cases but works out pretty well. Sometimes parameters may be needed for iw_ostream or other functions that will not be provided by iwregen

The correct way is to traverse the templatedata folder, get a DCR, calulate the generated file name and PT and then run iwpt_compile.

Then submit all generated pages.

After that, write a new step to your workflow that will generate the output of a DCR that was submitted and include it. The next time you need to do this, submit the DCRs and go have lunch. If you write script #2, that will become the basis for the new external task.

Adam Stoller

There is the easy way and there is the right way.

Either way you will write a script to do it.

You can find all .html (or what ever type of file you generate) and run iwregen on each. That may not give the expected results in all cases but works out pretty well. Sometimes parameters may be needed for iw_ostream or other functions that will not be provided by iwregen

The correct way is to traverse the templatedata folder, get a DCR, calulate the generated file name and PT and then run iwpt_compile.

Then submit all generated pages.

After that, write a new step to your workflow that will generate the output of a DCR that was submitted and include it. The next time you need to do this, submit the DCRs and go have lunch. If you write script #2, that will become the basis for the new external task.

The "correct" way assumes that there is a pre-ordained (also "correct") logic behind the relationship of the name and path of the DCR and its associated output file. If you let your users randomly name DCRs and output files - you pretty much have to use the first method described.

However, the first method suffers if the process used to generate the pages was customized, and uses iwpt_compile.ipl without setting the EAs on the output file. If this is the case - and you don't have a "correct" relationship between DCR and output file - you're pretty much SOL.

nipper

The "correct" way assumes that there is a pre-ordained (also "correct") logic behind the relationship of the name and path of the DCR and its associated output file. If you let your users randomly name DCRs and output files - you pretty much have to use the first method described.

However, the first method suffers if the process used to generate the pages was customized, and uses iwpt_compile.ipl without setting the EAs on the output file. If this is the case - and you don't have a "correct" relationship between DCR and output file - you're pretty much SOL.

True, that is why the last option (do it in workflow) is the best. If people randomly name output files, he is hosed.

I did forget to mention if #2 or WF is the choice, then you need to attach the TST EAs on the files. Ot you will be in a world of hurt.

Evani20

Yes, I forgot to ask about the EA before I release the method. Both of you are absolutely right.