how to know what tpl(s) generated the certain pages and from what dcr(s)

hi ,

we have a lot of pages (.aspx) which we need to know what tpl(s) has created them and from which dcr(s) the content came from . the Editors are not sure ( strange but true Smiley Sad

) and the developers who created these dcts left with no trace of documentation.

is there a way to extract lets say some sort of EA that explains what dcr(s) and tpl(s) created those aspx pages.???

by the way special thanks to ISCboris and nipper for your valuable help .

Find more posts tagged with

Comments

nipper

Do a view properties on the file in question.

You will see

TeamSite/Templating/PrimaryDCR: foo.xml
TeamSite/Templating/PrimaryDocumentType: Category/Type
TeamSite/Templating/PrimaryPT: foo.tpl

That being said, IF these files are done in workflow (say you submit a DCR and it generates the appropriate output files) that script needs to attach the EAs

brvhrt

Thanks andy,

i will create a perl script that goes through each workarea and extract all the EA for those pages then throw them in an excel sheet.

Adam Stoller

Do a view properties on the file in question.

You will see

TeamSite/Templating/PrimaryDCR: foo.xml
TeamSite/Templating/PrimaryDocumentType: Category/Type
TeamSite/Templating/PrimaryPT: foo.tpl

That being said, IF these files are done in workflow (say you submit a DCR and it generates the appropriate output files) that script needs to attach the EAs

To be more accurate - if you use iwpt_compile.ipl to generate pages or use iw_ostream (or Perl I/O) within your PTs - you need to make sure that the PTs (or calling scripts) correctly set the EAs on the generated files.

If you use iwgen and do not use iw_ostream in your PTs - the EAs should already be set for you.

brvhrt

To be more accurate - if you use iwpt_compile.ipl to generate pages or use iw_ostream (or Perl I/O) within your PTs - you need to make sure that the PTs (or calling scripts) correctly set the EAs on the generated files.

If you use iwgen and do not use iw_ostream in your PTs - the EAs should already be set for you.

adam,

thanks for the information you provided. i actually already created the script and it went through most of the workareas and give me the pages and their EAs.

i didnt know that when using iw_ostream the EAs are not set. ( good note ). does that happen in all cases or it depends in the way it is used. if you could elaborate more would be great.

Smiley Happy

Adam Stoller

adam,

thanks for the information you provided. i actually already created the script and it went through most of the workareas and give me the pages and their EAs.

i didnt know that when using iw_ostream the EAs are not set. ( good note ). does that happen in all cases or it depends in the way it is used. if you could elaborate more would be great.

When using iwgen - the only file that gets EAs set on it automatically is the one that is named on the command line for the output file. Any additional files created by way of iw_ostream do not get EAs set on them automatically.

When using iwpt_compile.ipl - no files get EAs automatically.

brvhrt

Thanks Adam for this valuable information. keep the good work Smiley Wink