Skip to main content

Posts

Showing posts from March, 2013

Try the wall with Padlet, it is fun

See my wall :::-) Created with Padlet
Post a Comment
Read more

Content Type Hub - It's hard to say I love you

Recently some other developers suggested using content type hub for a client project and it created massive overhead: Added complexity for deployment Lots of errors from content type publishing Lookup fields are not supported and we have to use metadata fields, again.. more overhead. My suggestions for anyone what to try content type hub: Do NOT use it if there's no requirement to consume content types by multiple web applications Do NOT use it even you need simular content types in different web applications but you need different customization
Post a Comment
Read more

How to get HTML5 working in IE and Firefox 2

HTML 5 may be the latest and greatest technology, but some browsers don’t have native support for the new semantic elements. Let’s momentarily forget about the really sexy functionality, like full control over the <video> element , and just focus on getting the elements rendered. The problematic A-grade browsers include IE 8 and below, Firefox 2, and Camino 1 (these last two browsers both use the Gecko rendering engine, which is why they’re both affected). Let’s start with Internet Explorer. IE doesn’t believe in HTML 5 elements Quite simply, IE doesn’t even see HTML 5 elements, much less style them. This is actually the same issue that we had before HTML 5, where the <abbr> element couldn’t be styled in IE 6, resulting in all manner of workarounds . (Let me add that we’ll also fix the <abbr> element while we convince IE to recognise HTML 5 elements). The fix There is hope! The trick, discovered by Sjoerd Visscher , is simply to create the ...
Post a Comment
Read more

SharePoint 2013: Unexpected response from server issue and how to fix

From time to time when you do some operations such as search using SharePoint 2013 you may see the following error: Unexpected response from server. The status code of response is ’500′. The status text of response is ‘System.ServiceModel.ServiceActivationException’ After having this issue on newly installed SharePoint 2013 farm in production environment, I figure it out that Single server is running out of memory. Especially, thanks to one new process noderunner.exe. Noderunner.exe is the new executable of search service on SharePoint 2013. This process can’t turn it off because Search is one of essential service application in SharePoint 2013, and it is integrated in many features. So, there are some things you can do to reduce the impact of Search on your system. Solution 1 Reduce the Search Service Performance Level with this PowerShell command: Set-SPEnterpriseSearchService -PerformanceLevel Reduced or Set-SPEnterpriseSearchService -PerformanceLevel PartiallyReduced,...
Post a Comment
Read more