HP TeamSite 7.5.0.1 patch set is now available

It should be made very clear that there is only a choice between XSLT 1.0 and 2.0 in Site Publisher. If you use XSLT in your DCR PTs, or with the CSSDK, you will still be using XSLT 1.0 - there is no choice there. The release notes are not clear at all about that.

For the XSLT in your DCR PTs (FormsPub), was 7.5.0.0 XSLT 2.0 OOTB and now 7.5.0.1 takes it back down to XSLT 1.0?

As a side note, I notice the 8.0 release notes mention the following about Formspub, but yet the 7.5.0.1 release notes fail to mention the same information:

XSLT

Teamsite 7.5 (typo, it probably should say 8.0) supports XSLT 1.0 and XSLT 2.0 stylesheet templates. Apache Xalan library supports XSLT 1.0 version; and Saxon Home edition library is supported for XSLT 2.0. Customers migrating from earlier releases of SitePub can choose either version 1.0 to continue to use Xalan, or upgrade to the 2.0 version to make use of the Saxon library.

Formspub uses XSLT 1.0 by default. To leverage XSLT 2.0 in FormsPub:
1. Develop a custom compiler class.
2. Specify the full path of this class in the ptcompiler attrribute of the templating element in templating.cfg.

The New Component screen allows you to select either the XSLT 1.0 or the XSLT 2.0 stylesheet to create a new skin.

Note: The OOTB-provided templates use XSLT 1.0.

TimK wrote:
For the XSLT in your DCR PTs (FormsPub), was 7.5.0.0 XSLT 2.0 OOTB and now 7.5.0.1 takes it back down to XSLT 1.0?

As a side note, I notice the 8.0 release notes mention the following about Formspub, but yet the 7.5.0.1 release notes fail to mention the same information:

XSLT
Teamsite 7.5 (typo, it probably should say 8.0) supports XSLT 1.0 and XSLT 2.0 stylesheet templates. Apache Xalan library supports XSLT 1.0 version; and Saxon Home edition library is supported for XSLT 2.0. Customers migrating from earlier releases of SitePub can choose either version 1.0 to continue to use Xalan, or upgrade to the 2.0 version to make use of the Saxon library.

Formspub uses XSLT 1.0 by default. To leverage XSLT 2.0 in FormsPub:
1. Develop a custom compiler class.
2. Specify the full path of this class in the ptcompiler attrribute of the templating element in templating.cfg.

The New Component screen allows you to select either the XSLT 1.0 or the XSLT 2.0 stylesheet to create a new skin.

Note: The OOTB-provided templates use XSLT 1.0.

Yes 7.5.0.1 forces Forms Publisher (Preview) and CSSDK (XSLTransformer class) to xslt 1.0 (Xalan). They basically provided that patch for me because I **** and moaned enough. We tried converting all our PTs to XSLT 2.0 but it was a ton of work and there are nuances that are not obvious that change the way your content displays, so you have to check every line of code. It's not fun. So we asked them to find a way to let us use the Xalan compiler and they forced those 2 processes back to 1.0. I was surprised they put that in an actual release, but that's what they did. Those lines from the 8.0 Release Notes are interesting - they should have added those to the 7.5.0.1 Release Notes as well.

We do use our own custom code to perform the vast majority of transformations, and we had to tweak that as well since we only use the CSSDK for our email notifications - not the transformations of our PTs. The CSSDK doesn't provide the features we need (we use the javax.xml.transform.TransformerFactory class to implement tramsformations). Unfortunately those java classes (which are shipped with TS) automatically used the Saxon 2.0 version of those classes, so I had to work some voodoo to force it to use the Xalan 1.0 classes. That may be what they're referring to in that obscure note.

We asked support if there was any way in 7.5 to use the old XSLT 1.0, and they said it wasn't possible. Thank you for **** and moaning! I've been following your complaints on these forums and know that you also had the same issues as us... We just accepted that we were going to have to make updates to our code to support XSLT 2.0...

So in 7.5.0.1, have you noticed improvements around your XSLT?

TimK wrote:
We asked support if there was any way in 7.5 to use the old XSLT 1.0, and they said it wasn't possible. Thank you for **** and moaning! I've been following your complaints on these forums and know that you also had the same issues as us... We just accepted that we were going to have to make updates to our code to support XSLT 2.0...

So in 7.5.0.1, have you noticed improvements around your XSLT?

Yes nearly all of the compiler errors produced by running our old 1.0 PTs through the 2.0 compiler are no longer failing. As I said in the other thread I found one issue so far that shouldn't have even been allowed in 1.0 that we did - I think it was embedding a disable-output-escaping inside a variable. That's not allowed in 1.0 but the old compiler TS used allowed it. That's a minor thing to fix. Everything else appears to be working as it did in 7.3.2 (and earlier). In other words, our XSLT 1.0 PTs are working fine with 7.5.0.1. No XSLT issues. We do not ise Site Publisher, so I can't speak to their implementation allowing a choice there.

You can feel free to email me if you like - david.smith3@wnco.com

Even though it sounds small; its kind of scary that you're seeing an issue. You would think they would have brought back the same compiler as previous versions of TS...

TimK wrote:
Even though it sounds small; its kind of scary that you're seeing an issue. You would think they would have brought back the same compiler as previous versions of TS...

