Curious behavior

  • Resolved iltrev

    (@iltrev)


    12 years, 1 month ago

    I just installed WP DoNotTrack on a couple sites, and it seems to be working. Well, almost.

    What it appears to be doing is that it works just fine for visitors, but not at all with my own visitst (I mean, when I am logged in as admin).
    Just to be more clear: I am using Ghostify on Safari, and what I see is that WP DoNotTrack works perfectly when I visit my sites as a non-logged-in user, disabling the generation of the code contacting secure.quantserve.com, but it doesn’t work at all in sessions where I am logged in as an admin.

    I tried both black- and whitelist mode, and none of them seems to be helping.
    Well, ok, I am perfectly happy with it as it is, but… Is there anything I can do to *completely* stop Jetpack from doing that?

    Thanks in advance

    https://www.ads-software.com/extend/plugins/wp-donottrack/

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Frank Goossens

    (@futtta)

    Morning Iltrev;
    Are you using normal, forced or superclean mode?

    frank

    Thread Starter iltrev

    (@iltrev)

    Tried both, no change.

    Thread Starter iltrev

    (@iltrev)

    As a side note: I also just installed Jetpack 1.9.1 – is there any way it could be due to that?

    Another thing: the url it contacts when I am logged in is https://secure.quantserve.com/query.js , as opposed to https://edge.quantserve.com/query.js. Any chance it is related to that?

    Plugin Author Frank Goossens

    (@futtta)

    Can you set wp donottrack to “whitelist” and “superclean” and try again?

    Thread Starter iltrev

    (@iltrev)

    Nothing changes (see this screenshot)

    Plugin Author Frank Goossens

    (@futtta)

    Very weird. I’ll investigate and get back to you on this.

    Thread Starter iltrev

    (@iltrev)

    Well thanks for now

    Have a nice day ??

    Plugin Author Frank Goossens

    (@futtta)

    remains weird; tested on my development instance and can’t reproduce (i.e. no calls to quantcast to be seen in firebug). what Jetpack features are you using?

    Thread Starter iltrev

    (@iltrev)

    Sorry for the delay…
    I am using just stats and subscriptions.

    Plugin Author Frank Goossens

    (@futtta)

    could you create a user with limited rights (contributor, author or editor) on your blog, so I can log in and see what is going on? you can mail details to futtta at gmail dot com.

    Plugin Author Frank Goossens

    (@futtta)

    OK, quick recap of what we discovered for anyone who would stumble on this post;

    • wp donottrack was not active in the admin-pages (for the tech-heads; no output buffering in wp-admin). i’ll fix this with a release today/ tomorrow
    • the quantcast tracking was triggered by jetpack notifications, which loads an iframe from jetpack.wordpress.com, which in turn contains the quantcast tracking code. you’ll have to manually disable jetpack notifications to stop this, as wp donottrack cannot act on the content of iframes.

    a general remark about jetpack; i’m glad i don’t use it myself, it’s pretty invasive.

    thanks iltrev for posting & helping out!

    frank

    Thread Starter iltrev

    (@iltrev)

    Thank you, it’s been a pleasure helping out (and being helped)

    Plugin Author Frank Goossens

    (@futtta)

    more info on this subject in this blogpost I just wrote.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Curious behavior’ is closed to new replies.