How long does it take to open a Sitecore node?

December 12, 2014 by boro

In Sitecore builds a lot of the focus during development and performance tuning is understandably around the customer facing experience. Recently we’ve needed to investigate performance issues within the CMS itself. If you’ve ever dug into this you’ll know its a tricky application to analyse as a lot of the interactions are client-side.

One metric we wanted to gather was ‘how long does it take to open up a sitecore node’? With the help of support they suggested digging into the js file which glues all this together: ‘\sitecore\shell\applications\content manager\content editor.js’.

If you add in the following log entries the chrome console should reveal all:

scContentEditor.prototype.onTreeClick = function(sender, evt) {
    console.time("GetTreeviewChildren");
    ...

scContentEditor.prototype.onTreeClick = function(sender, evt) {

console.time("GetTreeviewChildren");

...

and then to finish up:

scContentEditor.prototype.expandTreeNode = function(sender, result) {
  ...
  console.timeEnd("GetTreeviewChildren");
}

scContentEditor.prototype.expandTreeNode = function(sender, result) {

...

console.timeEnd("GetTreeviewChildren");

}

and

scContentEditor.prototype.collapseTreeNode = function(sender) {
  ...
  console.timeEnd("GetTreeviewChildren");
}

scContentEditor.prototype.collapseTreeNode = function(sender) {

...

console.timeEnd("GetTreeviewChildren");

}

Depending on your findings you have a few options for improving performance. Be sure to check you’ve set the pre-fetch cache sizes (/app_config/prefetch/master.config) and the master db cache sizes.

Customizing the Sitecore Rich Text Editor

December 2, 2014 by boro

You have several options when customizing the Sitecore Rich Text Editor. It’s simple to setup custom sets of buttons and assign to different templates. If you are unsure on doing this I’d suggest googling ‘sitecore custom rich text editor’. This post details how to use the ‘Html Editor Configuration Type’ items.

Within the application there are various global settings which configure things like default tags to use for line breaks, which profile to use as default and a few more:

<!--  HTML EDITOR DEFAULT CONFIGURATION TYPE
            Specifies the type responsible for setting up the rich text editor. Can be overriden at profile level. Must inherit from Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration,Sitecore.Client.
            Default value: Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration,Sitecore.Client
      -->
      <setting name="HtmlEditor.DefaultConfigurationType" value="Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration,Sitecore.Client" />
      <!--  HTML EDITOR DEFAULT PROFILE
            Path to the default html editor profile.
            Default value: /sitecore/system/Settings/Html Editor Profiles/Rich Text Default
      -->
      <setting name="HtmlEditor.DefaultProfile" value="/sitecore/system/Settings/Html Editor Profiles/Rich Text Default" />
      <!--  HTML EDITOR LINE BREAK
            Specifies the tag that the HTML editor inserts on Enter. Values can be
            "br", "div" and "p".
      -->
      <setting name="HtmlEditor.LineBreak" value="p" />
      <!--  HTML EDITOR REMOVE SCRIPTS
            If true, the rich text editor removes script tags from RTE field values before saving. Setting the value to true reduces the potential for cross-site scripting and other script-related issues.
            Default value: true
      -->
      <setting name="HtmlEditor.RemoveScripts" value="true" />
      <!--  HTML EDITOR SUPPORT WEB CONTROLS
            Indicates if the Html Editor supports web controls. If true, Web Controls are shown as yellow boxes.
            Default value: true
      -->
      <setting name="HtmlEditor.SupportWebControls" value="true" />
      <!--  HTML EDITOR VALIDATOR SERVICE URL
            Specifies the url that validates XHtml.
      -->
      <setting name="HtmlEditor.ValidatorServiceUrl" value="http://validator.w3.org/check" />

<!-- HTML EDITOR DEFAULT CONFIGURATION TYPE

Specifies the type responsible for setting up the rich text editor. Can be overriden at profile level. Must inherit from Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration,Sitecore.Client.

Default value: Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration,Sitecore.Client

-->

<!-- HTML EDITOR DEFAULT PROFILE

Path to the default html editor profile.

Default value: /sitecore/system/Settings/Html Editor Profiles/Rich Text Default

-->

<!-- HTML EDITOR LINE BREAK

Specifies the tag that the HTML editor inserts on Enter. Values can be

"br", "div" and "p".

-->

<!-- HTML EDITOR REMOVE SCRIPTS

If true, the rich text editor removes script tags from RTE field values before saving. Setting the value to true reduces the potential for cross-site scripting and other script-related issues.

Default value: true

-->

<!-- HTML EDITOR SUPPORT WEB CONTROLS

Indicates if the Html Editor supports web controls. If true, Web Controls are shown as yellow boxes.

Default value: true

-->

<!-- HTML EDITOR VALIDATOR SERVICE URL

Specifies the url that validates XHtml.

-->

The problem we ran into was that for certain rich-text-editors we wanted the line breaks to be br tags, elsewhere p tags. This ruled out the setting above.

One hidden feature which is very useful is the ability to setup different configurations for each rte. If you look in the folder in core ‘/sitecore/system/Settings/Html Editor Profiles/Rich Text Default’ you will see an item of type ‘/sitecore/templates/System/Html Editor Profiles/Html Editor Configuration Type’. Here you can define a type, the default mapped to ‘Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration,Sitecore.Client’

If you need to setup specific RTE’s to use br tags instead of p tags:

Setup your custom RTE profile in core
Create an item of type ‘/sitecore/templates/System/Html Editor Profiles/Html Editor Configuration Type’ called ‘Configuration Type’
Create a new class which inherits from ‘Sitecore.Shell.Controls.RichTextEditor.EditorConfiguration’
Update the ‘Configuration Type’ item to reference your new class
Override the methods you need – I found simply overriding SetupEditor was enough (see below).

An example of the code:

using Sitecore.Data.Items;
using Sitecore.Shell.Controls.RichTextEditor;
using Telerik.Web.UI;

namespace ###.SitecoreCustom
{
    public class CustomRichTextEditor : EditorConfiguration
    {
        public CustomRichTextEditor(Item profile) : base(profile)
        {
        }

        protected override void SetupEditor()
        {
            base.SetupEditor();

            Editor.NewLineMode = EditorNewLineModes.Br;
        }
    }
}

using Sitecore.Data.Items;

using Sitecore.Shell.Controls.RichTextEditor;

using Telerik.Web.UI;

namespace ###.SitecoreCustom

{

public class CustomRichTextEditor : EditorConfiguration

{

public CustomRichTextEditor(Item profile) : base(profile)

{

}

protected override void SetupEditor()

{

base.SetupEditor();

Editor.NewLineMode = EditorNewLineModes.Br;

}

Sitecore parallel publishing

November 28, 2014 by boro

In version 7.2 Sitecore introduced the ability to really crank up the publishing performance of the application. There is a lot more information about how to enable Sitecore parallel publishing at http://www.sitecore.net/Learn/Blogs/Technical-Blogs/Reinnovations/Posts/2014/03/Enabling-Parallel-Publishing.aspx

During testing it was found the time it took to publish was noticeably shortened. See here for some stats.

One uncertainty was exactly what does parallel publishing do behind the scenes? What does ‘parallel’ actually mean?

The setting MaxDegreeOfParallelism configures the number of threads to use
Languages are published concurrently
You don’t get any more publish queues by increasing the number of threads. This means you can only run 1 publish at a time still.
Publishing targets are published to in sequence – e.g. if you have 2 targets: web1 & web2 and publish to both, items will appear in web1 first, once complete items will then be pushed to web2
Be careful cranking things up too much – you need to ensure the servers in use can cope with the load. The dbs will be under a lot more strain during the publishes
For any diagnostics check in the new log file generated specifically for publishing

How to prove the targets run in series?

I ran a simple experiment to prove this:

Create 2 publish targets: web & web2
Create folder structure:
1. Parallel item (folder)
2. + item for web (only allowed to publish to web)
3. + item for web2 (only allowed to publish to web2)
Added custom publish item processor with Thread.Sleep(###)
Run publish with MaxDegreeOfParallelism set as 4
Check web db and check web2 db via dbbrowser

The data arrived:

Web 2a
Web 2b
Web2 2a
Web2 2c

The publish logs and the UI also indicate its one target after another.

1048 08:44:27 INFO Settings.Publishing.MaxDegreeOfParallelism:4

…

8588 08:44:45 INFO [Publishing]: Starting to process 2 publishing options

8588 08:44:45 INFO [PublishOptions]: root:{8960D17C-38F1-4DB0-8EBD-FD6B128D9E00}, language:en, targets:Web, database:web, mode:SingleItem, smart:False children:True, related:False

8588 08:44:45 INFO [PublishOptions]: root:{8960D17C-38F1-4DB0-8EBD-FD6B128D9E00}, language:en, targets:Web2, database:web2, mode:SingleItem, smart:False children:True, related:False

…

7040 08:44:46 INFO Starting [ParallelPublishing] – ProcessQueue

7040 08:44:46 INFO Processing queue

7040 08:45:46 INFO Processing re-try list (count=0)

7040 08:45:46 INFO Finished [ParallelPublishing] – ProcessQueue in 60354 ms

7040 08:45:46 INFO Publish Mode : SingleItem

7040 08:45:46 INFO Created : 2

7040 08:45:46 INFO Updated : 1

7040 08:45:46 INFO Deleted : 0

7040 08:45:46 INFO Skipped : 1

…

10136 08:45:46 INFO Starting [ParallelPublishing] – ProcessQueue

10136 08:45:46 INFO Processing queue

10136 08:46:46 INFO Processing re-try list (count=0)

10136 08:46:46 INFO Finished [ParallelPublishing] – ProcessQueue in 60101 ms

10136 08:46:46 INFO Publish Mode : SingleItem

10136 08:46:46 INFO Created : 2

10136 08:46:46 INFO Updated : 1

10136 08:46:46 INFO Deleted : 0

10136 08:46:46 INFO Skipped : 1

Two submit buttons in Sitecore WFFM

November 19, 2014 by boro

We recently ran into an interesting challenge where the user wanted two submit buttons on their wffm form, the value of which then needed logging in the WFFM database. Note this approach does rely on javascript.

WFFM gives you the ability to setup custom fields (see Sitecore docs). I based this implementation on section 3.7.3

In your solution setup a custom ascx:

<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="CustomFormItem.ascx.cs" Inherits="###.Website.Forms.CustomFormItem" %>
<asp:HiddenField runat="server" ID="ButtonHiddenField" />
<script type="text/javascript">
    $scw(document).ready(function () {
        var hiddenField = $scw('#<%= ButtonHiddenField.ClientID%>')
        var submit = hiddenField.parentsUntil('#MainPanel').find(':submit');
        var clone = submit.clone(true);
        clone.attr('value', '<%=Title%>');
        clone.click(function() {
            hiddenField.val('<%=Title%>');
        });
        submit.click(function() {
            hiddenField.val('<%=DefaultButtonText%>');
        });
        clone.appendTo(submit.parent());
    });
</script>

<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="CustomFormItem.ascx.cs" Inherits="###.Website.Forms.CustomFormItem" %>

<asp:HiddenField runat="server" ID="ButtonHiddenField" />

$scw(document).ready(function () {

var hiddenField = $scw('#<%= ButtonHiddenField.ClientID%>')

var submit = hiddenField.parentsUntil('#MainPanel').find(':submit');

var clone = submit.clone(true);

clone.attr('value', '<%=Title%>');

clone.click(function() {

hiddenField.val('<%=Title%>');

});

submit.click(function() {

hiddenField.val('<%=DefaultButtonText%>');

});

clone.appendTo(submit.parent());

});

</script>

and then the code behind:

using System;
using System.Web.UI;
using Sitecore.Data.Items;
using Sitecore.Form.Core.Controls.Data;
using Sitecore.Form.Web.UI.Controls;

namespace ###.Website.Forms
{
    public partial class CustomFormItem : ValidateUserControl, IHasTitle
    {
        protected void Page_Load(object sender, EventArgs e)
        {

        }

        public string DefaultButtonText
        {
            get 
            { 
                Item item = Sitecore.Context.Database.GetItem(Form.FormID);

                if (item != null)
                {
                    return item.Fields["Name"].Value;
                }

                return "default button";
            }
        }

        public override ControlResult Result
        {
            get { return new ControlResult("Custom Button", ButtonHiddenField.Value, "parameters"); }
        }

        protected override Control ValidatorContainer
        {
            get { return new Control(); }
        }

        protected override Control InnerValidatorContainer
        {
            get { return new Control(); }
        }

        public string Title { get; set; }
    }
}

using System;

using System.Web.UI;

using Sitecore.Data.Items;

using Sitecore.Form.Core.Controls.Data;

using Sitecore.Form.Web.UI.Controls;

namespace ###.Website.Forms

{

public partial class CustomFormItem : ValidateUserControl, IHasTitle

{

protected void Page_Load(object sender, EventArgs e)

{

}

public string DefaultButtonText

{

get

{

Item item = Sitecore.Context.Database.GetItem(Form.FormID);

if (item != null)

{

return item.Fields["Name"].Value;

}

return "default button";

}

public override ControlResult Result

{

get { return new ControlResult("Custom Button", ButtonHiddenField.Value, "parameters"); }

}

protected override Control ValidatorContainer

{

get { return new Control(); }

}

protected override Control InnerValidatorContainer

{

get { return new Control(); }

}

public string Title { get; set; }

}

You then need to create the custom field within Sitecore. This wants to live in ‘/sitecore/system/Modules/Web Forms for Marketers/Settings/Field Types/Custom’. The only field you need to set is the UserControl field. In my example this was /forms/customformitem.ascx.

When you setup your form you can then select:

In the front end this looks like:

And finally, when you submit you get:

Sorry mr a@b.com!, you might receive a few test signups 🙂

Summarising the Sitecore log

November 4, 2014 by boro

The Sitecore log analyser is a great tool for viewing patterns in log files over time.

If getting access to log files is slow or you simply want a quick summary of certain log files then hopefully the following might help. You can select the date range, filter terms and then view all log entries which fulfil that pattern.

I’d consider it to live in the same realm as the ‘/sitecore/admin’ pages as it can reveal critical site information (hence the admin check).

The front end isn’t the most glamourous but serves its purpose:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="LogViewer.aspx.cs" Inherits="###.Custom.LogViewer" %>

<!DOCTYPE html>

<html xmlns="http://www.w3.org/1999/xhtml">
<head runat="server">
    <title></title>
</head>
<body>
    <form id="form1" runat="server">
    <div id="LogViewerPanel" runat="server">
		Filter (| separate terms): <asp:TextBox runat="server" ID="FilterTextBox" Width="250"></asp:TextBox>
		Start Date (yyyy/MM/dd): <asp:TextBox runat="server" ID="StartDateTextBox"></asp:TextBox>
		End Date (yyyy/MM/dd): <asp:TextBox runat="server" ID="EndDateTextBox"></asp:TextBox>
		<asp:Button runat="server" Text="Go" OnClick="SearchClick"/>
	    <hr />
		<asp:TextBox runat="server" ID="ResultTextBox" TextMode="MultiLine" Width="1200" Height="600"></asp:TextBox>
    </div>
    </form>
</body>
</html>

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="LogViewer.aspx.cs" Inherits="###.Custom.LogViewer" %>

<!DOCTYPE html>

</head>

<body>

Filter (| separate terms): <asp:TextBox runat="server" ID="FilterTextBox" Width="250"></asp:TextBox>

Start Date (yyyy/MM/dd): <asp:TextBox runat="server" ID="StartDateTextBox"></asp:TextBox>

End Date (yyyy/MM/dd): <asp:TextBox runat="server" ID="EndDateTextBox"></asp:TextBox>

<asp:Button runat="server" Text="Go" OnClick="SearchClick"/>

<hr />

<asp:TextBox runat="server" ID="ResultTextBox" TextMode="MultiLine" Width="1200" Height="600"></asp:TextBox>

</div>

</form>

</body>

</html>

and then the code behind:

using System;
using System.Collections.Generic;
using System.Globalization;
using System.IO;
using System.Linq;
using Sitecore.Configuration;
using Sitecore.IO;

namespace ###.Custom
{
	public partial class LogViewer : System.Web.UI.Page
	{
		const string DateFormat = "yyyy/MM/dd";

		protected void Page_Load(object sender, EventArgs e)
		{
			LogViewerPanel.Visible = Sitecore.Context.User.IsAdministrator;
			
			ResultTextBox.Text = "";

			if (!IsPostBack)
			{
				StartDateTextBox.Text = EndDateTextBox.Text = DateTime.Now.ToString(DateFormat);
			}
		}

		protected void SearchClick(object sender, EventArgs e)
		{
			DateTime startDate = DateTime.ParseExact(StartDateTextBox.Text, DateFormat, CultureInfo.InvariantCulture);

			DateTime endDate = DateTime.ParseExact(EndDateTextBox.Text, DateFormat, CultureInfo.InvariantCulture);

			if (endDate < startDate)
			{
				Dump("End date must be after start date");
				return;
			}

			if ((endDate - startDate).Days > 7)
			{
				Dump("You can only pick a range of 7 days");
				return;
			}

			FindLogFiles(startDate, endDate, FilterTextBox.Text);
		}

		private void FindLogFiles(DateTime startDate, DateTime endDate, string filter)
		{
			Dump("Reading logs for: ", startDate.ToShortDateString(), " to: ", endDate.ToShortDateString(), " with filter: ", filter);

			List<DateTime> dates = new List<DateTime>();

			dates.Add(startDate);

			while (startDate < endDate)
			{
				startDate = startDate.AddDays(1);

				dates.Add(startDate);
			}

			string logFolder = FileUtil.MapPath(Settings.LogFolder);

			DirectoryInfo di = new DirectoryInfo(logFolder);

			string logFilePrefix = "log";

			List<FileInfo> validLogFiles = new List<FileInfo>();

			foreach (FileInfo fi in di.GetFiles(logFilePrefix+"*"))
			{
				if (fi.Name.ToLower().StartsWith(logFilePrefix))
				{
					foreach (DateTime dateTime in dates)
					{
						if (fi.Name.StartsWith(logFilePrefix + "." + dateTime.ToString("yyyyMMdd")))
						{
							validLogFiles.Add(fi);
						}
					}
				}
			}

			ShowLogEntries(validLogFiles.Distinct().OrderBy(a=>a.Name), filter);
		}

		private void ShowLogEntries(IEnumerable<FileInfo> files, string filter)
		{
			foreach (FileInfo fileInfo in files)
			{
				Dump("");
				Dump("Reading: ", fileInfo.Name);

				string content = FileUtil.ReadFromFile(fileInfo.FullName);

				string[] filters = filter.Split(new [] {'|'}, StringSplitOptions.RemoveEmptyEntries);

				int lineNumber = 0;

				foreach (string line in content.Split(new [] {'\r', '\n'}))
				{
					foreach (string filterPart in filters)
					{
						if (line.Contains(filterPart))
						{
							Dump(lineNumber, "--", line);
						}
					}

					lineNumber++;
				}

				Dump("------------------------------------------------------");
			}
		}

		private void Dump(params object[] values)
		{
			ResultTextBox.Text += String.Concat(values) + "\r\n";
		}
	}
}

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

using System;

using System.Collections.Generic;

using System.Globalization;

using System.IO;

using System.Linq;

using Sitecore.Configuration;

using Sitecore.IO;

namespace ###.Custom

{

public partial class LogViewer : System.Web.UI.Page

{

const string DateFormat = "yyyy/MM/dd";

protected void Page_Load(object sender, EventArgs e)

{

LogViewerPanel.Visible = Sitecore.Context.User.IsAdministrator;

ResultTextBox.Text = "";

if (!IsPostBack)

{

StartDateTextBox.Text = EndDateTextBox.Text = DateTime.Now.ToString(DateFormat);

}

protected void SearchClick(object sender, EventArgs e)

{

DateTime startDate = DateTime.ParseExact(StartDateTextBox.Text, DateFormat, CultureInfo.InvariantCulture);

DateTime endDate = DateTime.ParseExact(EndDateTextBox.Text, DateFormat, CultureInfo.InvariantCulture);

if (endDate < startDate)

{

Dump("End date must be after start date");

return;

}

if ((endDate - startDate).Days > 7)

{

Dump("You can only pick a range of 7 days");

return;

}

FindLogFiles(startDate, endDate, FilterTextBox.Text);

}

private void FindLogFiles(DateTime startDate, DateTime endDate, string filter)

{

Dump("Reading logs for: ", startDate.ToShortDateString(), " to: ", endDate.ToShortDateString(), " with filter: ", filter);

List<DateTime> dates = new List<DateTime>();

dates.Add(startDate);

while (startDate < endDate)

{

startDate = startDate.AddDays(1);

dates.Add(startDate);

}

string logFolder = FileUtil.MapPath(Settings.LogFolder);

DirectoryInfo di = new DirectoryInfo(logFolder);

string logFilePrefix = "log";

List<FileInfo> validLogFiles = new List<FileInfo>();

foreach (FileInfo fi in di.GetFiles(logFilePrefix+"*"))

{

if (fi.Name.ToLower().StartsWith(logFilePrefix))

{

foreach (DateTime dateTime in dates)

{

if (fi.Name.StartsWith(logFilePrefix + "." + dateTime.ToString("yyyyMMdd")))

{

validLogFiles.Add(fi);

}

ShowLogEntries(validLogFiles.Distinct().OrderBy(a=>a.Name), filter);

}

private void ShowLogEntries(IEnumerable<FileInfo> files, string filter)

{

foreach (FileInfo fileInfo in files)

{

Dump("");

Dump("Reading: ", fileInfo.Name);

string content = FileUtil.ReadFromFile(fileInfo.FullName);

string[] filters = filter.Split(new [] {'|'}, StringSplitOptions.RemoveEmptyEntries);

int lineNumber = 0;

foreach (string line in content.Split(new [] {'\r', '\n'}))

{

foreach (string filterPart in filters)

{

if (line.Contains(filterPart))

{

Dump(lineNumber, "--", line);

}

lineNumber++;

}

Dump("------------------------------------------------------");

}

private void Dump(params object[] values)

{

ResultTextBox.Text += String.Concat(values) + "\r\n";

}

GetItem on unpublishable Sitecore items

October 22, 2014 by boro

Consider the following code:

Item rootItem = master.GetItem(new ID(id), Language.Parse(language));

1	Item rootItem = master.GetItem(new ID(id), Language.Parse(language));

All pretty straight-forwards. It knowingly uses the master db as its only needed within the cms realm.

How about if the item in question in unpublishable? What then happens? You get null!!?? So, how to actually get the item?

bool disableFiltering = Sitecore.Context.Site.DisableFiltering;
Sitecore.Context.Site.DisableFiltering = true;
Item rootItem = master.GetItem(new ID(id), Language.Parse(language));
Sitecore.Context.Site.DisableFiltering = disableFiltering;

bool disableFiltering = Sitecore.Context.Site.DisableFiltering;

Sitecore.Context.Site.DisableFiltering = true;

Item rootItem = master.GetItem(new ID(id), Language.Parse(language));

Sitecore.Context.Site.DisableFiltering = disableFiltering;

If you wanted to expand the idea and make it a bit more reusable you could build a disposable switcher to apply the same changes.

Hopefully this helps as it had me stumped for a while!

Sitecore event handlers

October 17, 2014 by boro

One very useful area of Sitecore is the ability to subscribe to system events. Examples are things like when items are saved (item:saved), items are published etc.

All the out the box events can be seen within the <events> section of the config.

You can subscribe to events via config:

<configuration xmlns:patch="http://www.sitecore.net/xmlconfig/">
	<sitecore>
		<events>
			<event name="cta:saved">
				<handler type="###.Shell.Events.CtaItemSaveHandler, ###" method="SaveCtaItem" />
			</event>
		</events>
	</sitecore>
</configuration>

</event>

</events>

</sitecore>

</configuration>

and raise your own custom events via:

Event.RaiseEvent("cta:saved", new object[]
					{
						context.Items[0]
					});

Event.RaiseEvent("cta:saved", new object[]

{

context.Items[0]

});

One thing to note, events such as item:saved will be run when sometimes you don’t expect it. Examples are package installations.

You can guard against custom event handlers running during package installations if you check for the existence of the current httpContext:

class MyEventHandler
{
    void ProcessEvent(...)
    {
        if (HttpContext.Current == null)
        {
            return;
        }

        //code to process event...
    }
}

class MyEventHandler

{

void ProcessEvent(...)

{

if (HttpContext.Current == null)

{

return;

}

//code to process event...

}

For more info on how to make use of Sitecore events, have a look at http://sdn.sitecore.net/Articles/API/Using%20Events.aspx

Sitecore pipeline groups

September 30, 2014 by boro

Recently we’ve (mvp’s) have been lucky enough to get hold of a copy of the technical preview of Sitecore 8. It’s worth noting that anything within this version is subject to change!

One thing that a few people noticed and asked about during the Symposium was some additional config options around pipelines e.g.:

<group groupName="FXM" name="FXM">
    <pipelines>
        <tracking.matchpages>
            ...
        </tracking.matchpages>

<tracking.matchpages>

...

</tracking.matchpages>

This group syntax was something I’d not seen before – read on to find out how it works.

If you want to then run the pipeline you simply need to include the “domain” in the call. This example is from the TrackingManager within the new FXM dll’s:

this.pipeline.Run("tracking.matchpages", matchPagesArgs, "FXM");

1	this.pipeline.Run("tracking.matchpages", matchPagesArgs, "FXM");

where this.pipeline is:

Sitecore.Abstractions.ICorePipeline

1	Sitecore.Abstractions.ICorePipeline

One of the cool additions to the new Abstractions dll!

public interface ICorePipeline
{
	void Run(string pipelineName, PipelineArgs args);
	void Run(string pipelineName, PipelineArgs args, bool failIfNotExists);
	void Run(string pipelineName, PipelineArgs args, string pipelineDomain);
	void Run(string pipelineName, PipelineArgs args, string pipelineDomain, bool failIfNotExists);
}

public interface ICorePipeline

{

void Run(string pipelineName, PipelineArgs args);

void Run(string pipelineName, PipelineArgs args, bool failIfNotExists);

void Run(string pipelineName, PipelineArgs args, string pipelineDomain);

void Run(string pipelineName, PipelineArgs args, string pipelineDomain, bool failIfNotExists);

}

Another addition in the Sitecore 8 otb setup is more structure to the app_config folder. It’s all too easy for this to become rather unruly so this form of segmentation is a nice addition.

Large number of Sitecore items per folder

July 23, 2014 by boro

Sitecore always recommend a limit of around 100 items per folder. After running some tests on 2 versions of a tree I can see why! Below are a few stats to back that up.

Before:

And after:

Then running some queries over all the descendant items revealed:

Nested folders (after)
Total: 341
Time to read: 639ms

Flat items (before)
Total: 336
Time to read: 1786ms

Its clearly much faster to access all the items even with just some simple nesting (roughly 80 items per folder) rather than 300+ in one folder.

Sitecore – lots of versions or lots of children?

July 23, 2014 by boro

The performance of your site can very quickly deteriorate if you are using a non bucket content structure and either the number of items in a folder bloats or the number of versions of an item bloats.

For a bit more reading on the number of items per folder see: Large number of Sitecore items per folder

These sql scripts allow you to quickly find the number of these offenders:
Children in a folder

SELECT TOP 1000 
	ParentID,
	COUNT(*) AS Total,
    (SELECT Name FROM [dbo].[Items] J WHERE J.ID = I.ParentID) AS Name
FROM [dbo].[Items] I
GROUP BY ParentID
ORDER BY Total DESC

SELECT TOP 1000

ParentID,

COUNT(*) AS Total,

(SELECT Name FROM [dbo].[Items] J WHERE J.ID = I.ParentID) AS Name

FROM [dbo].[Items] I

GROUP BY ParentID

ORDER BY Total DESC

Versions of an item

SELECT 
	COUNT(DISTINCT Version) AS VersionCount, 
	Language ,
	ItemID,
	(SELECT Name FROM [dbo].[Items] WHERE ID = VF.ItemId) AS Name
FROM VersionedFields VF
GROUP BY ItemID, Language
ORDER BY VersionCount DESC

SELECT

COUNT(DISTINCT Version) AS VersionCount,

Language ,

ItemID,

(SELECT Name FROM [dbo].[Items] WHERE ID = VF.ItemId) AS Name

FROM VersionedFields VF

GROUP BY ItemID, Language

ORDER BY VersionCount DESC

blog.boro2g .co.uk

Some ideas about coding, dev and all things online.

Category Archives: Sitecore

How long does it take to open a Sitecore node?

Customizing the Sitecore Rich Text Editor

Sitecore parallel publishing

Two submit buttons in Sitecore WFFM

Summarising the Sitecore log

GetItem on unpublishable Sitecore items

Sitecore event handlers

Sitecore pipeline groups

Large number of Sitecore items per folder

Sitecore – lots of versions or lots of children?