Everything Interwoven/HP produces is scary. Smiley Happy I'm just glad we have a very miminal amount of work ahead than if we had to upgrade everything to 2.0. That was very scary for us. Our website is everything to this company and any content that would display incorrectly would be a big hit for us. So we need to be very confident in what we're putting on the website. Fixing minor 1.0 issues (that should have been caught in their earlier compiler) is a small problem as far as we're concerned. We are testing all of our templates thoroughly before we go to production. You'll be stuck doing the same regardles of which version you decide to upgrade to. I'd rather do a little work than a ton. Plus on a side note, while researching how best to update our PTs from 1.0 to 2.0 we came across a few articles that said don't ever try and upgrade existing 1.0 to 2.0. Best option would be to leave all your 1.0 XSLT as it is and begin developing new XSLT with 2.0 - that's assuming you have a compiler that supports both. Unfortunately IW/HP did not even think about that for Forms Publisher or CSSDK (or java) - they assumed the only place people were using XSL was in SP. A foolish assumption that has really made them bungle these latest releases.

We attempted this morning to install the 7.5.0.1 patch on Windows 2012 and the installer is erroring out for us when trying to unpack the main iwpkg... We have a case opened and are awaiting a response.

After working with support, we found that we needed to stop all IW services, including IIS because we have the iwproxy dll configured and it was not allowing the install to continue with that running...

After playing with 7.5.0.1, we can confirm that FormPub is using XSLT 1.0 now, but its not 100% the same 1.0 compiler that previous versions of teamsite had... For example, we had XSLT from TS 7.2.1 which had a trailing slash after the "value":

<xsl:variable name="heading" select="item[@name='heading']/value/"/>

This code functioned fine in TS 7.2.1, but was failing in 7.5 with the XSLT 2.0 compiler (more strict). In upgrading to 7.5.0.1, we expected that this code would function as it did in 7.2.1 with the 1.0 compiler, but it did not work; PT compiler error... So even though 1.0 was brought back to formspub, its still requiring us to make code updates which we hoped to avoid in installing this patch...

And to make things worse, the XSLT 1.0 sitepub enhancement doesnt even work, it still appears to be using 2.0 regardless of the selection made when creating a new component...

We confirmed all of this by running the following through the XSL:

Version: <xsl:value-of select="system-property('xsl:version')" />
<br />

Vendor: <xsl:value-of select="system-property('xsl:vendor')" />

<br />
Vendor URL: <xsl:value-of select="system-property('xsl:vendor-url')" />

No matter which choice, it still saying you're on 2.0 Saxon...

I can concur it is not the exact same XSLT 1.0 compiler as was in previous versions - it's more strict, which is probably good. We have had to make some minor updates to our XSL that shouldn't have even been allowed in 1.0, but for some reason the old compiler allowed it. I think you'll find the updates you need to make are for fewer than if you had to use 2.0 across the board.

I can't speak to SP - we don;t use it. But after your comment, I'm glad we don't.

I've finished installing the 7.5.0.1 patch on our Dev and QA servers and it's going pretty smoothly. The install takes about 2 hours to do both TS and Search and perform the minor config updates for our purposes. We've tested all of our PTs amd there were just a handful of minor syntax issues that failed under the new 1.0 compiler - all very easy fixes compared to what we would have had to do to become 2.0 compatible. We still need to validate how special characters are rendered but don't expect any big surprises there. All in all, we are feeling pretty happy with 7.5.0.1.

Smitty97007 wrote:
......... All in all, we are feeling pretty happy with 7.5.0.1.

OK, someone hacked Smitty's account and is posting again. :-)

"pretty happy" is a relative term. We're not ecstatic. And I can't wait to find out how this affects people who are upgrading to 7.5 or 8 when they have a sh%t ton of PTs coded in XSL.

Kevin Butcher

Do any of you still use the Interwoven site to download software? I see in this article that it says to use the HP Autonomy Download center for the patch which I have but I've heard nothing from HP in 3 days. How silly is it that you have to request a patch? A patch does no good unless you can download the full version so why not make it easier to download? Anyway I also do not see it on the Interwoven site so I was curious how long it took you guys before HP responded to your "Download Request".

Downloads are on a new site

Log into the man support site and use the menus. This changed a month or so ago.

Gregg Faus

I requested downloads on the new support site about 10 days and haven't heard a peep. My request is still pending.

Adam Stoller

The downloads location status appears to be in a bit of a flux right now - some stuff is only on the new HP download site, some stuff appears to only be on the old Interwoven download site - I suggest checking both - but start with the HP site as that's the one that should be used going forward (and the only one that carries 8.0)

You have to go through several clicks once there to get to the actual software to download (choose something in the first column, then choose something in the second column, then the choose something in the third column - and then the files should show up below - or something like that).

If you're not seeing anything - you might be better off trying to call HP Support than going through emails.

Kevin Butcher

Thanks fish. I opened a case with HP so we'll see what happens. I can't see any of th products we own from the HP site just the old Interwoven site. Hopefully we'll get it straight here soon. Thanks everyone for their replies. So glad DevNet didn't die with all the changes.

gfaus wrote:
I requested downloads on the new support site about 10 days and haven't heard a peep. My request is still pending.

How did you "request"

I just go to the site, Click Downlodads->Products

A new window opens (HP Autonoy Download center)

Product Family is DIgital Margeting -> LS/OD/MB/TS are the choices, select the Base Component and then the platform.

I see versions 7.3.1 through 8, including the 7.5 patch.