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; } } }

regeneration

Amanda_J_0204

Using Teamsite 6.7.2 on Windows 2003

We are trying to find a way to regenerate all templates within a workarea. I've heard of scripts that are supposed to locate all files and regenerate them; however, I'm somewhat new to coding for Teamsite. It also may be beneficial to give the user the ability to select which pages they want to regenerate.

So I tried selecting all possible files in the particular workarea that would need to be regenerated, and went to Actions -> Regenerate Page. This regenerated all but three pages. The pages that didn't regenerate were originally generated by templates that use iw_ostream to output more than one file, and all three files are not the main file one sees on generation. They do not have any EA's applied to them.

My main question is: how do you set EA's for files that were generated by iw_ostream? Unfortunately, I'm still a bit new to Teamsite; I appologize if this is a(n) RTFM.

Find more posts tagged with

Comments

Crsb

you just need to run iwextattr once the file is regenerated.
see iwextattr command syntax in documentation or iwhome/bin/iwextattr --help.

Amanda_J_0204

you just need to run iwextattr once the file is regenerated.
see iwextattr command syntax in documentation or iwhome/bin/iwextattr --help.

Thanks.. We'll need to run this for a lot of files... Is there a way for this to somehow be built into the .tpl?

nipper

Thanks.. We'll need to run this for a lot of files... Is there a way for this to somehow be built into the .tpl?

By default it is done when you generate UNLESS the output was generated with iwpt_compile or if it is a secondary output using ostream

Adam Stoller

Thanks.. We'll need to run this for a lot of files... Is there a way for this to somehow be built into the .tpl?

