VisualPreview error msg

I am having a strange error wtih a file output by <iw_ostream> when I click on the file to preview it.

I have MS script debugger enabled, running W2K + IE with updates, patches,etc. The visuapreview bar does not actually appear in the document (so there is no way to close it), but I do see the visualpreview code in the document source. Another clue, the file loads normally in Firefox (no error msg) but no visualpreview bar.

Here is the error msg in IE :

A Runtime Error has occured.
Do you wish to Debug?
Line 233
Error: 'visual_preview' is undefined

and here is the snippet highlighted by script debugger:

visual_preview.prototype.get_text = function(key)
{
return {
close_instruct: "Are you sure you want to close VisualPreview?\n\nNote: To restart VisualPreview, either click on the \x22Back\x22 button in your Web browser or select a file and click \x22Preview\x22 from the ContentCenter interface."
}[key];
}

Hre is my ostream call (problem happens with or without oenc, filter) :

<iw_ostream oenc='iso-8859-1' file_val="$ostreampath" filter="ostream_convert()">
HTML here...
</iw_ostream>

I have validated the html, checked encoding,extended attribs (none, since it's ostream) etc. but dont' know what to do next... There doesn't appear to be any problem with the deployed file, but I'd still like to get to teh bottom of this, or it will surely cause me grief with my "clients".

Any ideas how to fix this? (or at least, tell me what's going on). ANY INSIGHT WOULD BE APPRECIATED.

Thank you very much.

TS 6.1.0 build 33333 on Solaris 8

Find more posts tagged with

Comments

Hans

I forgot to mention, if I turn off script debugging in IE, I still can't see the visualpreview bar, and IE status bar reports a JS error at bottom left "Done, but with errors on page".

Firefox javascript console also reports an error "visual_preview" is not defined.

Any help or insight is GREATLY APPRECIATED - I'm stumped, really don't know what to do with this.

thanks.

TS 6.1.0 on Solaris 8

Hans

I have found the solution to this problem - do not use a <base href="..."> in any files output by TS, whether through iw_ostream or default output stream.

Since I validated everything I could think of (encoding, xml, html, DCR, DCT, PT, etc.), I had to start from scratch before finding the problem. I guess the moral of this episode is don't assume that something will work in your presentation template just because it's valid html, xml, etc. and works elsewhere.

Hans

TS 6.1.0 on Solaris 8