Let me say smth. ;)

Habitat is considered as a demo project to highlight HELIX principles on practice. While Sitecore don’t recommend using it for Production codebase, many sitecoreans still use it as a base for their Sitecore platform projects. There are some people against this and there are lots of supporters. Main arguments of supporters would be that Habitat looks good, have lots of inbuilt functionality and is continuously developed by GitHub community.  Opponents claim that it is bad of using something that is not recommended by the platform vendor. Apart from having some great features, habitat project comes with a set of npm/gulp scripts and free item synchronization framework (unicorn) that allows companies who are building their websites on Sitecore to save costs on early stages of a project. Your dev team would be grateful for having dev setup/deploy scripts that actually work from first attempt (assuming you have the right version of npm and gulp J ). Your finance direct...

You setup Social Connected module and configured your twitter app correctly? Getting authError parameter in the URL and System.OverflowException error in the log file? You’re definitely having an old TweetSharp library that causing this issue. Social Connected 2.1 uses TweetSharp library to communicate to Twitter API and there is a breaking change in twitter with user id that isn't targeted by this version of Social Connected. If you are running on SiteCore 7.2+ platform - you're safe as you can use 3.0 version which addresses the issue. If you're running on Sitecore up to 7.2, then you're in a little trouble, but don't worry too much as you can apply the following fix (at your own risk though :) ) Download Social Connected 3.0 Don't install it! Unpack the package Find TweetSharp.dll in the package and copy it over to your S itecore bin folder  Enjoy!

If you just need an answer - go to the last paragraph! :) Otherwise, you can read the full story how I found the solution. Today, I come across an interesting issue with Sitecore master database. I made some changes to the content tree and later on I decided to revert them and reset master database state to initial state. So, I asked my team to restore master db to the previous backup (that was taken a day ago). After a restore had been finished, we verified Content Editor and were so surprised to see items that we added just today. These changes shouldn't be there. So, I requested one more restore (just in case), I verified db backup file date - everything was alright, however changes still appeared in the Content Tree. So, I opened Items table in the Sitecore master database and then I understood what is wrong - these changes were not there, which means Sitecore takes them from somewhere else. Sitecore tends to cache a lot of information, so when you restore its' Master...