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

No content in the Output file!

Jenni

Hi All,

Our TPL is generating a blank page with the below error in the iwutild.log. Any pointers?

Note that we moved the content store from 6.7.1 to 7.2.1 on 2008 VM 64 bit server. The same code works fine on 6.7.1.

[html]

concatenation (.) or string at

\iw-home\TeamSite\iw-perl\vendor\lib/TeamSite/PT/iw_perl.pm line 410.
Subroutine iwgethome redefined at

\iw-home\TeamSite\iw-perl\vendor\lib/Teamsite/Config.pm line 66.
Subroutine iwgetmount redefined at

\iw-home\TeamSite\iw-perl\vendor\lib/Teamsite/Config.pm line 86.
Subroutine iwgetlocation redefined at

\iw-home\TeamSite\iw-perl\vendor\lib/Teamsite/Config.pm line 115.
Subroutine hostname redefined at

\iw-home\TeamSite\iw-perl\vendor\lib/Teamsite/Config.pm line 149.
Useless use of a constant in void context at

/iw-home/TeamSite/iw-perl/lib/ecm/utils.pm line 804.
Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1404.
Unrecognized escape \M passed through at (eval 94) line 1404.
Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1406.
Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1407.

Could not load dcr: Y:\default\main\abc\WORKAREA\common/sy

[/html]

Find more posts tagged with

Comments

nipper

So what is the file that is supposed to be loaded ?

Is there a space in the name or is that the complete name ?

You very well may be having permissions issues like before.

Is that from a different branch/workarea ?

Jenni

Thanks for the reply Nipper.

We would specify the file name before the generation. eg. abc and the output is a JSP file.

There is no space in the file name that I specify.

I dont think it is a permission issue.

Different branch/workarea? yes we are having this issue in a new one. This is not in the branch/wa were I had the reference to JS files to other WA.

fobfobfob

(I am coming from a teamsite 5.5 world)

You can get better diagnostics by compiling the template and data record on the command line

IWHOME/TeamSite/iw-perl/biniwpt_compile.ipl -pt [template] -iw_pt-dcr [DCR]

If that is not enough

IWHOME/TeamSite/iw-perl/biniwpt_compile.ipl -pt [template] -iw_pt-dcr [DCR] -ocode foo.ipl will generate an executable file foo.ipl, which is also easier to diagnose

nipper

jen

I meant this:

Could not load dcr: Y:\default\main\abc\WORKAREA\common/sy

So either there is a regex gone wild (now that sounds like a geek movie if I ever heard of one), or a TPL issue. What should the full path be ?

FOB - running iwpt_compile on the command line (with -ocode) is still supported though of marginally less value now. Often it tells me the same thing I got from the logs.

nipper

Also some of your warnings in the TPL may be a concern. I would search for this string: testlogfp

Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1404.
Unrecognized escape \M passed through at (eval 94) line 1404.
Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1406.
Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1407.

fobfobfob

> Subroutine iwgethome redefined

This is a really weird thing.

In your PT, do you use a lot of custom Perl modules? Do any of them define a routine iwgethome and export it globally?

nipper

> Subroutine iwgethome redefined

This is a really weird thing.

In your PT, do you use a lot of custom Perl modules? Do any of them define a routine iwgethome and export it globally?

She does show at least 1 additional PM and I was assuming they redefine some IWOV modules (not a stellar approach).

Jenni

Sorry about the delayed response.

I am trying to execute the below cmd and I am not seeign any output getting generated.

[html]
iwpt_compile.ipl -pt art.tpl -iw_pt-dcr xyz.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ofile a.jsp
[/html]

The Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1406 issue has been taken care. The code was referencing a file that was not available.

Jenni

I even tried the below statement.

[html]

iwpt_compile.ipl -pt art.tpl -iw_pt-dcr xyz.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ocode foo.ipl
[/html]

Adam Stoller

Sorry about the delayed response.

I am trying to execute the below cmd and I am not seeign any output getting generated.

[html]
iwpt_compile.ipl -pt art.tpl -iw_pt-dcr xyz.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ofile a.jsp
[/html]

The Unquoted string "testlogfp" may clash with future reserved word at (eval 94) line 1406 issue has been taken care. The code was referencing a file that was not available.

The command, as shown is unlikely to work.
You would need to specify the path to the PT, DCR and output file.
While it is possible that you might have all three within he same directory - it is highly unlikely (PTs are usually in a 'presentation' directory, DCRs are usually in a 'data' directory, and output files are usually placed somewhere else - though for testing it is not uncommon to drop them in the current directory for expediency.

I would expect something like the following:

> cd Y:\default\main\abc\WORKAREA\common\category\datatype
> iwpt_compile.ipl -pt presentation\art.tpl -iw_pt-dcr data\xyz.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ofile a.jsp

If that's actually what you did - okay, if not, I suggest you try that first and see if it results in anything more than what you [haven't] seen thus far.

Jenni

Hi,

