How to Fix Recurring Meeting Workspace Error: ‘g_InstanceID’ is undefined

I was having a problem with Meeting Workspaces today.  The links to each meeting instance on the left Quick Launch were not working, and every time we clicked on one of them, we would get a JavaScript error: ‘g_InstanceID’ is undefined. 

At first, I assumed that my CSS must be hiding a control that was required for the navigation links to work.  Then I found a post by Mike Monjeau entitled MOSS – How to fix recurring Meeting Workspace error: ‘g_InstanceID’ is undefined that describes the fix for this.

Basically, when you use a master page other than default.master for a Meeting Workspace site, you can get this error.  If you add the following lines into your new master page, you can solve the problem:

  1. Add the following line of code under the <%@ Import Namespace=”Microsoft.SharePoint” %> tag:
    <%@ Register Tagprefix="Meetings" Namespace="Microsoft.SharePoint.Meetings" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %>
  2. Add the following line of code after the opening <body> tag:
    <Meetings:PropertyBag runat="server"/>

     

     

     

Double Quotes Silliness

I’ve been caught by this one more times than I’d like to count, so I wanted to post about it.  If you copy code (or any text for that matter) from the Web, it often may contain a double quote character.  There are actually two double quote characters, ” and ”.  See the difference?  (No, it’s not that obvious.)  The first quote is the one you are probably most used to seeing.  It’s ASCII character 34 (decimal), and is the one that is most often used in code.  The second is the right quote character, ASCII character 148 (decimal).

So, if you find some code out there that is supposed to solve your problem at hand, you copy and paste it in somewhere, and you start seeing even odder errors, check the quotes!

Question About My “Web Parts Falling Off the Page” Post and a Few Suggestions

I got another comment to my previous post about Web Parts falling off the page this morning that I can’t respond to due to the sender’s communication preferences, so I’ll answer it here.

Hi Marc,

With reference to your blog entry have you found any solutions to this weird problem. I am having the same problem. At first it was simply annoying and I thought maybe I am missing something. I feel pretty clueless at the moment.

I have custom pages built where a page has 2 DVWP, one is a category list and another is a product list view. Clicking on the first DVWP filters the product view. Clicking on a product takes you to another page. I have in all 69 subsites all of which have their own 2 precious lists. Since I migrated to the production box the custom page showed errors. I then figured that the ListIDs were different so I manually edited each of the sites to insert the correct ListID from SPD, checked the browser and they rendered correctly. Next time I browse the site, they are gone!!! I open it in SPD again and the DVWP code are completely gone.

Have you found any solution to your predicament that might help me out?

Many thanks,

MW

The quick answer is: No, I haven’t found a solution.  That said, it stopped happening.  That doesn’t give me any great comfort, though.

It sounds like MW is making nice use of DVWPs to generate dynamic content on pages.  Bravo!  However, I have several suggestions that could have saved MW a really large amount of time:

  • Instead of using the ListIDs in the DVWPs, he could have switched to ListNames.  From the sounds of it, all 69 subsites have the same two ‘precious lists’, I am assuming with the same names.  By changing to ListNames, there would have been no manual editing to match the GUIDs.
  • By storing the XSL in one central location, any changes to the two DVWPs could be made in one place, not 69.  Use the <xsllink> element to achieve this.

Office Application Compatibility with SharePoint

I’m often asked about the differences in Office 2003 and 2007 compatibility with SharePoint.  There’s an extremely detailed document on Microsoft’s site that explains it in ‘Good, Better, Best’ terms.  You can find the article entitled Microsoft SharePoint Products and Technologies Document: Microsoft Office Programs and SharePoint Products and Technologies Integration – Fair, Good, Better, Best at:
 
It even covers Office 200 and XP to some degree.
 
(I never can rememeber where it is, so this is as much a memo to me as anything else!)

Branding for _layout Pages in SharePoint

I got a comment on one of my earlier posts about SharePoint branding (the look and feel of sites, including colors, fonts, page layouts, etc.).  I couldn’t respond directly due to the person’s communication settings on their Live Space, so I thought I’d answer it here:

Marc,
Great blog, but I was wondering if you could fill in some gaps for me.  I move elements around in my custom master page and I want those changes applied to the application pages as well.  I have been trying to find out how to do that.  I didn’t rename or remove any pieces.  I only rearranged them or made them not visible on the page.  So how can I make those changes appear on the /_layouts pages?  Thanks for any help you can provide.

Pages in the _layouts directory are actually stored in the hive on the server’s hard disk rather than in the database.  Each page is available to all sites.  These pages also have a different master page (also stored in the hive) called application.master.  Therefore, when you make changes to default.master (Don’t change it directly — make a copy — you never know when you might need to go back!), those changes aren’t applied to the _layouts pages.

What you should do is to turn your CSS into a theme and apply that to your site.  This works because the theme is applied to all of the pages, including the _layouts pages.  Keep in mind that there are some CSS classes in application.master that don’t occur in default.master as well as some different constructs, so you may need to go back and forth a bit.