Adobe Experience Manager Sites & More

Report · 10/15/15

By adding the clientcontext as required by analytics integration, I get 404's for twitterprofiledata, fbprofiledata, fbinterestsdata in the path /etc/clientcontext/default/contextstores/ even though I am not doing any FB or Twitter integration?

Is there some other workaround to stop the clientcontext directory on my publish instance call fbprofiledata etc?

smacdonald2008 · 10/15/15

Here is the AEM Client Context documentation:

http://dev.day.com/docs/en/cq/current/developing/client_context_detail.html

If you feel there is missing information to do your job with AEM- - please log a bug here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html

View solution in original post

smacdonald2008 · 10/15/15

Here is the AEM Client Context documentation:

http://dev.day.com/docs/en/cq/current/developing/client_context_detail.html

If you feel there is missing information to do your job with AEM- - please log a bug here:

http://helpx.adobe.com/marketing-cloud/experience-manager.html

lisalin · 10/15/15

CQ 5.6 has a hot fix for it. - NPR-3930

https://helpx.adobe.com/experience-manager/kb/cq561-available-hotfixes.html

Adobe Experience Manager Sites & More

Stop TwitterProfileData, FbProfileData calls

Learn

Documentation

Events

Community

Support

Resources

Adobe account

Adobe