I tried the below statements. But still dont see any file that is generated.

[html]

> cd Y:\default\main\abc\WORKAREA\common\category\datatype
>iwpt_compile.ipl -pt presentation\art.tpl -iw_pt-dcr data\xyz.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ofile a.jsp
[/html]

Adam Stoller

Hi,

I tried the below statements. But still dont see any file that is generated.

[html]

> cd Y:\default\main\abc\WORKAREA\common\category\datatype
>iwpt_compile.ipl -pt presentation\art.tpl -iw_pt-dcr data\xyz.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ofile a.jsp
[/html]

I cannot tell from your posting whether you just copied/pasted the above verbatim or actually typed in the appropriate information (and recognized that the '>' at the beginning of the line was a shell prompt and not something to be literally typed in)

Please show us exactly what you typed in (you're allowed to use 'abc' and 'xyz.dcr' to obscure potentially confidential information), and then also show us the results of typing

dir

in the same directory after running the command.

Jenni

I did not type in '>'. Here are the list of commands I executed:

[html]

1. cd Y:\default\main\abc\WORKAREA\common\templatedata\Ins\art

2. iwpt_compile.ipl -pt presentation\art.tpl -iw_pt-dcr data\YYY.dcr -iw_include-location Y:/default/main/abc/WORKAREA/common -ofile a.jsp

3.
Y:\default\main\abc\WORKAREA\common\templatedata\Ins\art>dir
Volume in drive Y is IFS Volume
Volume Serial Number is E134-20030

Directory of Y:\default\main\abc\WORKAREA\common\templatedata\Ins\art

07/12/2011 09:39 AM

presentation03/02/2010 04:04 PM 13,593 superdct.js05/23/2011 09:18 AM 12,489 datacapture.cfg 2 File(s) 26,082 bytes 4 Dir(s) 274,912,284,672 bytes free[/html]

nipper

Some bad TPL developers will grab a parameter (say the ofile) and regex the workarea, etc from it.

That works when you use the GUI, because it feeds iwpt_compile the complete path, it will fail in this case because you do not include the path.

Try something like this:

iwpt_compile -pt Y:\default\main\abc\WORKAREA\common\templatedata\Ins\art\prestentation\...... etc

Often I start putting print statements in the TPL to start debugging.

You will likely need to do that, get a lot of coffee and plan to sit at your desk for a while.

You didn't have any plans this weekend, did you ? :-)

Jenni

Nipper,

You are reading my mind... The tpl is quite big with lots of logic involved.

I even tried to list the modules and punch in a truncated code into a perl script to test and it never reported any errors.

I did try specifying the entire path. Same result.

One point to note here is that the same code works in the previous version.

jagadesh

Some more points on debugging TPL, its not the resolution of your issue but it can try to narrow down the problem
Validate the TPL whether the tpl format is right or wrong just open in browser as xml file. If you are able to view properly it will be valid presentation file or else it has some thing wrong in code.

please confirm the DCR are not corrupted.

Validate all your variable declared and used in the TPL in a proper way.

Jenni

Thanks for the suggesstion.

1. The tpl is valid. I am able to produce the o/p with the same code on TS 6.7.1
2. The DCR is not corrupted. If I try to replace the tpl code to just grab a text field in the DCR, it works.
3. I cant be 100% sure. I did check the pm and a small portion of the code and it didnt report any error.

ISCBorisB

Thanks for the suggesstion.

1. The tpl is valid. I am able to produce the o/p with the same code on TS 6.7.1
2. The DCR is not corrupted. If I try to replace the tpl code to just grab a text field in the DCR, it works.
3. I cant be 100% sure. I did check the pm and a small portion of the code and it didnt report any error.

It *feels* that something has not been transitioned correctly to 7.2.1.

Very good chances are that this "something" belongs to you, not to TS.
It may be missing PM or standalone custom script that you include or execute directly.
It can be missing DB (or some other) required Drivers like Oracle.
It can be missing or incorrect custom configurations or Environment variables - anything.

You'd have to identify the trouble maker. Purge template. Start with an absolute minimum. Make sure it works.
Add a little. Make sure it works. Continue adding - you've got the gist... Sooner or later
(I suspect sooner) you'll hit a template fragment that bombs out. That'll give you a good idea
where to start troubleshooting outside of template.

Adam Stoller

I did not type in '>'. Here are the list of commands I executed:
...

Thanks for clarifying that - it's sometimes difficult to tell what people are actually doing.

Based on this and all the subsequent responses - I think I'd go with Boris' suggestion

be able to help you - but we'll need to see the offending code and any other code that it references...

Jenni

Looks like there is some restriction such that we would be able to generate the file only via a workflow!!

Thanks for your contribution.

nipper

Looks like there is some restriction such that we would be able to generate the file only via a workflow!!

Thanks for your contribution.

OK, so the the workflow invokes iwpt_compile with a command line parameter that you should try to figure out (and then you can run it stand alone)