Support » Plugin: Slimstat Analytics » Flaws in latest slimstat

  • Resolved t-ryder


    I am managing some websites for my customers and lately I switched to slimstats for all of them. I had to change the cookie hint banner a bit because the out of the box CSS code gave me no good results.

    <p style=" -webkit-box-sizing: border-box; -moz-box-sizing: border-box; box-sizing: border-box; z-index: 99999; width: 100%; position: fixed; bottom: 0; margin: auto; padding: 1em; border: 0 solid; border-top: 1px solid #000; text-align: center; -o-text-overflow: ellipsis; text-overflow: ellipsis;background: #fff;">This website uses cookie monsters and seduces aliens to dance mambo.<br><br><a href="{{accept_url}}"><strong>OK dude</strong></a> or <a href="{{deny_url}}"><strong>Nopes</strong></a> - Read my privacy yadda yadda <a href=""><strong>linky</strong></a></p>

    Works better, with the out of the box code my text was cut off.

    But that is not the main reason why I write this feedback.
    Slimstat generates a URL when opting-in. It is if chosen so. So if a user now shares this URL via shariff wrapper social sharing icons/buttons and the other user opens that link the other guy opted-in wihtout maybe even knowing that he/she opted-in being maybe noobish. That is not good imo and maybe would offense against law unintentional by leading the other user into an unwilling opt-in. This may sound crazy, but think about it.
    I am no privacy law expert or lawyer… the scenario is unclear to me regarding the new laws.

    • This topic was modified 1 year, 7 months ago by t-ryder.
    • This topic was modified 1 year, 7 months ago by t-ryder.
Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Flaws in latest slimstat’ is closed to new replies.