SitePub XSLT Determine if preview or generated HTML

Tober

In TeamSite(s) 7.1 and 7.2.1, we were using the value of:

 

<xsl:value-of select="Properties/@Admin"/&gt;

 

To determine if a sitepub page was being previewed in TeamSite (this value would be true)

 

Or if this page was generated HTML output from a SitePublisher .page file (this value would be blank)

 

We believe the developer who did this for us a few years back (he's on longer working with us, go figure) used this example from here: http://www.littleforest.co.uk/xsl-reference/ (its similar, but instead of geneated HTML, they are saying LiveSite runtime, which we do not use, but it worked in either case)

 

We are now trying to migrate to TeamSite 7.5.  We are experiencing all the same issues as everyone else trying to get to TS 7.5, but this one is a real showstopper for us because this value is used across multiple components that are on thousands of pages and we don't know what to do at this point... We opened a case with autonomy but they said that since its custom code and not something out of the box, they cannot assist without involving professional services.

 

Does anyone know of a way in the XSLT of a Sitepub component to determine whether a page is being previewed in TeamSite VS generated HTML output?  In previous versions of TeamSite, generating the HTML would give a blank/empty value for Properties/@Admin.  But in TS 7.5, generating the HTML gives a value of 'true' and our code is displaying the wrong content.  I know TS 7.5 is still new and not many people are using it yet, but maybe someone is doing this another way that may work in 7.5... Fingers crossed.

Rick Poulin

What happened is that in 7.4, they changed some of the flags. Before, context.isPreview() used to mean "edit, preview and possibly generate (?)" and context.isRuntime() was only true on the runtime. As of 7.4, they flipped it such that isPreview() is only true in preview, and context.isRuntime() is only true on the runtime, and edit+generate is ambiguous. Or something. I keep playing between versions so I'm all sorts of confused on the topic.

 

Point is, I feel that support gave you a bull**bleep** answer. It's true that the way you've used the @Admin attribute is custom code, but where that value comes from is HP code. They should have been able to explain the change to you.

 

As for how to resolve it, I have a common external that is referenced by all my components. Amongst other things, it prints those context.isPreview() and context.isRuntime() flags and then I have my XSL look at that instead of /Properties/@Admin, since I can't control where that one comes from. Thus, when I flip between early teamsite and 7.4+ teamsite, I only change it in one place.

 

That doesn't help you right now, as you're going to have to go through all your components one way or another, but that's a way to isolate yourself from such future activities.