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

evil module inclusion problem

System

I will explain this all in more detail later if necessary, but I want to try to get out of here right now, so I'll be short. I have a utilities module. If I use it in a presentation template, I can no longer preview that template from the GUI. If I do I get:


Preview And Generate Preview And Generate: 

The following error occured while creating file Y:\default\main\Intranet\TSG\WORKAREA\content\templatedata\zz_tst_E057104_0_manifest:
Broken pipe
The file was not generated.

and a hung iwpt_compile.ipl process on the server. If I take the command line for the process (retrieved via process explorer) and run it at the command line, I get valid output, but some warnings. I tracked the warnings down to the inclusion of TeamSite::XMLParser and TeamSite::XMLNode in the module itself (some of the functions in the module can do user lookups against either an xml mapping file or against AD). I removed the uses for those and it works fine in the context of a PT now. This is a major pain, because it means I have to maintain separate versions of a 99% identical module just to handle whether its called from a PT or from some other context.

This also doesn't make a whole lot of sense to me, given that:

A)the perl interpreter is supposed to check %INC before importing any module, to make sure it hasn't already done so, and
B)the encountering of warnings during the compile phase shouldn't cause iwpt_compile.ipl to hang anyway (and doesn't, except when its being run by the preview or generate cgis).

Anyone (especially someone from engineering) have any helpful thoughts here?

Find more posts tagged with

Comments

Adam Stoller

Unfortunately warnings being generated when running the program may be getting sent to STDOUT - if so - they're probably happening *before* the window has been initialized with 'content-type:text/html' and thus breaking the CGI aspect of previewing within the GUI.

If you're using TS6 you could try to take advantage of the warnings pragma - i.e. instead of:

#!/...../iwperl -w
use strict;
use TeamSite::XMLnode;
...

do

#!....../iwperl
use strict;
no warnings;
use TeamSite::XMLnode;
use warnings;
...

And that might get around some of those spurious warning messages that were causing issues.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

Yeah, I was suspicious that they were going to stdout, so I compiled to ocode, ran from the cmd line, and redirected stdout to a file, e.g.:


iwperl foo.ipl > foo.htm

the warnings all printed with stderr and the file was clean. Setting no warnings should work, but I'd rather not have the warnings than ignore them, if possible.

Migrateduser

Surprisingly


no warnings 'all';

doesn't stop it. So they must be errors rather than warnings, just non-fatal. Still doesn't explain why the interpreter isn't noticing that it already has the module included.

Migrateduser

I had a little more time to mess with this, so I put together two tiny test modules and a test script that follow the same paradigm of nested inclusion (which you will find attached). Surprisingly, this executes without any problems. Anyone see a reason this should be different than what happens with TeamSite::XMLParser?

Edited by robhuffstedtler on 10/25/04 10:48 AM (server time).

Migrateduser

ARgghhh..... didn't manage to attach all the files.

Migrateduser

Apparently, one can only attach one file - I guess I should have zipped them. Anyway, here is the last file