Abobe CQ 5.6 : Sitecatalyst load event firing twice in certain browsers | Community
Skip to main content
Level 3
October 16, 2015
Solved

Abobe CQ 5.6 : Sitecatalyst load event firing twice in certain browsers

  • October 16, 2015
  • 5 replies
  • 1347 views

Hi All,

I have a very peculiar problem with site catalyst events. On firefox and IE  browsers, load event is fired 2 times for every page and 1st request has incorrect page name ( content:xyz:page1). I have done mapping in SC Framework in CQ to map pageName property to page.title. Second request has correct page name. When i tried debugging it, i found that storeinitialize event is getting fired twice from kernel.min.js line 540. I am not sure why it is getting fired twice. This issue does not happen on every page load, using firebug on firefox i found it is happening 3 out of 5 time on mozilla. Any help in troubleshooting this issue will be helpful.

Regards,

Mayank

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Sham_HC

Hi Mayank,

I am guessing you have single SiteCatalyst event mapped to two events in different components & page events. Hence triggering multiple times.

Thanks,

Sham

5 replies

smacdonald2008
Level 10
October 16, 2015

This sounds like a bug as opposed to a configurable setting. Please file a ticket here: http://helpx.adobe.com/marketing-cloud/experience-manager.html.

October 16, 2015

Hello Mayank,

We are having pretty much the same issue, the sitecat events are getting loaded twice one with the correct info and other with content:name:pagepath.

Can I get some information regarding the solution for this please?

 

Thanks

Pranaya

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

Hi Mayank,

I am guessing you have single SiteCatalyst event mapped to two events in different components & page events. Hence triggering multiple times.

Thanks,

Sham

Level 3
October 16, 2015

Hello Pranaya,

After Sitecat script at the end of page, there is <noscript> tag, in my case somehow <noscript> tag was not formed properly, javascript comment just above it was not getting closed properly which made <noscript> tag to malformed and to run on every page load event. Eventually i had to remove suite informaiton from my sitecat config so that <noscript> code is not executed. It was very weird issue since <noscript> code is coming from OOTB analytics component and on one site, on same CQ instance, it is working fine but on second site it gave us this issue. Let me know if above explanation helps, if you need any screenshot of what i am referring to, i can send you those as well.

Regards,

Mayank

Level 3
October 16, 2015

I also thought so initially but we have one site on same instance and it does not fire load event twice. Hence i do not think its a product issue. I did further analysis and i saw a warning message in console (EventData Store is not defined util.min.js line 111) when ever load event is fired twice.