Resolve Context Language based on Geolocation

Sitecore Language resolver didn’t change much since I am working with Sitecore. I remember John West blog post explaining the order of resolution.

  1. The sc_lang query string parameter.
  2. The language prefix in the path in the requested URL.
  3. The language cookie associated with the context site.
  4. The default language associated with the context logical site.
  5. The DefaultLanguage setting specified in web.config.

But what if I would like to change it ?

  1. The sc_lang query string parameter.
  2. The language prefix in the path in the requested URL.
  3. The language cookie associated with the context site.
  4. The language corresponding to visitor IP – using Geolocation service 
  5. The default language associated with the context logical site.
  6. The DefaultLanguage setting specified in web.config.

Continue reading

Sitecore compliance with GDPR- Part III

In  my previous blogs about General Data Protection Regulation (EU GDPR) –  Sitecore compliance with GDPR- Part III – I wrote about compliance at large. Then in Sitecore compliance with GDPR- Part II  a closer look how should be done in Sitecore. This time, I would like to go a little bit deeper – prevent Sitecore from tracking visitor action in session.

Continue reading

xDB Cloud service REST API explained

How to use REST API reference for the xDB Cloud service is described well here. But for someone it will use it for the first time may not be that obvious. Here is a description “for dummies”.

First we have to obtain valid authentication token to make a call to xDB Cloud API. it must to be included as a HTTP header in all requests. Here are a description of this call.  I use Fiddler as a tool.

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

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