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

iwregen/gen/pt_compile does not produce correct output using Perl PT in 6.7.1 SP1

Bill Klish

TeamSite 6.7.1 SP1
Windows 2003 EE SP1

Attempting to run iwpt_compile.ipl, iwgen or iwregen at the command line or in the UI is not producing correct output. The PT and DCR used to produce the correct output prior to SP1, but any references to dcr.Fieldname doesn't work. The content is just empty for those iw_value references.

No error is written back out, the HTML output appears, but when run through a simple perl program, the iwregen command returns code 1280.

templating.cfg exerpt:
[html]

[/html]
I also set the following at the top of the file and ran iwreset -a:
[html]

[/html]

Is there something else that needs to be set to have this stuff work in SP1? I don't see any upgrade/migration information in the SP1 release notes.

Find more posts tagged with

Comments

moonkhanna

Hi Bill,

I have been following up on most of the SP1 issues and no issue were reported similar to yours so I would think, there is some problem with your environment.

Just to have a clarification - Does the generate\ regenerate work when you do using the GUI and does not work when you try to generate using a perl program?

Bill Klish

It says successful in the GUI, but the dcr field values are not extracted and inserted into the resulting pages.

moonkhanna

Bill, Can you please paste your PT Code to the post.. The only reason your DCR values are not displayed is when PT is not able to read the right XPath for your DCR and that does not display an error message as well..

I feel there is some issue with how you are referencing the DCR
values in the PT

moonkhanna

also, please paste your DCT

Bill Klish

Perhaps it was lost in my first post.

The PT and DCR work fine before we installed 6.7.1 SP1. We have not changed the PT or DCR since the upgrade.

The DCT is very simple with 2 fields, one called Title, one called Body.

In the PT I have iw_value tags with name = dcr.Body and name=dcr.Title, both of which show no information.

Is there some sort of server configuration update that is needed?

nipper

I have my original templates working on SP1 without the ptcompiler setting. When I put it in, the preview never popped up.

moonkhanna

Not any Server Config, I am aware of..

ISCBorisB

Perhaps it was lost in my first post.

The PT and DCR work fine before we installed 6.7.1 SP1. We have not changed the PT or DCR since the upgrade.

The DCT is very simple with 2 fields, one called Title, one called Body.

In the PT I have iw_value tags with name = dcr.Body and name=dcr.Title, both of which show no information.

Is there some sort of server configuration update that is needed?

Check Fixing a HOPI Error

Bill Klish

I looked at that support article earlier today. It did not provide anything useful, as none of the errors identified in there are showing up.

Interestingly, I hacked around a little bit and I see that the regenerate page command in the UI is calling iwpt_compile.ipl and not iwregen. Inside of forms publisher it is also calling iwpt_compile.ipl. Changing my code to also call iwpt_compile.ipl instead also works for me.

Running iwregen at the command line does not work and it was being called in an external task in my workflow. Running iwgen at the command line does not work either. Replacing both of these with iwpt_compile.ipl does in fact work.

Should we abandon these CLTs? I don't see anything in the manuals stating that they no longer work.

nipper

Like I said mine work fine without the ptcompiler in the templating.cfg.

I use both preview and in my WF I run iwpt_compile

I am on Win2K 6.7.1 SP1

Bill Klish

Ok. iwpt_compile is not the problem. iwregen and iwgen are. Are you using either of those?

nipper

From the GUI regenerate file works, but I am not certain if iwregen is working or not, it was acting a bit strange.

will test some more

moonkhanna

I looked at that support article earlier today. It did not provide anything useful, as none of the errors identified in there are showing up.

Interestingly, I hacked around a little bit and I see that the regenerate page command in the UI is calling iwpt_compile.ipl and not iwregen. Inside of forms publisher it is also calling iwpt_compile.ipl. Changing my code to also call iwpt_compile.ipl instead also works for me.

Running iwregen at the command line does not work and it was being called in an external task in my workflow. Running iwgen at the command line does not work either. Replacing both of these with iwpt_compile.ipl does in fact work.

Should we abandon these CLTs? I don't see anything in the manuals stating that they no longer work.

Adam Stoller

Just in case it wasn't clear what Nipper was suggesting (I believe) - you have:

<data-type name="generic" dcr-type="iwov">
  <presentation>
    <template name="generic.tpl" extension="shtml" ptcompiler="com.interwoven.ui.formspub.utils.PerlPTCompiler">
      ...
    </template>
  </presentation>
</data-type>

Have you tried removing that attribute, letting FormsPublisher use whatever it's internal default is - and see if that works with iwgen and iwregen?

If so - the bug is in that particular setting - which I believe was created so that it could be set to use an XSLT compiler for folks using non-OS users - and the PerlPTCompiler option may be "for completeness", but may be broken.