The Baretta

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, th...

Here's an error message I received a few weeks back from a user who was having trouble accessing a page: Strange... Anyhow, my first thought was - Faulty Web Part - so made my way to SharePoint Designer to fix/remove the web part from the page, only to find that I was unable to connect to any sites on the entire Web Application! Here's the Error I was receiving when trying to access SharePoint Designer: "An error occurred while trying to fetch data from your SharePoint site. Attempted to read or write protected memory. This is often an indication that other memory is corrupt" Now I'm thinking 'oh shit..' well not to worry, all I needed to do was a simple IISRESET and the issue was resolved.

I feel like there are many sites/blogs/articles etc that list all the wondrous things that InfoPath can do.  They praise how user friendly it is for non-coders, how quick it is to design forms in comparison to Adobe & Visual Studio.  What none of them tell you is that if you want to design a code-less InfoPath form, you are severely restricted in many areas that you wouldn't realise, until of course you need to implement that functionality. "Why would you need to stick to a code-less InfoPath form?" you ask?  Well, in our organisation, the reason is simple.  We plan on creating many automated forms, and we plan on pushing them out to the various departments so that they can administer small changes themselves, only asking for help when they need technical advice. So as a coder who knows what can be achieved with a cheeky bit of C# here and there, I am going to list of issues I've found while trying to create a code-less form: ...