ALI Publisher 6.5 Released
As you may have heard, Publisher 6.5 was released last week. And this isn’t one of those baby releases that just changes the BEA branding to Oracle – it’s a legit upgrade, and I’d encourage everyone to make the move – if not for the new features, for the boatload of bug fixes. Even if you’re not ready to upgrade to the 6.5 portal, it’s supported with ALI 6.1 MP1 and MP2 (see the Interoperability Matrix – login required).
See the release notes for full details, but here’s a quick summary from the huge list of bug fixes and enhancements:
Adaptive Tag is broken in Rich Text Editor at switching WYSIWIG to HTML editor. (Issue #54748)
Only “Time”, “Page Name” & Community name” transformer tags display the value. (Issue #42867)
Rich Text Control does not support anchor tags ‘#’ in <a href=#</a> links. (Issue #55759)
These issues are reason enough to upgrade to 6.5! No longer do you have to use Presentation Templates to leverage adaptive tags – the new Dojo WYSIWYG editor doesn’t delete your tags, and even shows them unformatted in the rich text editor that you know they’re there. Sure, ideally it would be nice if these tags were actually parsed (so the rich text editor would show the actual opener link below), but I’m not complaining – this is a huge step forward.
Publisher content is accessed via a redirect.jsp page which AquaLogic Interaction does not cache. This can cause major performance problems. (Issue #48758)
In a clustered environment, published_content_noredirect.jsp fails to proxy the entirety of the published content page. (Issue #60272)
This is also an enormouse improvement! Rather than issuing a redirect, the Publisher Redirector now streams the data from the Published Content server directly back to the Portal Server. Why is this big? Because now the portal is able to cache all this published content, resulting in dramatically lower loads to Publisher and dramatically increased performance for end users.
Also of note, this was actually an undocumented feature in 6.4, which was discovered by Fabien Sanglier. In fact, he even fixed the bug about all content not coming back. Ah, Fabien, always ahead of the times…
When you publish a document to the Knowledge Directory, it uses the description as the filename. (Issue #62669)
We’ve run into this one before – good to know that you no longer need to beg support for the critical fix!
Finally, the new Dojo Rich Text Editor includes a spell checker. Hit the link for a screen shot of that wonderful piece of functionality in action.
Meh, who needs spell check anyway? If I ever figure out what’s up with this thing, I’ll post the fix!
