Preview or Generate Mode

Is it possible to know in the Appearance XSL if its preview or generate mode. What I am trying to accomplish is we have a navigation component that generates an include file to be included in all the pages. For preview purposes I have the component on the Home page template so it can be previewed within SitePublisher. But as part of the workflow we are generating asp pages and I would like to replace the header component with just an include statement.

Please let me know if this is possible. Thanks for all the help.

Find more posts tagged with

Comments

Stokes

Yes. In Java External code you can use RequestContext.isRuntime() and isPreview(). In older LS versions I've used an External to place those values into the result XML for use in my Appearance XSL.

In LS3.1, you can access those same properties in XSL using $CONTEXT[runtime] and $CONTEXT[preview]. So you could do something like:
<xsl:variable name="isRuntime" value="boolean('$CONTEXT[runtime]')"/>
or
<xsl:variable name="isRuntime" value="not(boolean('$CONTEXT[preview]'))"/>

Stokes.

AlexC

In 672sp1 there will be a $CONTEXT{mode} which will return a constant for RUNTIME, PREVIEW, EDIT, and GENERATE_HTML.

Also note $CONTEXT uses {} instead of [] since [] is part of the beanpath spec for accessing array elements.

work4u

I have the following working

<xsl:variable name="isRuntime" select="'$CONTEXT{runtime}'"/>
Runtime=<xsl:value-of select="$isRuntime"/>
<xsl:variable name="isPreview" select="'$CONTEXT{preview}'"/>
Preview=<xsl:value-of select="$isPreview"/>

But I need to know if it is in generate mode. $CONTEXT{mode} throws a java error saying 'mode' is not a supported value.

Any thoughts?

AlexC

I do not know, I thought it was going to remap the enum into some constant and you would have to do trial and error to see which you get. We should probably add isHtmlGenerated as a method on the request context in the future release.

berlin1525

Has there been any updates to this? My question is similar to this post.

I am building custom components and adding them to a page through SitePublisher. I'd like to know from within the component what state the page is in.

The root of this is I'd like to pass this value to the javascript I have in the component and have it execute in any mode other than Edit.

When I use $CONTEXT{mode} in the component it is always returning PREVIEW, even though I'm in edit mode for the page that I've added the component to.

Any thoughts?

Using TS 7.0.

Bowker

I posted yesterday an issue with using $CONTEXT in XSL components in a decision (xsl:if/xsl:when...) because $CONTEXT is not converted to the requested value until AFTER the component has been processed.

For example if you do:

...

The test will ALWAYS FAIL because the system is testing "$CONTEXT{mode}" against 'PREVIEW' and not the actual mode.

If I'm mistaken here please correct me but I have some pretty hard evidence with some simple components I created yesterday.

shameem

You need to write an external in order to read the HTML and retrieve the whole HTML file as text during the preview mode and add it to the as child element.

CHeck in your XSL whether the is blank or not. If no child elements to Result element include the HTML file and if any content exist in element, show that content.

Hope that solves...

shameem

Got some opportunity to do more research on this.

You are right Dan.

I was thinking, am wrong some where in XSL syntax even though I am pretty sure. So tried all sorts of testing $context{mode} after assigning the value to a variable.

Nothing below works. So ended up creating a external component to decide this for me and return a value to my XSL. Pasting all my trails so that somebody else saves some time.

If berlin1525, works4u, Alex got it worked, please throw some light.