@Techphoria414 Blog

The Sitecore Page Editor: Unleashed

Tue, 15 May 2012 17:45:46 -0700

Today I had the honor of presenting once again to the Sitecore Users Virtual Group, this time on how to best utilize the Page Editor, as well as some helpful extensions.

The Webcast

The Example Code
You can download the full Visual Studio Solution used for this demo, including a version of the Dynamic Key Placeholder prototype updated for Sitecore 6.5 Update-4. The solution also includes TDS projects with the items needed to run the site.

The Page Editor: Unleashed Source Code

Other Helpful Resources

Sublayout Development with Custom Items and Scriptlets (as seen in example code)

StackOverflow: Create Content Folder

Converting Data Source Paths to IDs (John West)

Add Presentation Component Data Sources to the Links Database (John West)

Handling Presentation Component Settings (Adam Conn)

Dynamic Placeholder Keys (Original Article, including working pre-6.5 version)

Layout Deltas What Ifs (Adam Conn)

Programmatically Updating Layout Details (John West)

Advanced Database Crawler (Alex Shyba, as referenced with indexing data source content)

Cropper (screen capture tool)

TDS and Sitecore.* DLLs

Tue, 15 May 2012 08:40:09 -0700

One fail-safe feature of Team Development for Sitecore that has bit me a few times is its prevention of Sitecore.* DLLs from copying to your web root during a build. Though I appreciate TDS lookin out, there are times when you have non-module libraries, or modified Shared Source libraries, that you do want deployed on build. To work around this, you can utilize the BeforeFileReplacements build target. Place the following in your TDS csproj, just before the closing </Project>, and edit DeploySitecoreBinaries as needed for your assemblies.

<Target Name="BeforeFileReplacements">


<ItemGroup>
<DeploySitecoreBinaries Include="$(SourceWebPhysicalPath)\Bin\Sitecore.SharedSource.Search.dll;
$(SourceWebPhysicalPath)\Bin\Sitecore.Sharedsource.dll;
$(SourceWebPhysicalPath)\Bin\Sitecore.Sharedsource.PartialLanguageFallback.dll;" />
</ItemGroup>
<Copy SourceFiles="@(DeploySitecoreBinaries)"
DestinationFiles="@(DeploySitecoreBinaries->'$(_OutputPath)bin\%(RecursiveDir)%(FileName)%(Extension)')" />
</Target>

Sitecore Workflow Emails with rss2email

Thu, 05 Apr 2012 13:30:09 -0700

One of the coolest features added by Sitecore way back in 6.2 was Workflow RSS Feeds. My WeBlog cohort Alistair Deneys discussed them a bit back in 2009. I even recall at Dreamcore 2010, Michael Seifert feigning the approval of a press release onstage, using a workflow RSS feed on his smartphone. You can even setup RSS feeds in Outlook, which is a great option for PC users who deal with that wonderful piece of bloatware on a daily basis.

Workflow RSS feed links in the Workbox. You can see we're very busy moderating comments here at Techphoria414.

The content and functionality of the RSS feed is great -- it would take a lot of effort to reproduce it in a custom email action. The example below doesn't even show the field-by-field change comparison that's included when an item is updated.

Despite the possibilities with RSS, I feel this functionality is really underused. RSS after all these years is still a bit foreign to many non-technical users, and the reality is that in a business setting people aren't paying attention to RSS feeds in the same way they do their email. We even encountered a customer recently who couldn't add RSS feeds to their Outlook client because of a network group policy! So we set out to find a simple solution that allowed us to securely turn the content of the RSS feed into emails for our users. We found it in a cool little tool called rss2email.

Rss2email does just what it says -- translates an RSS feed into email. It's a small python script which you configure from the command line, then run on a scheduled basis. It's pretty simple to set it up for Sitecore Workflow RSS:

Download and Install Python 2.x
Download and unzip rss2email to a location of your choice, e.g. c:\rss2email.
Copy config.py.example, rename it to config.py and edit as needed. The settings I changed were:

DEFAULT_FROM (something like sitecore-no-reply@mydomain.com)
FORCE_FROM=1 (to ensure the default from address is always used)
SMTP_SERVER (obviously)

