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

Extended Attributes

meha

Hi,

Im trying to set EA(Extended Attribute) for generated html in the tpl. And my contents are taken from Visual Editor. The problems im facing are:
1) Im setting in tpl like "my $hlEA = `$iwhome/bin/iwextattr -s Headlines='$hlines' $vpath[$#vpath]`;
Im setting the attribute Headlines. since $hlines is within single quotes, if the text of $hlines contains a single quote, it gets removed in EA when its set.
2) The html tags like <p> are also set in EA.

I wish some one could suggest me the reason for these issues.

Thanks & Regards,
Meha

Find more posts tagged with

Comments

Migrateduser

A couple of things stick out to me...

I don't know what your vpath array looks like, but I wonder what your command looks like. Could you log it by doing something like:



my $cmd = qq^$iwhome/bin/iwextattr -s Headlines='$hlines' $vpath[$#vpath]^;
open(FILE,">$iwhome/tmp/eaLog.txt");
print FILE "$cmd";
close(FILE);
my $hlEA = `$cmd`;

If you want the single quotes escaped, I'd suggest using escape characters -- more than one may have to be used, given the Perl interpreter, but then again, you're using single quotes... you may need to experiment with that.

Whatever comes out of that log file I described above should be able to be entered into the command line without errors.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP1 on W2K
(3) TS 6.1 SP2 on Win2K

meha

HI Dave,

Thanks for ur reply.

I have tried out what u have told, within the text file it shows the single quote but in the EA it has been removed. Eg:Birmingham's is as Birminghams in EA

Even if i try to escape the change is applied in the text file. but not reflected in EA.

Im not able to figure out, do help me out.

Thanks a lot
Meha

Migrateduser

Meha,

I'm 99% sure that you might not be escaping the single quote as many times as necessary. Sounds strange, but for instance, I had put together a very slick callout that makes heavy use of Javascript. Being a TS callout, Perl is used to actually generate the output. SO, there were characters that I needed to escape SIX times for it to work -- with various interpreters parsing my code, it was iteratively stripping out the escape characters, which I needed to account for.

1. You could try adding escape characters until the output in the text file is what you expect it to be, OR
2. You could use double-quotes instead, although you may encounter the same problem down the road (but with less likelihood). For instance: ... Headlines="$hlines" ...

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

Adam Stoller

Try: my $cmd = qq^$iwhome/bin/iwextattr -s Headlines="$hlines" $vpath[$#vpath]^; and see if using double-quotes in the command line helps fix the problem.

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

Migrateduser

This would help the immediate situation, but this person's users may be creating content that contain double quotes, hence **** off the syntax that you and I suggested. Double quotes are definitely better than single quotes, but I don't see how this person will get around using possibly many escape characters, other than stripping them out ahead of time which partially defeats the purpose.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

chuckles

Quotes aside, isn't it impossible to set EA for a file while it is being generated? If you are generating a new file, it may not exist until the TPL is finished running. Try putting an if (-e $file) check before you set the EA and print out some debugging info. Just a guess.

iwovGraduate

... isn't it impossible to set EA for a file while it is being generated? ...

You can set extended attributes for a file thats being generated from within the TPL.

Migrateduser

True, because isn't the file itself created as soon as the TPL interpretation has kicked off, therefore any modifications you're doing to the file within the TPL are valid? I don't recall the exact order, but I know this is possible.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K

iwovGraduate

I am not sure of the exact order either. It has worked for me so I never tried to ponder about it

meha

Hi,

I have tried with double quotes. But now if the content includes a double quote it is not setting th EA at all.

What could be done for this.

Thanks & Regards,
Meha

Adam Stoller

Try this: use TeamSite::CGI_lite;
my $cgi = new TeamSite::CGI_lite();
my $hlines = $cgi->escape_form_data($hlines);
my $cmd = qq^$iwhome/bin/iwextattr -s Headlines="$hlines" $vpath[$#vpath]^;
my @results = qx($cmd 2>&1);
my $status = $?;
if ($status){
# error ...
}oruse HTML::Entities;
my $hlines = encode_entities($hlines, "\"'<>&");
my $cmd = qq^$iwhome/bin/iwextattr -s Headlines="$hlines" $vpath[$#vpath]^;
my @results = qx($cmd 2>&1);
my $status = $?;
if ($status){
# error ...
}

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