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

use of uninitialized value

Ottawa_IWOV

I am running iwgen from the command line and I am receving the following error:

use of uninitialized value at (eval 32) line 338.

I then debug the template file using the -ocode flag...

then I run the outplut ipl with -d Smiley Tongue

tkdb and look at line 338, but there does not seem to be much wrong with the file...

does anybody have any ideas on this.

BTW, the file is still generated, but I want avoid that error message...

Thanks.

Lucas Cochrane
lcochrane@dc.com

Find more posts tagged with

Comments

LooseCannon

That's just a warning not an error. Your sha-bang probably has the warning switch turned on, like:

#!/p01/app/iw-home/iw-perl/bin/iwperl -w

P.S. It's good practice to always execute perl with the warning switch on.

Ottawa_IWOV

Thanks for the good call on that one LooseCannon....

I am also running into problems when I run a .tpl through the iwpt_compile.ipl script. I am getting something that looks like this....

<ERROR source='Teamsite: Smiley Tongue

T::iw_include'>
element syntax:<iw_include file='...' mode='...'/>
In 'docroot' mode, -iw_include-location <vpath> must be used
</ERROR>

Any ideas on this one?

Thanks.

Lucas Cochrane
lcochrane@dc.com

LooseCannon

It would help if you post the syntax of your iwpt_compile command.

Adam Stoller

To hazzard a guess simply from reading what you posted ... you are using an iw_include directive with a mode attribute value of 'docroot' (default mode value) and when you use this mode, you must supply the -iw_include-location vpath argument to your command line.

You might want to look at the documentation (perldoc TeamSite: Smiley Tongue

T::iw_include) which would seem to confirm the above assessment

--fish
(Interwoven Senior Technical Consultant)

Ottawa_IWOV

this is the syntax i am using for my iwpt_compile.ipl command....

iwpt_compile.ipl -pt y:\internet_hrdc-drhc\main\development\workarea\dev\templatedata\hrdc-drhc\en_generic\presentation\hrdc_en.tpl -iw_pt-dcr y:\internet_hrdc-drhc\main\development\workarea\dev\templatedata\hrdc-drhc\en_generic\data\020710 -ocode testing.ipl

Thanks.

P.S. I added the mode="docroot" in my .tpl in response to this error after I consulted the documentation, but that did nothing...

Lucas Cochrane
lcochrane@dc.com

Place the include file that hrdc_en.tpl is calling in the same presentation dir. Call the include file from hrdc_en.tpl like:

<iw_include pt='master-include.tpl' mode='ptlocal'>

That should resolve your problem.

mogoo

As an alternative to LooseCannon's suggestion, and as fish was pointing out, you can simply add an -iw_include-location flag to your command...

iwpt_compile.ipl -pt y:\internet_hrdc-drhc\main\development\workarea\dev\templatedata\hrdc-drhc\en_generic\presentation\hrdc_en.tpl -iw_pt-dcr y:\internet_hrdc-drhc\main\development\workarea\dev\templatedata\hrdc-drhc\en_generic\data\020710 -iw_include-location YOURHOME\.......YOURWANAME -ocode testing.ipl

...hope that helps!
maureen

Ottawa_IWOV

All,

Thanks for the awesome replies to this post, everything has been clarified, except....

For some reason iwgen does not seem to reference the directory for generating files in templating.cfg. When I generate thru the GUI, I am forced to generate to the directory specified in templating.cfg. However when i use iwgen from the command line, I have to specify the exact location...

Am I missing something here?

Thanks.

Lucas Cochrane
lcochrane@dc.com

Adam Stoller

What do you mean by "forced to generate to the directory specified in templating.cfg" vs. "have to specify the exact location" ?

When you go through the GUI - the areavpath (and with the iwmount know, file system path) is already known and the rest of the path is based on any restrictions you've placed in your templating.cfg.

If you go through the command line - you either have to supply the either the full file-system path, or relative file-system path from where you are running the comand, for the directory to generate the file into - I assume it is still constrained by any restrictions you have in templating.cfg (yes?)

The GUI already has context - the shell doesn't (necessarilly).

--fish
(Interwoven Senior Technical Consultant)