Yes please!
I did manage to sort of solve it, but it isn't ideal. I loaded up FrontPage and loaded the home page of the Project Portal into it for editing. I then explicitly added this line into the code:
<link rel="stylesheet" type="text/css" id="onetidThemeCSS" href="_themes/agile2-default/agil1011-109.css">
I also had to add the agil1011-109.css (which fortunately was still in my browser cache as I couldn't see where it was stored on the SharePoint server) in a sub folder _themes/agile2-default under the site in FrontPage. This ensured that the CSS class ms-vstsbanner was now implemented.
Once that was done everything returned to normal - at least for the main page of the Portal. Whether I need to do this for every page declared in the portal will remain to be seen.
Because this is regarded as a manual change to the page, any further change to the theme in SharePoint now retains the VSTS stylesheet reference and only adds the following line to indicate the SharePoint theme:
<meta name="Microsoft Theme" content="journal 1011, default">
As I said it is not ideal and really VSTS should better expose it's CSS styling either by explicitly declaring the theme in use in the _themes folder or more ideally integrating more naturally with SharePoint so that the VSTS theme is declared as one of the listed themes in SharePoint so you can easily return to it if you don't like your previous selection. I would have added the VSTS theme to SharePoint if I could only figure out a way of editing the spthemes.xml file as suggested by the MSDN documentation.
Still this is a v1 product. Hopefully a little more joined up implementation may come in a service pack or a v2.
Regards
Steve
|