Tuesday, 19 May 2015

Issue with Embedding Yammer Feed in SharePoint 2010

On the 14th of May 2015, Yammer deployed an update to their Embed Yammer Feed script that stopped any Yammer Feeds on SharePoint 2010 from working.  In our case, the Yammer Feed got stuck on 'Loading...'

This error that is causing the Yammer Feed to fail to load is:
Object doesn't support property or method 'forEach' . yam-platform-feed-57f4f449766511e4f91eb519a39b2781.js, line 480 character 19099


The reason this is happening is because SharePoint Master pages have a line of code which forces all Internet Explorer Browsers to run in IE8 Compatibility Mode.  This is done to ensure all the ribbon & SharePoint functionality continues to work on new browsers.

The line of code in question:  <meta http-equiv="X-UA-Compatible" content="IE=8"/>

Hint: don't just remove this line of code!  you'll cause yourself a headache.

The line that Yammer & Microsoft are taking is that if you plan to stick to SharePoint 2010, the only way to use Yammer is to download the Yammer Web Part for SharePoint 2010 which is only being supported until March 15, 2016.  After that, you'd wanna not be on SP2010 anymore if you want Yammer functionality on your intranet.

Workaround to keep using Yammer Embed:

However, here's a workaround that may cater for your needs:  Wrap the compatibility code around around a SPSecurityTrimmedControl so that doesn't run in Compatibility mode when staff only have Read-Only Access.

<Sharepoint:SPSecurityTrimmedControl runat="server" Permissions="AddAndCustomizePages"><meta http-equiv="X-UA-Compatible" content="IE=8"/></SharePoint:SPSecurityTrimmedControl>

There's a few caveats with doing this though:  your site-admins cant see the feed, there may be other pieces of functionality that need IE in compatibility mode even for reading sites/pages.


REFERENCES:
http://www.markadrake.com/blog/2013/11/21/public-sharepoint-sites-and-ie8-compatibility

1 comment:

  1. Hi,
    I’m curious to know if you (or anybody you know) have implemented this work-around. Looking for more details about what will be impact of removing this piece of code entirely on my master page. Will it break any core SP functionality? If yes, which one? Thanks in advance!

    ReplyDelete