XPages File Uploads and Editable Areas
As you dig deeper into XPages, sometimes you find strange behaviour. My approach (once I can reproduce it) is the same as with any complex problem I encounter in support. First I strip it down to the bare minimum and see if it still happens. Then I add, one by one, anything that's extra or more complex until I can isolate whatever is causing the problem. Or in the words of Sir Arthur Conan Doyle (from the mouth of Mycroft Holmes) "When you have eliminated the impossible, whatever remains, however improbable, must be the truth." In this case, I am implementing the file ...
Thematically Challenged – Best Practice for Dynamically Changing Themes in Xpages
For a while now one of the items on my wish-list of functionality to add to XPages has been the facility for the user to change the theme of an XPages application, possibly even for individual users to select a theme for their own experience. Currently, you need Domino Designer to change the theme for the web (fortunately now free, but still needing to installed). There is the option of assigning a stylesheet to each page (or a custom control on every page) that is computed based on a sessionScope or applicationScope variable. My first thoughts on this were to programmatically set the stylesheets ...
Workaround for Multi-Value Fields Bug
Tommy Valand posted on his blog yesterday and on the Notes 8.5 forum today a bug with multi-value fields. Basically save switches the output between a multi-value field and a semi-colon-separated string. Coincidentally I was working on an XPages application today, with a keyword form, for which I needed a multi-value field. Not surprisingly, I got exactly the same output. I don't know if it's something that's slipped into 8.5.1 or something that's been there since 8.5.0, but considering that it's consistent and unlikely to be resolved within the timescales required by my app, I set about trying ...
Update I've now got everything working, got answers to my last blog post, and worked out the various Domino version differences affecting this all. So before I continue with Option 3 and Option 4, here's an update on where we are. Option 1 used the out-of-the-box server-side validation for radio buttons, check boxes and multi-value list boxes. This was ok, but in 8.5.0 any custom validation error message you entered for these controls was not rendered to the user. I'm pleased to say this is resolved for 8.5.1. Option 2 used an extension to the RequiredValidator function ...
