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

shared FormAPI functions within tpls

plantronics

I am trying to "include" a FormAPI function in my tpls using <iw_include pt="path/to/formapi/function.tpl"/> , but the calling page does not seem to have access. Is there any way around this?

Specifically what Im trying to do is call a function that strips white space from the output file (generated by templating) and not have to copy and paste this function every time I want to make a change. I know I can createa Perl module out of it but I dont have root access, dont have time to spend learning how to createa my own perl module, and am looking for a simple solution. Here is some sample code (the parse_page function is what I want to make "shared" via the iw_include):

<iw_perl><![CDATA[
sub parse_page {
my $data = $_;
# Strip all whitespace from the front of the doc.
$data =~ s/(\s*?)</</;
$data =~ s/\t//g;
# Strip anything after </html>
$data =~ s/<\/html>(.*)/<\/html>\n/s;
my @lines = split(/\n/,$data);
$data = "";
foreach my $line (@lines) {
if(length($line) > 0) {
$data="$data$line\n";
}
}
$_ = $data;
}
]]></iw_perl>
<iw_ostream filter="parse_page()">

tpl code goes here.....

</iw_ostream>

The contents of the include file would be everything inbetween the <iw_perl> tags including the tags themselves.

Mike

Find more posts tagged with

Comments

Adam Stoller

FormAPI is used within DCTs not PTs - the inclusion (via directives) of FormAPI code within PTs doesn't really make sense because the DCT is rendered completely within the TS environment as is the PTs processing of the DCR (which does *not* utilize javascript). The only place it makes sense from a PT perspective is if you were going to output javascript code within your rendered output page - but I doubt you'd want your web pages on your production web server referencing javascript source files from your TeamSite [development-side] server.

The code you show in your post is not FormAPI / javascript - it's Perl code (as you noted) - I'm not sure why you'd need root access to create a Perl module - but if you are doing TS development and need root access to do your work you should make sure you have sudo access - if they don't want to give you sudo access - well, that's something you'll need to take up with them.

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

plantronics

Sorry, Ive been switching hats too much lately between perl and javascript/FormAPI (using Perl to output formAPI functions and so on). I meant Perl as should be obvious from the code sample. Now that Ive clarified, is there some way to include a Perl function in the tpl (via a iw_inlclude statement seems not)? Right now, and I am just looking for a quick solution that doesnt involve creating an entire module just for one little function.

Mike

Adam Stoller

One builds a module one little subroutine at a time - it doesn't really take all that much effort (below).

However - if you want to do it in a somewhat awkward (IMO) way - I suppose you could create a PT that contains you're little iw_perl snippet - include that PT in your other PT and then use the previously defined subroutine elsewhere within your main PT.

Writing a module is pretty easy:package MyPTStuff;
use strict;
use warnings;
use vars qw(@ISA @EXPORT @EXPORT_OK $VERSION);
use Exporter;
$VERSION = 1.00;
@ISA = qw(Exporter);
@EXPORT = qw();
@EXPORT_OK = qw(parse_page);
1; # <-- This is important, not a typo
sub parse_page {
my $data = $_;
# Strip all whitespace from the front of the doc.
$data =~ s/(\s*?)</</;
$data =~ s/\t//g;
# Strip anything after </html>
$data =~ s/<\/html>(.*)/<\/html>\n/s;
my @lines = split(/\n/,$data);
$data = "";
foreach my $line (@lines) {
if(length($line) > 0) {
$data="$data$line\n";
}
}
$_ = $data;
}Done!

Mind you, I'm not sure your code is doing what you want - or perhaps not how it's commented - I believe you're looking for something like:sub parse_page {
my $data = shift;
$data =~ s|\t| |gsm; # replace all tabs with a space
$data =~ s|^\s+||; # remove leading white space
$data =~ s|</html>.*|</html>\n|s; # remove text after </html>
# remove all blank lines
my @lines = split(/\n/,$data);
$data = "";
foreach (@lines) {
$data .= "$_\n" if (!/^\s*$/);
}
return $data;
}...though I could be misreading your intent.

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