During the past few months now, I have been working mainly on the Sitecore Analytics. On one of our environment, our logs were being flood with an error. The error was “Failed to synchronize segments”. Even though the same issue was raised on the Sitecore Stack Exchange here, I will write up a summary or checklist if you want on how we got this issue fixed.
Sitecore Analytics Aggregators are pipelines required to emit data from MongoDB to the Reporting DB. The aggregators get executed every minute. This pipeline is responsible to aggregate the different values collected in the MongoDB, example, number of visits, goals triggered and so on, and push them the to SQL database.
Following my blog post about Sitecore Cache, I wanted to extend the current Sitecore Cache page to another level. Currently, the default cache page (http://yourdomain/sitecore/admin/cache.aspx) only allows you to clear all the cache. This may be a small post today but I’ll try to explain what is the Sitecore Cache Extension page.
Following my post on how to prevent Sitecore from tracking the user pattern, I am writing today on how to boost the user pattern programmatically. The reason I am writing this up is because there were some question about it on the Sitecore StackExchange and also, I had been given a task where I should boost the user pattern on certain conditions. So, let’s proceed.
Yesterday, I was implementing a module which reads from a file and then populate the Sitecore fields. The main issue I was facing is the datasources of the Treelist, MultiList, Droplink and so on. The query in the datasources were complexed.
Following the past few days, I have been working on a proof of concept which is based on the Sitecore Pattern Cards. The concept of Pattern Cards is to map profile values to specific types of visitors and implement personalization rules.
Sitecore Publishing Service (SPS) is a great module designed by Sitecore. The SPS module provides an enormous gain in publishing performance. Large number of items including media items can be published in less than 10 mins. You may read my previous post on the installation of the Publishing Service 1.0 here.