Why Won’t SharePoint Designer Recognize IE8? Firefox!

I loaded IE8 about a month ago and since then I’ve been getting the error below after I check in a page.  First, the usual message that the page needs to be approved:


If I choose ‘Yes’, I get the error: “A World Wide Web browser, such as Windows Internet Explorer, is required to use this feature.”, as below:


I did some surfing, and I’m not the only one seeing this behavior.  Others are seeing it in other instances that actually prevent them from accomplishing the task at hand.  My guess is that it is a bug, since IE8 is still in Beta.  The workaround is simple in this case: Just keep a browser window open to Galleries/Master pages and page layouts/My Submissions view in the Site Settings (http://[servername]/_catalogs/masterpage/Forms/my-sub.aspx).  This is the page that SharePoint Designer sends you to, which is convenient, but hardly a show-stopper if you can’t get there automagically.

UPDATE 2009-04-10: Well, IE8 is fully released now, and I’m still seeing this issue.  I still haven’t solved it with all my poking around and I’m still just working around it.  Anyone out there found a solution?

UPDATE 2009-04-19: Found the answer in a discussion that covered this message from a different angle.  The problem had nothing to do with SharePoint Designer or IE8, per se.  I had Firefox installed on my machine so that I could test how pages look in it, and somehow it was registered as the default program for something that SharePoint Designer must not have liked.  By uninstalling Firefox, the problem went away.  When I reinstalled Firefox (I still wanted it), I simply unchecked the option for Firefox to be the default browser, and all was good.  Simple solution to an annoying problem!  Sorry to cast aspersions on IE8, as it didn’t really have much, if anything, to do with it.


SharePoint Document Library Headscratcher

Here’s a head-scratcher for you…

In a SharePoint Document Library where you have Versioning and Check In/Check Out enabled, when you first upload a document, the “save” button on EditForm.aspx is labeled “Check In” and saves and also checks the document in (good). On a subsequent edit of the metadata (properties), you’re forced to check the document out again (good), but the “save” button is labeled “OK” and doesn’t check the document in (maybe good, maybe bad). Now I can see where this is a good thing because the user might want to fiddle the document a few times before they check it in. But what if you want to be sure they check it in?

It surely is by design, but in this case, the design isn’t what we want!

We have over 20 Content Types stored in one list, and we don’t want to give up the great capability that is there out of the box where the EditForm.aspx is “Content Type aware”. (When you switch Content Type, the form automagically adjusts the columns.) So I was thinking about using script to add a new Check In button to replace the OK button.  I’ve already got a lot of script on the page (of course it’s a custom version of the form called EditFormCustom.aspx — never edit the original!) that enforces business rules around the metadata interdependencies.

Alternatively, I was also thinking of redirecting on every save to a dashboard page where the user could see all of their docs and their disposition (a la My Site) so that they could manage them there.

Any other ideas?  (Short of writing a lot of crufty C# code.)