Edit r2e.bat to include an absolute path to python.exe. You could also place python.exe in your PATH.
Execute "r2e new <youremail>". This just gives r2e a default email address and creates its data file.
Get the URL of the workflow feed you wish to have emailed. Note: The feeds you pull from the Workbox are specific to each Sitecore user! Be sure to get your user to provide their own feed URL.
Execute "r2e add <feedurl> <useremail>". You likely will need to put the feed URL in quotes.
If you have a lot of existing items in the feed and want to avoid sending the user a slew of emails on first run, execute "r2e run --no-send"
Create a windows scheduled task that executes "r2e run" on a regular basis.

Your user will now receive an email for each new item entering the Workflow or Workflow State. I'm not giving the rss2email setup process justice, so be sure to reference the rss2email Getting Started guide. Once you have it running, the results are pretty great. In fact, the above screenshot was actually taken from my Google Mail account, not an RSS reader.

We have a small number of users who need these emails, so maintenance of r2e settings is not a huge issue. On a larger install, it would be interesting to find a way to adapt rss2email, or automate the addition/removal of users and their feeds. But quick and easy is what we were looking for, and this certainly delivered. Big thanks to Lindsey Smith for this tool.

Glimpse Debugging for Sitecore

Wed, 28 Mar 2012 09:44:08 -0700

While I have my gripes about the implementation of Sitecore.Context as essentially a repository for global variables, there is no doubt that the concept provides a great deal of the flexibility of the platform. But this flexibility can also create headaches in debugging. Context item, database, language, device... and further how they're used to construct and apply renderings. There's a lot going on in constructing just a single page. How can we securely expose information about the context to help debug published pages, even in production?

Glimpse is a debugging tool which espouses that "what Firebug is for the client, Glimpse does for the server." It securely and transparently adds a client-side debugging interface to your output pages.

Out of the box, Glimpse provides all kinds of information on what's going on with the server side of your ASP.NET Webforms or MVC application. What if we could extend this UI to include information about the Sitecore Context and other page information? The Glimpse site already provides a lot of great information on what Glimpse does and how to install Glimpse. It also provides a nice tutorial on its dead-simple plugin architecture.

To create a Sitecore plugin for Glimpse:

Install Glimpse using NuGet.
Create a new class library in your solution.
Reference Glimpse.Core, System.ComponentModel.Composition, and System.Web assemblies
Create a new class that implements IGlimpsePlugin
Mark your class with the attribute [Glimpse.Core.Extensibility.GlimpsePluginAttribute()]
Implement the GetData method to return a List of object arrays containing your debugging data
Implement the Name property to return the string "Sitecore"
Drop your new assembly into your Glimpse-enabled application

The result may look something like this:

click to enlarge

Download an example Glimpse plugin for Sitecore

You can either integrate this project with your solution if you'd like to make modifications, or include the built assembly as-is in your Glimpse-enabled project. It provides some basic information about the page, but I could certainly envision extending this to include more information, akin to the Sitecore Debug view.

Changing Item Templates With Sitecore PowerShell

Mon, 19 Mar 2012 22:12:38 -0700

So I'm starting to explore the Sitecore PowerShell Console module from Adam Najmanowicz, and I think the community could benefit from a few more example scripts. I'm working on some enhancements to WeBlog that will allow you to more easily use different templates for each blog, which required me to change the template of a large number of entries. PowerShell made this easy once I figured it out:

$master = [Sitecore.Configuration.Factory]::GetDatabase("master");
$entryTemplate = $master.Templates["YouPhoria/Blog/Entry"];
cd master:\Content\Home\Blog\;
Get-ChildItem -recurse | ForEach-Object { if ($_.TemplateName -eq "BlogEntry") { $_.ChangeTemplate($entryTemplate) } };

And there you go.

Obligatory note: You could also do this using Revolver, a command prompt module from my WeBlog partner in crime Alistair Deneys.

T414 Sitecore Best Practices Part 3: Sublayout Development with Custom Items and Scriptlets

Wed, 08 Feb 2012 14:55:13 -0800

The T414 Sitecore Best Practices Series is a screencast overview of the foundational pieces we use at Hanson Dodge Creative in our Sitecore development projects. Part 3 demonstrates our approach to creating Sublayouts using custom item classes (generated by the Custom Item Generator shared source module) and scriptlet-based user controls for efficient, clean Sitecore development that's Page Editor friendly. I've outlined this approach in a previous post as well.

Part 1: Introduction to TDS is available here.

Part 2: Solution Structure and Working with TDS is available here.

