Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have read the discussion here: http://drupal.org/node/477380. I don't have any access denied errors along w/ the messages/pmgrowl_json messages that appear in watchdog. However, it looks like these are counted as page hits, which is kind of skewing my reports by thousands of hits. I really do like this module. Is there any way for these not to show as page hits? Thanks.
Comments
Comment #1
glarsch CreditAttribution: glarsch commentedWow, my browser tweaked on me. Sorry for the duplicates.
Comment #2
janis_lv CreditAttribution: janis_lv commentedis this the right behavior?
under admin/reports/hits,
almost for every "node" visit there is a "/messages/pmgrowl_json".
is there a way to filter this out or correct it so that it won't show up in reports?
Comment #3
Ingumsky CreditAttribution: Ingumsky commentedSubscribe. There're lots of useless messages 'messages/pmgrowl_json' in users' trackers (navigation tab).
Comment #4
svenrissmann CreditAttribution: svenrissmann commentedHi,
I´ve had the same experience on my Sites.
You can kill this issue by simply putting exit(); after: drupal_json($data); in pmgrowl_json().
Doing so will prevent Drupal from counting this as a full PI.
What I noticed too, is that the polling of the jQuery Script for new Messages is acting like a PI and so the user is always Online if a Browser window is still open! You can reconstruct this easily using Author Pane and PM Growl on the same site. I´ve tried to kill this issue by faking something in _boot or _init but that doesn´t work and for sure isn´t realy good in performance. So what´s about looking for new messages via XML-RPC ??
Comment #5
elianmI'm getting this in version 7.x too. putting
exit(); after drupal_json($data);
didn't kill this issue.Do I have to open a new issue for version 7.x?
edit #1
I get a:
as well.
As far as I can see, I can't reproduce this locally, only in a live site.
How can I solve this?
edit #2:
This is another message I got in my live site:
Comment #6
soulfroysPutting exit(); after drupal_json($data); (suggested in #4) didn't work for me too...
Comment #7
Anonymous (not verified) CreditAttribution: Anonymous commentedsame here for drupal 7...
i get this notice only if there are no new messages for the user and it has nothing to do with authorpane.
i think on any pageload some code looks for output until he found some.
Comment #8
DevJoshLopez CreditAttribution: DevJoshLopez commentedim still getting this for the drupal 7 version. has anyone fixed this?
Comment #9
vidichannel CreditAttribution: vidichannel commentedHaving same problem here with watchdog messages showing up in the user's tracker for Drupal 7.
Comment #10
Anonymous (not verified) CreditAttribution: Anonymous commentedYep getting millions of messages here for anonymous on Drupal 7.
Comment #11
godzz CreditAttribution: godzz commentedI had a lot of message 403 "messages/pmgrowl_json" (users who lost cookies, unauthorized or etc, but still open browser)
helped add to pmgrowl.js:
if (!jQuery.cookie("DRUPAL_UID")) { return; }
after line "var pmGrowlCheckNew = function() {".
this for Drupal 7, when user unauthorized, script not send any request.
Comment #12
AndrewLeon CreditAttribution: AndrewLeon commentedThis issue appears on the d7 branch as well.
Comment #13
janis_lv CreditAttribution: janis_lv commented3 years and no fix :[
Comment #14
drusite CreditAttribution: drusite commentedIs there a fix for this?