I’m currently preparing a Domino Designer 8.5 New Features demo. My plan is to take a quite old Notes DB (created 12 years ago under Domino 4.5 and never modified since) and show how to modernize it using 8.5 techniques. At one step I’m trying to apply a new .css resource that is part of the very database using a “local” theme, meaning that the theme also is part of the database. The theme in question dows nothing but load a .css file, and it is referenced in the db’s application properties.
In previous projects and demoes I used similar techniques to alter multiple properties at runtime using themes, and it always worked very nice. But not this time, and I really don’t have a clue why that would be. The only difference I’m aware of is that this is a different database from my previous attempts. I compared more or less every setting in the involved seems, StyleSheets and Aplication properties but can’t find anything that obviously could be the cause for the theme not being processed at all.
Would anyone have a clue where I could be looking for a solution? Is there maybe some incompatibility between older DB versions and theme features? ODS of the DB in question is 43, btw. This shouldn’t be a problem, since in the dbs from other demoes where ODS 43 as well.
Subject: Yep, I had it too taking a DB from beat to gold…
… and yesterday I did what you recommended: created a brand new db, then copied over the handful of views and the one form.
Result was stunning:
without applying even a single stylesheet or customized theme, the first versioof the db was rendered to html showing numerous dojo field effects; firebug indeed shows various css files coming from the xsp and dojo packages, but I swear that I didn’t apply one to the database
in the newly created db, all the dojo effects are gone. But themes still don’t render!
Just to make this complete: other databases running on the same server don’t show any of that strange behaviour: themes are rendered, no unexpected dojo etc. behaviour etc.
I also rebooted the entire server (it’s a test machine), restarted http task and refreshed the xsp cache many times - no change.