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

XSL Presentation Template - Output missing code

dlsoderberg

TS 6.7.1 SP1 on Linux

I am designing some XSL Presentation Templates and am getting only the values from the DCR in my output file. All of the surrounding html code is not printing in the HTML file, only the values from the fields in the DCR that I'm pulling. I tried putting the example 'yacht' template that ships with TeamSite and that output is doing the same thing.

Has anyone else seen this similar behavior? So instead of seeing what I would expect:

[html] Value of field Value of another field

[/html]

I'm getting:

Value of field Value of another field

Thanks for any help offered!

Find more posts tagged with

Comments

LooseCannon

Attach the XSL file for reveiw.

Ambuj

Value of another field
TS 6.7.1 SP1 on Linux

I am designing some XSL Presentation Templates and am getting only the values from the DCR in my output file. All of the surrounding html code is not printing in the HTML file, only the values from the fields in the DCR that I'm pulling. I tried putting the example 'yacht' template that ships with TeamSite and that output is doing the same thing.

Has anyone else seen this similar behavior? So instead of seeing what I would expect:

[html] Value of field
[/html]

I'm getting:

Value of field Value of another field

Thanks for any help offered!

Please post code snippet and screenshot so that the problem could be clear...

dlsoderberg

Here is a snippet from the templating.cfg file:
[html]

[/html]
Here is a sample DCR as well:
[html]

Testing
n
Testing
<p>esting</p>
<p>Testing</p>
Testing
<metadata>
testing,keywords,dave
This is the description
public
landing

[/html]
I'm attaching the PT here as well. The only other thing I can point out at this point is that I played with removing the line in the PT. When it's in the file, I get everything outputted as is...the xsl doesn't translate into the DCR values. When the line is removed, the XSL does translate to the DCR values, but all of the surrounding information is lost (all HTML code and tags). I've attached a Word document with the source code of the output files of both scenarios as well.

siddin

Hi dlsoderberg,
plz refer to the last post of this thread [thread=21186]click here[/thread]

dlsoderberg

I don't see what in that last post will help me resolve my issue...the xsl attached there is just a snippet of your whole PT, I'm guessing. Is there something specific you are referring to in that post?

siddin

please try this remove this "/"
[html][/html]
change to
[html][/html]
and let me know if this works, i went through everything else looks fine to me

siddin

I am attaching the entire PT hope this helps

dlsoderberg

No difference...I still get the "

dlsoderberg

Should have know better...

I still get the following in the HTML file instead of the actual value:
[html]

[/html]

siddin

when you are using the below code and preview it are you able to see the html tags?
[html]

[/html]

and when using this you are able to see the actual value and not the html tags ?
[html]

[/html]

dlsoderberg

They both produce the same output...the HTML code with the XSL code still plugged in instead of the value from the DCR.

siddin

hey is the yacht XSL working for you i tried it at my site it is working for me, I copied your templating.cfg entry but modified dcr type to "iwov"

if possible send me your complete datacapture and xsl ill try at my end and let you know!

Adam Stoller

I tried out your stuff on my 671SP1 + Patch 1 Windows system
- I created a DCR that duplicated the structure you posted
- I then created an XSL file based on what you posted (which originally failed)
I played with it until I got the attached - which seemed to work - compare it to what you have and you should be able to go from there.

You should note that the DCR you posted contained improperly nested formatting in what was presumably textarea code (the 'p' and '/p' tags were each wrapped in their own font tags and thus not properly nested)

I think you also failed to keep consistency with regard to case-sensitivity of element addresses.

dlsoderberg

The yacht example doesn't work on my system, but the general-content example does.

Ghoti, your xsl didn't work on my system either. I've opened a case with support to try and get to the bottom of this one. I'll update again once the issue has been pinned down.

Thanks!

dlsoderberg

I found something interesting...I have Form API code that auto-names the DCR, then gathers the information for generating the output file and finally performs a callServer to a CGI script that generates the file with iwgen. When this process runs, the files don't generate correctly. But if I select the file and run Actions...Regenerate Page, it is then correct.

I'm not sure why the iwgen isn't getting me the proper results. Has anyone seen this before? Worst case, I can try throwing in an iwregen command as well as see if that takes care of it.

Adam Stoller

The yacht example doesn't work on my system, but the general-content example does.

Ghoti, your xsl didn't work on my system either. I've opened a case with support to try and get to the bottom of this one. I'll update again once the issue has been pinned down.

Thanks!