T414 Sitecore Best Practices Part 2: Solution Structure and Working with TDS

Tue, 07 Feb 2012 12:35:45 -0800

The T414 Sitecore Best Practices Series is a screencast overview of the foundational pieces we use at Hanson Dodge Creative in our Sitecore development projects. Part 2 dives into the specifics of Visual Studio solution structure, TDS project configuration, and using TDS.

Part 1: Introduction to TDS is available here.

Part 3: Sublayout Development with Custom Items and Scriptlets is available here.

UPDATE:
Sean Holmesby of Igloo Digital has a nice series of posts that also get into some details of TDS use and configuration, including some known "gotchas" that you may run into.

UPDATE #2:
If you're having trouble getting your Sitecore.* DLLs to copy on build, check this out.

T414 Sitecore Best Practices Part 1: Introduction to TDS

Mon, 06 Feb 2012 13:00:18 -0800

Over the next 3 days I'll be posting a series of screencast videos that demonstrate the standards and best practices we've developed for Sitecore projects at Hanson Dodge Creative. The foundational pieces of our standards include Team Development for Sitecore (TDS), the Custom Item Generator shared source module, and scriptlet-based sublayout development. Part 1 of the series is a shorter video providing a high-level introduction to TDS and the separation of development and web roots on your filesystem.

You can also view the Prezi that I created for this screencast.

Part 2: Solution Structure and Working with TDS is available here.

Part 3: Sublayout Development with Custom Items and Scriptlets is available here.

Happy Sitecoring,
Nick Wesselman / techphoria414

It's On: WeBlog Summit at Sitecore HQ

Thu, 06 Oct 2011 09:16:03 -0700

I'm excited to announce that in less than two weeks, I will be representing Hanson Dodge Creative at the WeBlog Summit in Copenhagen, Denmark at Sitecore HQ. Mark van Aalst, Alistair Deneys and I have been working on WeBlog (formerly EviBlog) for over two years now, each from our own corner of the world. Now, for the entirety of the third week of October, we'll be together in the same place, working toward our goal of creating world-class blogging functionality for Sitecore CMS. We are very grateful to Sitecore for hosting us and providing us access to the great minds they have amassed.

If you've ever had a feature idea for WeBlog, now is the time to let us know! Post your ideas to the WeBlog Forum on SDN.

- Nick Wesselman
@techphoria414

A Failsafe For non-Debug TDS Builds

Thu, 15 Sep 2011 16:43:27 -0700

Another advantage of Team Development for Sitecore is that deployment to your various environments can be configured as part of the Solution's Build Configurations, allowing you to easily deploy either right from your desktop or as part of an automated build process. The side effect of this is that if you don't remember switching to say, your QA server's build configuration, you can easily deploy in-progress code to an environment that's not your local machine. (I will not confirm nor disconfirm I've done this.) Though you probably don't want your production environment fully configured in TDS anyway, even a deploy to a QA or UAT server would be enough to get someone knocking on your door asking why "everything is broken."

We put together a quick failsafe to prevent this. You'll need to install the MSBuild Extension Pack. The example below assumes v4.0, x86. If the build is running in Visual Studio, and is anything other than a Debug build, a confirmation dialog appears that requires you to type in a super secret password before the build will continue. To add to your build, unload your TDS project, edit the .csproj, and paste in, perhaps near the bottom of the project config.

</Target>

<MSBuild.ExtensionPack.UI.Dialog TaskAction="Prompt" Title="Confirm Build" Button2Text="Cancel" Text="Type 'whiskey' below to confirm build to $(Configuration)">

</MSBuild.ExtensionPack.UI.Dialog>

</Target>

Illegal Characters in Path Exception in Sitecore Preview

Wed, 14 Sep 2011 12:43:36 -0700

Just filed a bug report with Sitecore Support. In case you are out there searching Google for the same exception, here's the issue. This is Sitecore 6.4.1 rev. 110720.

One of my developers accidentally applied Layout Details to a template, instead of its Standard Values. This used to work, even though it is not a best practice. When opening items based on the template, most of the time he would get the error below. This seems to be due to WebEditRibbon.ConvertToJson not finding the Layout Details on the template, then calling the wrong method on XmlDocument (Load instead of LoadXml).

[ArgumentException: Illegal characters in path.]
   System.IO.Path.CheckInvalidPathChars(String path) +142
   System.IO.Path.NormalizePath(String path, Boolean fullCheck, Int32 maxPathLength) +100
   System.IO.Path.GetFullPath(String path) +187
   System.Xml.XmlResolver.ResolveUri(Uri baseUri, String relativeUri) +131
   System.Xml.XmlTextReaderImpl..ctor(String url, XmlNameTable nt) +135
   System.Xml.XmlDocument.Load(String filename) +85
   Sitecore.Web.UI.WebControls.WebEditRibbon.ConvertToJson(String layout) +210
   Sitecore.Web.UI.WebControls.WebEditRibbon.Render(HtmlTextWriter output, Item item) +1268
   Sitecore.Web.UI.WebControl.Render(HtmlTextWriter output) +387
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +246
   System.Web.UI.HtmlControls.HtmlForm.RenderChildren(HtmlTextWriter writer) +315
   System.Web.UI.HtmlControls.HtmlContainerControl.Render(HtmlTextWriter writer) +48
   System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter)
   +11363410
   System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) +246
   System.Web.UI.Page.Render(HtmlTextWriter writer) +40
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint,
   Boolean includeStagesAfterAsyncPoint) +5290