In the past (I've seen some posts indicating it might not be true anymore) you could code the running of iwextattr into the PT itself so that your files get marked correctly automatically.

I'd try that before doing anything more exhaustive in terms of writing scripts to traverse the files.

Amanda_J_0204

By default it is done when you generate UNLESS the output was generated with iwpt_compile or if it is a secondary output using ostream

That's the problem - the files are secondary ostream outputs.

I'll try putting the iwextattr in the tpl...

Amanda_J_0204

In the past (I've seen some posts indicating it might not be true anymore) you could code the running of iwextattr into the PT itself so that your files get marked correctly automatically.

I'd try that before doing anything more exhaustive in terms of writing scripts to traverse the files.

I included the iwexattr in the tpl, resaved and generated the file, and then regenerated from the .html file in htdocs and it worked just fine.

Thanks for your help.

Amanda_J_0204

Turns out that when a user goes to regenerate an ostream file, it now regenerates - BUT it regenerates from the part of the tpl that creates the primary output file - NOT the part of the tpl that originaly created the ostream file. This is bad because the ostream file output is formatted differently and needs to contain more info that the primary output. Is there a way to force generation from the ostream section in the tpl?

Crsb

Turns out that when a user goes to regenerate an ostream file, it now regenerates - BUT it regenerates from the part of the tpl that creates the primary output file - NOT the part of the tpl that originaly created the ostream file. This is bad because the ostream file output is formatted differently and needs to contain more info that the primary output. Is there a way to force generation from the ostream section in the tpl?

there are many ways you can handle this:
- you could add more logic in your PT to only execute certain code for certain DCRs/output files and not others, this means that you will need a way to distinguish between files being regenerated or source DCRs.
- you could break down your PT into multiple PTs, with one primary that generates in first run and others secondary to be used when regenerating the ostream files. this will require to set primary PT EA of the ostream files to one of the secondary PTs...
Those are some ideas, but as i said, they are many ways you could handle this. i can't say which would be best for your since i dont' know very much about your setup (DCR structure, PT code, generation process....)

nipper

You never regenerate the osteamed out file
Only regenerate the file original file

That is why putting all the EAs on the ostream created file isnot done (typically)

Amanda_J_0204

there are many ways you can handle this:
- you could add more logic in your PT to only execute certain code for certain DCRs/output files and not others, this means that you will need a way to distinguish between files being regenerated or source DCRs.
- you could break down your PT into multiple PTs, with one primary that generates in first run and others secondary to be used when regenerating the ostream files. this will require to set primary PT EA of the ostream files to one of the secondary PTs...
Those are some ideas, but as i said, they are many ways you could handle this. i can't say which would be best for your since i dont' know very much about your setup (DCR structure, PT code, generation process....)

Trying to get the ostream file to regenerate from a separate tpl - when it's regenerated from under htdocs. Keep getting "ERROR com.interwoven.ui.formspub.RegenerateCommand () - An error occured trying to create a PT Compiler for path/toMyTemplate/template.tpl" in servletd_out. Not a very specific error. Will try to simplify the second tpl more.

Crsb

you might want to post as much as you can from servlet_out.log, you probably have syntax error in your code.

Amanda_J_0204

you might want to post as much as you can from servlet_out.log, you probably have syntax error in your code.

This is all that displays in servletd_out.log:

2010-01-21 09:15:26,339 [http-8080-9] ERROR com.interwoven.ui.formspub.RegenerateCommand () - An error occured trying to create a PT Compiler for portal/clubs-organizations/clubs-organizations-full.tpl

The tpl that I wanted to use for just regnerating the ostream file is located under templatedata/portal/clubs-organizations/presentation/ The path above has the right tpl name, but misses the presentation folder.

When a DCR is initally saved and generated, the EA is set for the ostream file (Full_Clubs.html), so it looks like this if I view the properties: TeamSite/Templating/PrimaryPT: clubs-organizations-full.tpl

For the sake of trying something different, I tried changing the EA for clubs-organizations-full.tpl so that it is:
TeamSite/Templating/PrimaryPT: presentation/clubs-organizations-full.tpl

Now, when I try to regenerate, I'm still seeing the "Unable to Generate Page(s)" and "Full_Clubs.html
Folder: /htdocs/arlington/portal
Comment: Presentation template used to generate this page is not available", but no error is being posted in servletd_out.log.

Amanda_J_0204

At the moment, I've given up on trying to regenerate from a second tpl because 1. if I select both files that are generated by the same DCR and go to Actions - Regenerate file, both regenerate fine (for me at least...), and 2. When I tried to regenerate the ostream file from the second tpl, the error message was not descriptive, and the log files didn't point out what specifically broke. (see my previous post)

However, if a user who is not a Teamsite master goes to regenerate both files that were generated by the same dcr, it generates the ostream file from the wrong part of the tpl - it's missing content and formatting. The user has the appropriate permissions to use the template and can generate normally from it - it's just not letting them regenerate files correctly. I tried looking through the permissions associated with this user's role - there's nothing specifically controlling regeneration. Has anyone run into a problem like this, and were you able to resolve it?

nipper

Read my previous post if you want the answer. There is a reason TS does not put EAs on the ostream generated file. Regenerating an ostream generating file is a BAD IDEA. Regenerate teh main file and the others will get generated as well.

Amanda_J_0204

Read my previous post if you want the answer. There is a reason TS does not put EAs on the ostream generated file. Regenerating an ostream generating file is a BAD IDEA. Regenerate teh main file and the others will get generated as well.

nipper, why is this a bad idea? I can ask the user to generate the three templates the ordinary way for 47 separate branches (there are plans to simplify this in the future), but at the moment, being able to regenerate everything from under htdocs would save some time.

nipper

It is because that is the way the product was built.

TPLs generate a primary object and optional secondary objects. If you tell TS to regen a secondary object, things will get hosed.

So change you use case.

Or

I am not saying your approach is valid, I am skeptical. However, if I were told that it must work this way (TPL generates 5 objects) and I must be able to regenerate all 5 correctly when I click regen on any of the 5, I would write a very complex TPL.

Basically, I would build 5 iw_includes that can be called independently (with proper parameters).

My TPL would start as an iw_case, figure out which was the selected object (basically primary), call the iw_include for that object and call 4 other ostreams for the other 4 objects. You would have 5 different selections for the iw_case, each with a different primary.

This will not work for preview (or at least probably not) because figuring primary would be difficult or impossible.

Like I said, this can be done, hwoever I really wonder about your true requirements. Also you will be leaving something that will be hard to maintain.

nraval

Assuming that you want regenerate all DCR/form

Can you get list of all workareas/files that needs to be regenerate and

iterate in loop run iwregen.exe for each file and submit each file (iwsubmit )

Does it make sense ?

Amanda_J_0204

However, if a user who is not a Teamsite master goes to regenerate both files that were generated by the same dcr, it generates the ostream file from the wrong part of the tpl - it's missing content and formatting. The user has the appropriate permissions to use the template and can generate normally from it - it's just not letting them regenerate files correctly. I tried looking through the permissions associated with this user's role - there's nothing specifically controlling regeneration. Has anyone run into a problem like this, and were you able to resolve it?

The problem above was an IE/Firefox issue. Different EAs were being set depending on which browser was being used. Since there is only one person trying to batch regenerate at the moment, I'm thinking they should just use IE for now.