This post documents Sitecore's ParseReferrer pipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
This post documents Sitecore's CreateVisit pipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
This post documents Sitecore's TrafficTypes pipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
This post documents Sitecore's ExcludeRobots pipeline and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
This post documents Sitecore's CreateTracker pipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
This post documents Sitecore's StartAnalytics pipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
This post documents Sitecore's StartTracking pipeline, and is part of a series providing information on all the pipelines and processors in involved in a Sitecore 8 request . It's not a line by line account, but all the key logic is described.
I have compiled a list of every pipeline and processor in Sitecore 8 that runs directly as a result of an HTTP request and presented them in the order they occur.
Sitecore users and developers occasionally ask how to find out when an item was most recently published or when it was first published. Unfortunately, the answer isn't as simple as you might assume.
This post outlines a method of selecting different processors in the httpRequestBegin pipeline depending on the context site. (Edit: John West has now expanded on this idea , with an approach that does not require a 'parent' processor)