codeflood logo

Posts from 2014

Reusable JavaScript in SPEAK

In my previous post I showed how to extend existing SPEAK models and views when creating new SPEAK components so we can reuse what we've already got rather than duplicating wads of code. Reuse at the view and model level is good but it's only one part of the puzzle. What about reusing individual functions? To reuse arbitrary code in C# we can wrap that code up in a class which can be called by other code files by way of a using statement (and appropriate references in the project). But JavaScript doesn't really have a native way to allow including existing functions from another location in the current file. It's normally up to the host environment how to get other files loaded in before the current file.

Reusable SPEAK components

With the recent(ish) release of Sitecore 7.2 the greater Sitecore development community is finally getting their hands all over the shiny new SPEAK UI framework. SPEAK is a successor to Sheer UI and is intended to be used by all developers wanting to add functionality to a Sitecore instance. I've written this post against SPEAK 1.1 which is included in Sitecore 7.2. One of the strong design...

Revolver 2.2.2 Released

Two (and a half) weeks and two releases! This minor update for Revolver includes fixes to support shared session state. Shared session state occurs when an ASP.NET application is configured to store session state outside the memory of the ASP.NET application itself, or in other words, when InProc session mode is not used. With shared session state the objects stored in session need to be...

Revolver 2.2.1 Released

Revolver 2.2.1 has just been released and is now available over at codeflood. This is a rather small release to address 2 specific issues. You will find the downloads for the Sitecore package on the Revolver Download Page. The first issue addressed was a security concern in the Javascript of the Revolver client. Thanks goes to Marcin Okon of bwin.party who raised the concern and helped verify the...

Unique Item Name per Bucket

Last year I wrote a post on customising the URLs used to access items within an Item Bucket when using Sitecore 7+. The basic idea was that the structure of the bucket was completely ignored. So a URL for an item within a bucket would include the path to the bucket, then the item name. There was one important aspect of this approach that I deliberately ignored at the time of writing to keep the...