Are you running 671SP1 + Patch 1 - or just 671SP1?
My code worked on Windows - I don't know if there are any issues with the Linux version.

dlsoderberg

I'm just on 671 SP1, no patch.

I've found that if I take out my Form API script altogether so that I manually save and generate the output, the HTML file generates correctly. With my Form API script in place, the code handles naming and saving the DCR and then setting up and generating the HTML file, and that is not working correctly. In that case, the output file is created but does not have any values from the DCR...it just outputs the XSL code directly into the output.

Adam Stoller

I'm just on 671 SP1, no patch.

I've found that if I take out my Form API script altogether so that I manually save and generate the output, the HTML file generates correctly. With my Form API script in place, the code handles naming and saving the DCR and then setting up and generating the HTML file, and that is not working correctly. In that case, the output file is created but does not have any values from the DCR...it just outputs the XSL code directly into the output.

Well - that sounds like there's an issue in your FormAPI code - I suggest you spend more time debugging that then. Check for environment information, variable evaluation, etc.

dlsoderberg

Has anyone out there tried to auto-generate output files using the XSL parser? I've tried iwgen, iwpt_compile and URL generation (http://hostname/iw-cc/urlgenerate?dcr=dcr_name&pt=pt_name&output=output_name), but none of them work for me. Both iwgen and iwpt_compile do generate output files, but not correctly. (They dump the XSL code into the output, no DCR values) If I then manually select the HTML file and run Actions...Regenerate Page, the output file is then correct. The URL gives me an error that URL generation is not supported with my current PT parser.

Any suggestions would be greatly appreciated!!!

Thanks!

Phanie

Has anyone out there tried to auto-generate output files using the XSL parser? I've tried iwgen, iwpt_compile and URL generation (http://hostname/iw-cc/urlgenerate?dcr=dcr_name&pt=pt_name&output=output_name), but none of them work for me. Both iwgen and iwpt_compile do generate output files, but not correctly. (They dump the XSL code into the output, no DCR values) If I then manually select the HTML file and run Actions...Regenerate Page, the output file is then correct. The URL gives me an error that URL generation is not supported with my current PT parser.

Any suggestions would be greatly appreciated!!!

Thanks!

was just going through this KB 61587 which eventually speaks about why we get the error.

LooseCannon

Has anyone out there tried to auto-generate output files using the XSL parser? I've tried iwgen, iwpt_compile and URL generation (http://hostname/iw-cc/urlgenerate?dcr=dcr_name&pt=pt_name&output=output_name), but none of them work for me. Both iwgen and iwpt_compile do generate output files, but not correctly. (They dump the XSL code into the output, no DCR values) If I then manually select the HTML file and run Actions...Regenerate Page, the output file is then correct. The URL gives me an error that URL generation is not supported with my current PT parser.

Any suggestions would be greatly appreciated!!!

Thanks!

iwgen and iwpt_compile do not support the XSLT PT compiler. According to IWOV the supported method to generating output with the XSLT PT compiler is with the URL generation cmd. BUT the URL cmd only works when templating.cfg defaults to XSL PT compiler. This bug is supposed to be fixed in SP2.

Calling the compiler ($iwhome/httpd/webapps/content_center/WEB-INF/lib/bsf.jar org.apache.xalan.xslt.Process) directly is a viable workaround.

dlsoderberg

Thanks Phanie and LooseCannon!

I got this resolved with the changes from the KB Article and then setting up the URL properly in my Form API code to call the urlgenerate command. I'm finally beyond this issue.

Thanks to everyone who offered help on this one!

tobias

Hi dlsoderberg,
when you use the urlgenerate URL command to generate your output files, do you do that in a (popup) browser window or did you find some other way - one that does not require you to open up a browser?

I am asking because we are facing the same issue, only our output files should not be displayed in a browser upon generation.
That's why we are discussing using the URL command in a hidden frame or something similar, but we don't really like this approach. So if there is another way of accomplishing the page generation, we would be more than happy to learn about it and check it out.

Thanks,
Tobias

LooseCannon

Hi dlsoderberg,
when you use the urlgenerate URL command to generate your output files, do you do that in a (popup) browser window or did you find some other way - one that does not require you to open up a browser?

I am asking because we are facing the same issue, only our output files should not be displayed in a browser upon generation.
That's why we are discussing using the URL command in a hidden frame or something similar, but we don't really like this approach. So if there is another way of accomplishing the page generation, we would be more than happy to learn about it and check it out.

Thanks,
Tobias

One way... Run the URL Generate command from a URL workflow task.