How to enable/disable visits tracking from content database.

I has been ask by business to find out a way to not track internal visits – easy stuff – we can add internal IP, public IP into <excludedIPAddresses> node of Sitecore.Analytics.ExcludeRobots.config file.

 

It worked for a while. Then I has been ask to disabled only on CM, but     …sometimes 😉 . Marketers, usually don’t want to see internal traffic to be tracked, but from time to time they would like to test some functionalities and  to track visits.  Deploying each time a config file is not an option.

I thought, it would be nice to add some logic into  the same pipeline (excludeRobots) where we filter already IP to exclude.

Continue reading

How to track from where visitor downloaded a PDF file

For the Website owner it is important to know how the data is accessed in order to understand the flow. This information will be used in Website personalization process to optimize.  For the content page we can use Path Analyzer.  For media assets it is a different story.  In our case a visitor cans download from landing page, case study detail page and search results page. He has to find a way how to track in xDB all PDF downloads regardless from where the visitor access it.

Continue reading

How to exclude a list of specific items from Solr search results

I’m pretty sure that happens to you to look for items that match specific criteria except  few specific ones. We all have friends that don’t  know what they want, but they know what they don’t want. (I love you baby).

In my case, the client wanted a list of case studies specific to an  industry except those that the visitor already saw.  The first thought is to get results from Solr and then filter those already seen. But what about metadata that helps us implement paging, or just get  first 10 items ? Do we need another query ? Tee answer is to sent exclusion param with our query .

Continue reading

Switch Solr indexes

The content rendered on the Website should not be affected by index rebuild. A solution to that is to setup Solr in a way that it will rebuild an index in a separate core so that the rebuilding does not affect the search index that is currently used. Once the rebuilding and the optimization of the index completes, Sitecore switches the two cores, and the rebuilt and optimized index is used.

I will describe the implementation steps with Sitecore 8.2 and Solr 5.3.1. I don’t expect this to be different with newer version.

Continue reading

Sitecore 8.2 Rendering Issues

We experienced issues with shared layout on few of our pages. Presentation assembling seemed not following Presentation Detail Information Flow.

Based on Sitecore documentation this is a flow

rendering

 

  • SharedLayout option uses __Rendering field
  • FinalLayout option uses __Final Rendering field
  • Going from right to left, if a field has a layout delta, it goes to the field to its left to gather more presentation information.

After the investigation we noticed that on Save Button click in Experience Editor, the full share layout is saved and not the delta in __rendering fields. ( in case when a page is inheriting renderings from standards values).

Sitecore provided us with a patch. You can request one – the reference number is 144214