First phrase - first step

So lets blogging... :)

Comments

Post a Comment

Popular posts from this blog

Client-side scripting for Taxonomy/Term Set Fields

    I haven’t found any way of how to attach to onchange event of term store fields for the edit/new forms, so I had to spend a couple of hours on reverse engineering of WebTaggingDialog.js and ScriptForWebTaggingUI.js and in piece of HTML which represents SharePoint FormField for Taxonomy field.      So, in HTML this field is bound as a set of spans, divs, hidden field and image to open WebTaggingDialog.aspx:   < SPAN id =ctl00_MyTaxonomyFieldID_ctl00_ctl00>     < INPUT id =ctl00_MyTaxonomyFieldID_ctl00_ctl01 class ="ms-taxonomy ms-taxonomy-height ms-long" value =MyTaxonomyFieldValue|f0d123d1-ac8c-4a18-bccb-65c9b5ea83af type =hidden>     < DIV id =ctl00_MyTaxonomyFieldID_ctl00_ctl02 class ="ms-taxonomy ms-taxonomy-height ms-long" InputFieldId ="ctl00_MyTaxonomyFieldID_ctl00_ctl01" SspId ="68e138c4-5729-4ddd-ab0d-95c688c6c8eb" GroupId ="00000000-0000-0000-0000-000000000000" ...
Read more

Sitecore + Social Connected 2.1 + Twitter. System.OverflowException issue with TweetSharp library

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!
Read more

Some thoughts on using Sitecore Habitat for Production codebase

Image
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...
Read more