The solution is simply to apply the layout details to the Standard Values, instead of the Template itself.

TDS and Sitecore.* DLLs

Mon, 12 Sep 2011 21:33:14 -0700

Quick one for you. If you're using TDS for Sitecore, you've no doubt run into the issue that any DLLs starting with Sitecore.* will not deploy. Though an admirable protection against deployment of core Sitecore DLLs, it can be an issue with Shared Source modules that are not installed through packages, or Sitecore.Support.* DLLs. The quick fix is to unload your TDS project and edit its .csproj, and add a BeforeFileReplacements event handler such as the following.

  <Target Name="BeforeFileReplacements">
    <!-- restore certain Sitecore.* DLLs that TDS refuses to copy -->
    <!-- BeforeFileReplacements will be called after TDS has deleted Sitecore.*
    from its Output, but before it deploys -->
    <ItemGroup>
      <DeploySitecoreBinaries Include="$(SourceWebPhysicalPath)\Bin\Sitecore.SharedSource.Search.dll;" />
    </ItemGroup>
    <Copy SourceFiles="@(DeploySitecoreBinaries)"
DestinationFiles="@(DeploySitecoreBinaries->'$(_OutputPath)bin\%(RecursiveDir)%(FileName)%(Extension)')" />
  </Target>

UPDATE 9/14/2011: Changed the name of the Item Group. It was deploying everything in the bin\ folder, including Sitecore.Kernel. I assume because the group name SourceWebBinaries was previously used by TDS.

Enjoy,
Nick / @techphoria414

Dynamic Placeholder Keys Prototype

Thu, 25 Aug 2011 00:09:30 -0700

Sitecore is undoubtedly putting increased effort and attention on the Page Editor as both an editing and design tool. This is evident in features such as the Unified Page Editor, layout deltas, and parameters templates. Sitecore 6.4 makes it very easy for a content editor to add a rendering to a placeholder, and even select or create a data source item for it.

However, a recent SDN post brought to light a limitation of the Sitecore layout engine that can make it difficult to build complex pages using placeholders and renderings. The poster posed a reasonable-sounding request, with a frustrating reality:

Sublayout A, has placeholder X.
Sublayout B, has placeholder Y.
Sublayout C, has no placeholder.

Within X on A, I want to place two instances of sublayout B. They are at the same level as each other, we'll call these B1 and B2. However I now want to put C into B2/Y. This can't be done however as the fully-qualified reference for B1/Y and B2/Y is the same, it will just go into B1/Y.

Just today, I had this very situation come up with one of our Information Architects -- how to construct an Accordion Sublayout, with multiple accordion folds, where each of which could contain their own unique content? This could perhaps be done through content heirarchy, perhaps using Presentation Inversion of Control to give some flexibility to the renderings inside the folds. But this is a Content Editor centric approach. Other folks on the thread above did suggest creating additional sublayouts with different placeholder names, but this is a hack and not intuitive to end users.

I don't believe there is a perfect solution currently, and I wouldn't be surprised if Sitecore is working the problem. In the mean time though, I've thrown together a quick prototype of a "wrapper" control for the Placeholder control that gives it a dynamic key. The basic idea:

Every rendering reference (a rendering assigned to a placeholder in Presentation Details) has a unique ID, though it's not displayed anywhere outside the layout XML.
Append that unique ID to keys of placeholders within the referenced Sublayout. This provides a unique value for the placeholder key that should remain constant. (As you can see in the code, obtaining that ID at the time Sitecore is constructing the page structure is a bit difficult.)
Supplement the getPlaceholderRenderings pipeline to treat the placeholder as if it didn't have a GUID appended to it, when looking for placeholder settings.
Utilize the Page Editor to construct pages -- you will not be able to easily construct pages using dynamic placeholder keys otherwise.

Download the prototype code

To try out the supplied code, you'll need to

Add and compile to your own assembly
Add GetDynamicKeyAllowedRenderings to the getPlaceholderRenderings pipeline
Add the namespace of the DynamicKeyPlaceholder class to system.web/pages/controls with a tag prefix of your choice
Utilize the DynamicKeyPlaceholder class in place of Placeholder in your sublayout, e.g. <xx:DynamicKeyPlaceholder Key="content" />
Setup your placeholder settings, fire up the Page Editor, and try it out...

A limitation remains that you cannot nest a Sublayout within itself. There is deeper code in Sitecore that prevents this. And sorry kids, can't help you with XSLT renderings here.

Let me reiterate that this is indeed prototype code. No guarantees, warantees, support or in-flight movie provided. But I'm very interested in feedback and other ideas. To keep the conversation going, please comment in the existing SDN thread.

Nick / @techphoria414

Sitecore Users Group Meetings

Fri, 13 May 2011 10:27:45 -0700

The next fortnight is bringing us two great opportunities to network with other Sitecore users and developers. First up, May 18th is the inaugural meeting of the Sitecore Users Virtual Group, sponsored by Hedgehog Development. The first meeting will be a question and answer session with the Sitecore ninja himself, John West. Registration can be found here and questions can be submitted for John here.

The following week, Hanson Dodge Creative is proud to to be hosting the May 2011 Sitecore Midwest Users Conference here in Milwaukee on May 24th. This user group meeting will have some great content from Sitecore, and an expansion of the WeBlog presentation I did at Dreamcore. If you are within shouting distance of Milwaukee, we hope you can make it. Registration can be found here.

-Nick

Dreamcore Day 2 Sessions and Wrap up

Wed, 20 Apr 2011 12:55:24 -0700

Well that's about it for Dreamcore. It all went by so fast. I'll do a separate (textual) entry when I get back to Milwaukee wrapping up our Dreamcore experience, but here's my video wrap-up. I had a great time and met a lot of great people. Wish we didn't have to wait a year to all get together again!

Also: Please give me some feedback on the video blog format. Would you be interested in ongoing Sitecore vblogs, perhaps with some screencast code samples or demos? Thanks folks.

Dreamcore Day 1 - Afternoon Report

Tue, 19 Apr 2011 17:37:31 -0700

Making some progress on this video blogging thing. Windows Live Movie Maker at least gives me a title screen and a quicker upload. Tonight: What happens in the Neighborhoods of Boston, stays in the Neighborhoods of Boston.

Dreamcore Day 1: Morning Report

Tue, 19 Apr 2011 13:01:26 -0700

For those not lucky enough to be with us in Boston, I'm trying something new at the Techphoria414 Blog, a little video report. The uhhh lighting sucks in my hotel room, and ummm my voice is hoarse from being sick. It's like you're really there!! Enjoy. No autotuning, please.

I'm a little surprised at myself for not mentioning ASP.NET MVC. Though they weren't specific, Lars and Kerry did indicate that Sitecore is committed to a deeper integration of MVC into Sitecore. w00t.

See you in Boston: Techphoria414 Dreamcore Preview

Sat, 16 Apr 2011 14:34:49 -0700

The second annual Dreamcore conference is upon us. It's a great opportunity for Sitecore geeks to gather, share best practices, and hear about the latest and greatest product developments coming out of Denmark. Last year's conference was very well done -- a great learning experience, and a great time. This year looks to be even better! Here are my highlights from the published agenda.

Quick Post: Dewplayer Not Loading in IE

Tue, 15 Mar 2011 21:03:40 -0700

A quick post for all you poor people who may encounter the same issue I do. I found a solution through Google, but it was in French. Hopefully you can find this in English.

