LoudVoice's Cookie - 3rd Party Cookies Off

I thought my implementation of LoudVoice was incorrect until I realized that having 3rd party cookies turned off in a browser breaks LoudVoice. I understand the need for the cookie, but the overwhelming number of safari users is still there according to these stats.

In my implementation of LoudVoice, I merged the Social Login + LoudVoice, (as seen here), so that people don't have to log in again to comment.

Now, if someone were to have 3rd party cookies turned off, then on every new page load they must login manually with their social login. It also breaks the "log out" link. When no 3rd party cookie is present the oneall server resets the "author_session_token". Resetting that token is the only thing I'd like to prevent, if possible. Otherwise I'd have to check for the author session via API on every page load that contains LoudVoice comments which seems a bit excessive. Is there any other workaround that can be done to avoid this issue?

Best Answer

  • Claude_SchlesserClaude_SchlesserAdministratorOneAll Team
    Answer ✓

    Hi Ryan,

    I'm sorry that it took so long, but the bugfix was part of a bigger improvement package for LoudVoice and it unfortunately took longer as expected.

    LoudVoice will now set the cookie on the domain which should solve the issue!

    Best Regards,

Answers

  • Claude_SchlesserClaude_SchlesserAdministratorOneAll Team
    Hi Ryan,

    thank you very much for the error report. I think that technically speaking it should be possible to save the cookie on behalf of the domain that includes LoudVoice and not on the domain where LoudVoice is hosted. We will have a closer look at this!

    Your implementation sounds great by the way ;)

    Best Regards,
  • Thanks Claude. Setting a cookie or session variable on the domain and sending it back through the API would be great.

    Any update on whether or not this will be made possible?
  • Claude_SchlesserClaude_SchlesserAdministratorOneAll Team
    Hi Ryan,

    we have been able to reproduce the issue, but we unfortunately haven't released a bugfix yet.
    One of our developers is however already working on it!

    Best Regards,

Welcome!

Please sign in to your OneAll account to ask a new question or to contribute to the discussions.

Please click on the link below to connect to the forum with your OneAll account.