Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
FormAPI in inline
Jens
Hi all,
after updating from TS 5.5.2 to 6.1 formAPI doesn't work if it is coming via inline.
any workarounds possible for that.
Ciao,
Jens
Find more posts tagged with
Comments
brandon1
By
"after updating from TS 5.5.2 to 6.1 formAPI doesn't work if it is coming via inline.
any workarounds possible for that."
Do you mean that formAPI written by a callServer is not working?
Current Project: Content Services implementation
Jens
no, in datacapture.cfg we use an <inline>-Tag calling a perl-script and this contains a javascript-block.
brandon1
OKay
Can you post the "javascript block" or maybe the entire PERL script?
Current Project: Content Services implementation
Jens
i tried this with an easy inline.
datacapture.cfg:
<inline command='/bin/cat /data/iw-home/local/test.cfg' />
test.cfg:
<?xml version="1.0" encoding="ISO-8859-1"?>
<substitution>
<script>
<![CDATA[
<!--
alert("jens");
-->
]]>
</script>
<item name="test">
<text />
</item>
</substitution>
the item is displayed correct. alert doesn't appear.
Migrateduser
test.cfg should contain something that looks like this:
<substitution>
<option label="a" />
<option label="b" />
<option label="c" />
</substitution>
... for instance.
Dave
Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
brandon1
Seems strange to me that you would even place formAPI in a substitution statement? This worked in 5.5?
Current Project: Content Services implementation
Migrateduser
I think we crossed wires... Jens says s/he's migrating to 6.1. Also, datacapture.cfg makes a
call
to cat test.cfg -- test.cfg should ultimately spit out something like the text I wrote in my previous post, regardless of what language is creating the output.
Instead, Jens has tried to concat a smaller DCT, which is not going to work.
Dave
Current Environment(s):
(1) TS 6.1 SP1 on W2K3
(2) TS 6.1 SP1 on W2K
Jens
Hi guys,
thanks for reply.
what i posted is just a simple example, which works in 5.5.2 and not in 6.1.
our real <inline> calls perl-script which create items and formapi-element dynamically, depends on database entries.
But i already found out that the problem is the same. so i think if the simple code is working the big one would be working too.
Ciao,
Jens
Migrateduser
I found that JavaScript generated by inline would only execute in certain browsers even in 5.5.2. I would not generate FormAPI this way if you can avoid it - can't you replace your inline with a script tag? If the script has to be dynamic, I think you can write the script to return just JavaScript without the substitution, and just have the script tag reference that URL.
Jens
it's a good idea, i will try this.
PaulD
Hi Jens,
We have the same issue on AIX. What platform is your version TeamSite running on?
thx
Paul
Jens
our platform is solaris.
this issue is also fixed in TeamSite 6.1.0 Service Pack 1 for solaris
Bug ID 55034: Properly evaluate script tags for in-line callouts.
see also:
https://support.interwoven.com/kb/kb_show_article2.asp?ArticleID=53345
PaulD
Jens
Thank you for the info!
Paul