How to turn on/off Hotjar dynamically without page reloading - cookies

I have a web application using Hotjar to track user's information and behavior while they navigate through it, but I would like to give the user the possibility to turn on/off Hotjar tracking.
The idea is to have a check button that would turn on when selected and off when deselected. I was thinking also that this action could use some specific cookies, that would tell Hotjar the tracking is on or off dynamically.
Is it possible? If so, is it possible without page reloading?

According to this position from HotJar support, it is not yet possible to turn off using events.

Related

Clicking a node in the Sitecore tree makes all other nodes disappear

I'm encountered a weird issue with new Sitecore user accounts. I set their permissions correctly, giving them access to read, write, create, etc the content items/folders they need and the Media Library. When they user logs in and clicks any of the 5 nodes in the tree (or their children) the Sitecore tree/navigation will hide all other nodes.
So if they click an image in the Media Library, the Sitecore tree will focus on the Media Library and not show the Content, System, Templates, etc nodes.
I've tried adding every single role in my company's Sitecore system to a test user and that didn't change a thing, it still happens. Any thoughts on this would be greatly appreciated.
In the Content Editor, click the Content Editor menu, and then click Application Options. Click View tab and check "Show Entire Content Tree"
https://doc.sitecore.net/sitecore_experience_platform/content_authoring/the_editing_tools/the_content_editor/customize_the_content_editor
Can you please check your URL if it contains ro=/sitecore/media when you click an image media item? Also let please let us know which version you using of Sitecore? Have you made any changes to link manager ?
This sounds to me like a session issue. The Sitecore shell does not like running in a stateless load balanced environment, and the tree in particular manages it's context in session state. If you have more than one server for authoring behind an NLB make sure you have sticky sessions enabled. Otherwise check to make sure your session state setup is properly configured.

How to customize mobile device detector?

I have a customize request from my client in sitecore mobile module.
I want to be on full view site from my mobile on Career page, i am able to do it but any of the link inside career page with having mobile layout in presentation detail is taking that page again to mobile device.
Can we make any customization that maintain the device in cookies so that it keep user on full view site after coming to career page.
Is there any setting we can do in pipeline or session. I just want to be throughout in full view site after coming on career page and no going back to mobile layout. Kindly suggest.
Yes, you can do exactly that. You'd need to update the rule to detect the various devices (which I'm guessing you already have). You can then create a custom condition to check if cookies have been set for the full site(does not need to be a cookie of course, but that'd be the easiest way).
You can find the existing Conditions and Actions here in the path /sitecore/system/Settings/Rules.
To create custom conditions and actions, please read the following article on SitecoreInsight.com
After creating your custom condition, go into your device item again and update the Rule there to only switch to that device when that cookie has not been set.
[edit]
Come to think about it, it might be possible to have your 'go to full site' link appended with a querystring sc_device={GUID of device}. I'm not sure what would take precedence here, the 51degrees rules or Sitecore's cookies... Worth a try though :-)

Is it possible to enable iCloud without user intervention (ie programmatically)?

I'm getting ready to add Ensenbles to my iPad app, and trying to figure out how much of a problem it's going to be if the device is not iCloud enabled, and then figure out how to get the device enabled, without user intervention (if that's at all possible).
Is this possible? (to enable iCloud without user intervention)
No, not at all. If the user doesn't enable iCloud, you don't get to override their decision. You can ask them to enable iCloud, but you can't do anything about it in your app.

Sitecore user cannot load items in editor

I have a content editor that, when she logs into the Sitecore content editor and clicks an item, nothing happens. The item doesn't load for editing. If she clicks off of the item to another item she's prompted "do you want to save the changes to the item"?
Logging in with another account resolves the issue. Logging in with her account on another PC resolves the issue.
Has anyone ever seen this before? Sitecore is non-functional on this user's PC.
When you say that the item doesn't load for editing, you need to be more specific? Obviously, if she's clicking off the item and getting prompted to save, then the user is able to edit the item. What is it that she can't do?
Also, it depends on what role you have the user set to use, but depending on how you have your site configured, a user can simply click the item, see the fields and enter content in them. There may not be any "edit" queue. Is this not the case? If not, then there's more details that are needed to properly answer your question.
It sounds like a browser / caching issue. I usually try the following.
1. If IE 9 the I try and open a session in private and try again
2. Clear all browser history
3. If that doesn't work try with another browser.
4. If other browser fixes the issue then try to reset the original browser's settings to the defaults.
Last check if you are using a proxy server and try without. This is a long shot.
What version of Sitecore is being used? Older versions using IE9 require compatibility mode to be enabled (this was resolved in later updates of 6.5)
I find the Content Editor most stable in Firefox and IE9 compatibility mode. Chrome has a few finicky issues but generally works.

Sitecore: tracking of the last visited page

On the site that I'm developing we need to track the last visited page for each user (users login to the site). What's the best way to do this? We are already using a custom profile so adding a new field is easy. The site will not have a lot of traffic so updating this field wont be an issue, i think. Are there better ideas? Does sitecore already offers something that we can possible use?
OMS has a "Top Exit Pages" report by default... but that is tracked across sessions, not users.
A good IIS log parser should also be able to give you this information... again, that would be by session (or IP) and not logged in user.
If you really want to get every exit page AND filter by logged in user... what I would do is add a new pipeline processor to httpRequestBegin, and place it after the ItemResolver. Then save the Item.Paths.Path. I would advise against writing this data to the user Profile if you are using the default ASP.NET Profile handler and you have a decent amount of traffic, because it is highly inefficient. Roll your own simple storage solution here, or just dump the data to a log.
My first question would be: Why do you need only the last visited page of the user? What are you trying to determine?
In a lot of cases, you are probably starting down an analytics route, or perhaps even trying to drive some marketing.
If the analytics is what you are going for, you can probably just pop an event out to your google analytics account with the current username as an event variable to allow you to look at analytics by user and by page. Alternatively, you could use the Sitecore OMS/DMS features for tracking all that data and looking at the analytics there.
If you are looking at driving marketing, you probably want to use OMS/DMS, especially if you want to start getting into personalization or engagement plans. OMS/DMS will track user activity, and all the pages they visit, though not by user account. With some customizations, you can probably add that data in, but it will depend on what you are trying to use the information for. The username may not be what is important to you.
If, however, you just want to know what page to send the user back to after logging them in, it would be better to just store that in session or pass as a post parameter if session is not a viable option for you.