Wednesday 14 February 2018

Tracker.Current is not Initialized: sitecore

After setting up fresh sitecore instance, when we're trying to open page item for the first time in experience editor.
Then usually we get error as: "Tracker.Current is not initialized".

Generally we get this issue because of analytics. Here fixed this issue with alternative ways.

First one is just disable Tacking, and it will work fine. For that
 Goto "~/App_Config/Sitecore.config" and find <sites> node under this find site="website" and check if "enableTracking" is true then make it false.
 Great, now check it should work.


But the main issue is we didn't fixed this issue, actually we ignore this issue and now our sitecore instance will not do tracking.

So our goal is to enableTracking as true and page should be open in experience editor fot that
another alternative is -
  • Check mongoDB is installed or not?
  • Mongo service is running or not?
  • Find "~/App_Config/Include/Sitecore.Analytics.Tracking.config" and check
    • "Analytics.ClusterName" setting is correct or not?
    • "Analytics.Hostname" setting is correct or not?


  this solution is little bit complex but this way once fixed then in future our instance will tracking enabled.



Tuesday 6 February 2018

Default Values in Sitecore Configs


It will be great if we've idea about default values of configs Item in Sitecore, to do change on that.

Here I'm attaching the image for quick look.



Click here to get list of all the default value of Item in sitecore Config.



Happy Sitecore 😎