The XPages Blog

Thankfully the list of XPage fixes we've added to 851 FP1 isn't as long as it was in 85 and the following are well worth mentioning all the same.

# PHAN7X8T85 | Problem with actions in nested custom controls:

Top of the list is this one and you're likely to hit this if your application uses nested custom controls. For example, you might have an edit document simple action in a custom control and this custom control is embedded in another, it might be in an Editable Area, and at runtime you find that have to click the action twice for it to perform the action. On some applications the action won't perform at all. So if you see this happening to your XPages application on a 851 runtime, apply FP1 to resolve this issue.

# MKEE7V9F82 | Browser Time Zone always shows GMT:

You'll only hit this bug if your application is set to use the browser's time zone (this is a setting you can enable in the Application Properties on the XPages tab and select 'Browser' for Time Zone) rather than the servers (default). This has been fixed in FP1.

# PHAN7WSQRP | Unable to call the Quickr API from XPages:

This is another issue resolved by FP1 and it should unblock you if your incorporating Quickr into your XPages application.

Hope this helps.

p.

Here are some additional details on the XPages fixes, 9 in all, you can expect in the Notes Domino 8.5 Fix Pack 1 fix list. You will see here that XPages will have a section all to itself. And all of these fixes have also made it into 851.

Most of the bugs were to do with view panels, with 'EGLN7NSDB7', 'MDOY7NYDNA', 'MDOY7NYW3N' and 'MDOY7MFVUY' all resolve issues one way or the other with categorized columns.

A fix through 'JGRT7PFTGG' allows you to use Java resources that come from a third party jars file, and so helping you extended any existing business logic in Notes applications.

A dash or a missing dash can cause you problems. Using the metaData control in 85 to specify a httpEquiv value generated the wrong HTML<meta httpEquiv="Content-Base">. This missing dash has been fixed through 'PRID7NBUJ3' so that the correct html is generated at runtime oin the browser -<meta http-Equiv="Content-Base">.

Controls added to the header and footer of a data table now display, fixed with 'PHAN7NXSAM'. And you shouldn't no longer see a problem with partial refresh on the Safari browser, this is fixed through 'PHAN7MLBSG'.

And finally, and my favourite, that Tabbed Panel bug 'PHAN7NXGLG'. You now don't have to use the worst workaround in the world where you had to 'review' each tab in order to submit all the data on the tabbed panel. This fix will come as a welcome relief to many including myself as you should now be able to use this container control to its full potential.

Here is the list as posted in the release notes for Fix Pack 1... 

XPages

• SPR# EGLN7NSDB7 - Problem with two views on one XPage - categories expand/collapse on both views at once
• SPR# MDOY7NYDNA - XPages category columns do not display any images specified via the iconSrc property
• SPR# MDOY7NYW3N - XPages view panel categorized columns cannot be hidden from display
• SPR# JGRT7PFTGG - Resources fail to load alling a 3rd party JAR from a XPage
• SPR# MDOY7MFVUY - Categorized columns in XPages ViewPanels only work when they are leftmost view columns and contiguous
• SPR# PHAN7MLBSG - Partial Refresh error with containers in Safari
• SPR# PHAN7NXGLG - The panels on Tabbed Panel need to be reviewed or reselected before data gets saved
• SPR# PHAN7NXSAM - Column headers and footers don't display in data tables
• SPR# PRID7NBUJ3 - Wrong http-equiv attribute generated

All the above fixes are in 8.5.1 (to be released in Q3 2009) along with quite a few more than the 9 listed in FP1. Needless to say I won't be writing up a report on all of these 851 fixes ;-)

p.