I was testing out the Dewplayer flash mp3 player on our sister blog, you-phoria, but it wasn't working in IE. Here's the markup that I used, generated from the Dewplayer homepage. Can you see the issue?

< object type ="application/x-shockwave-flash" data ="/mp3/dewplayer-bubble.swf?mp3=/mp3/07-STS9-Mobsters.mp3" width ="250" height ="65" id ="dewplayer" name ="dewplayer"> <param name="wmode" value="transparent" /><param name="movie" value="dewplayer-bubble.swf" /> <param name="flashvars" value="mp3=/mp3/07-STS9-Mobsters.mp3" /> </object>

Yup. I put Dewplayer in a different folder but only updated one of the paths, the data attribute. It still worked fine in Firefox and Chrome, but in IE it appeared to never finish loading. *facepalm*

Using ManagedFusion URL Rewriter with Sitecore

Mon, 14 Feb 2011 12:55:10 -0800

Perhaps a rare combination, but we recently encountered a project which required use of the Reverse Proxy functionality of the ManagedFusion Url Rewriter module. To play nice with Sitecore, you need to add a simple processor to the Sitecore HTTP Request pipeline. Read on for the code.

The Black Art of Sitecore Custom Data Providers

Mon, 03 Jan 2011 10:28:00 -0800

Having coded a few Sitecore data providers, and with the release of Hanson Dodge Creative’s data provider for the Bits on the Run Video CDN, I thought I would take the time to gather my thoughts and lessons on implementing custom data providers for Sitecore. There are many ways of integrating external data with Sitecore, but a data provider is one of the most powerful. You can get external data to display and behave as native Sitecore data -- to be browsed, rendered and related to other content within Sitecore. How cool is that? Developing custom data providers is a bit of a black art though – documentation is lacking, and the side effects of such a low-level integration are often unexpected. I’ve tried to capture various tips, HOWTOs, and gotchas here. I’ll also be keeping this entry updated as I come across other useful information.

Bits on the Run Sitecore Module

Mon, 03 Jan 2011 10:05:03 -0800

Over the holidays, Hanson Dodge Creative released our Sitecore shared source module for Bits on the Run, an online video platform. It allows videos hosted on the CDN to appear within the Sitecore Media Library. Check out the module home page and documentation for more information.

Two Quick Tips on Sitecore.Caching

Mon, 13 Dec 2010 13:19:17 -0800

There are two "gotchas" in using Sitecore.Caching that have come back to bite me for the last time. I'm going to write about them so that I don't forget -- and hopefully help you out too.

Sitecore Custom Items, and Sublayout Coding with Scriptlets

Fri, 10 Dec 2010 11:33:27 -0800

On a recent Sitecore project, our Sitecore team at Hanson Dodge Creative attempted a new coding style in our Sitecore Sublayouts, preferring <% scriptlets %> over controls, and making heavy use of Velir's Custom Item Generator as our Domain Model and View Model to avoid tag soup and reduce our dependency on Sitecore webcontrols for field rendering. Read on to find out the why's and the how's.

Sitecore Item Editor Tricks and ASP.NET MVC

Wed, 08 Dec 2010 16:01:39 -0800

In a recent Sitecore project we did at Hanson Dodge Creative, we had a need for custom Item Editors to allow users to search and select items from a legacy CMS database. The basic idea was to select content from the legacy CMS, store content IDs in Sitecore fields, and render the content within Sitecore sublayouts. The approach worked great, but we ran into some challenges (and their solutions) along the way with our Item Editors, which I wanted to share with the Sitecore community. We also made some good use of ASP.NET MVC to build the Item Editors. I'm a big fan of using MVC with Sitecore, so I thought I'd also take an opportunity here to show one great use of it.

Lots of good info here on creating Item Editors in Sitecore, so read on.

EviBlog Youphoria Branch

Sun, 21 Nov 2010 12:32:00 -0800

Today I'm releasing my updates to Mark van Aalst's EviBlog module for Sitecore. My version of the module is currently branched in the Shared Source repository. Since I developed the updates for a music blog I help run, the branch is named for the you-phoria blog.

http://svn.sitecore.net/EviBlog/Branches/youphoria/

The full installation package is also available.

11/22/2010 Update: Merged with trunk, thanks to @adeneys for the heads up on his updates for XSS protection and staged configurations.

Read on for more information...