Shoutbox refresh keeping users logged in, filling tracker log

http://drupal.org/node/247889 tracks the problem with shoutbox cloggging the tracker because of refreshes.

Not sure about it keeping the user logged in. I can't promise a fix in the next release but I will look around to see if it will be an easy fix.

will this hack work in d6?

+1
what need to modify for cutout that messages from log in D6

That what i understood.
AppleBag, you have changed statistics_user_tracker()

   229  function statistics_user_tracker() {
   230    if ($account = user_load(array('uid' => arg(1)))) {
   231
   232      $header = array(
   233          array('data' => t('Timestamp'), 'field' => 'timestamp', 'sort' => 'desc'),
   234          array('data' => t('Page'), 'field' => 'path'),
   235          array('data' => t('Operations')));
   236
   237      $result = pager_query('SELECT aid, timestamp, path, title FROM {accesslog} WHERE uid = %d' . tablesort_sql($header), 30, 0, NULL, $account->uid);
   238      while ($log = db_fetch_object($result)) {
   239        $rows[] = array(
   240          array('data' => format_date($log->timestamp, 'small'), 'class' => 'nowrap'),
   241          _statistics_format_item($log->title, $log->path),
   242          l(t('details'), "admin/logs/access/$log->aid"));
   243      }
   244
   245      drupal_set_title(check_plain($account->name));
   246      $output = theme('table', $header, $rows);
   247      $output .= theme('pager', NULL, 30, 0);
   248      return $output;
   249    }
   250    else {
   251      drupal_not_found();
   252    }
   253  }

i have found the same code in D6 at file /modules/statistics/statistics.pages.inc

    42  function statistics_user_tracker() {
    43    if ($account = user_load(array('uid' => arg(1)))) {
    44
    45      $header = array(
    46          array('data' => t('Timestamp'), 'field' => 'timestamp', 'sort' => 'desc'),
    47          array('data' => t('Page'), 'field' => 'path'),
    48          array('data' => t('Operations')));
    49
    50      $result = pager_query('SELECT aid, timestamp, path, title FROM {accesslog} WHERE uid = %d'. tablesort_sql($header), 30, 0, NULL, $account->uid);
    51      $rows = array();
    52      while ($log = db_fetch_object($result)) {
    53        $rows[] = array(
    54          array('data' => format_date($log->timestamp, 'small'), 'class' => 'nowrap'),
    55          _statistics_format_item($log->title, $log->path),
    56          l(t('details'), "admin/reports/access/$log->aid"));
    57      }
    58
    59      if (empty($rows)) {
    60        $rows[] = array(array('data' => t('No statistics available.'), 'colspan' => 3));
    61      }
    62
    63      drupal_set_title(check_plain($account->name));
    64      $output = theme('table', $header, $rows);
    65      $output .= theme('pager', NULL, 30, 0);
    66      return $output;
    67    }
    68    else {
    69      drupal_not_found();
    70    }
    71  }

insert hack after line 52
while ($log = db_fetch_object($result)) {
the code

 	if ($log->title != 'View Shouts') {
	l(t('details'), "admin/reports/access/$log->aid"));
	}

anybody say me will that work, i'm newbee in drupal and php.

error too many ")" at the end, erase one of em and leave

if ($log->title != 'View Shouts') {
l(t('details'), "admin/reports/access/$log->aid");
}

But nothimg chage, View Shouts left in reports

subscribe, thx

Is this something we want looked at for the 6.x branch?

definitely for 6.x thx !

If anyone has a solution that doesn't involve hacking core, I'd love to know..

I noticed this annoying issue too..

A solution is not to use Drupal menu system, but use a separate PHP file for the shoutbox update with a minimal db usage (include directly the Drupal settings.php, bypass all bootstrap process).

Another module that does this is Chatroom - there is a custom chatroom.php file that is hit, which allows a bypassing of core statistics/tracker, and for less db overhead when reading from the chat room table.

I would suggest Shoutbox take the same approach, for scalability...

Updating title, marked #247889: View Shouts in log! as a duplicate.

subscribe

I don't think having a separate shout.php would work with how shoutbox is currently set up. Submodules depend on altering the ajax callback path, then using that path to determine group context, user context, etc. That wouldn't be possible with a separate php file.

Any ideas?

With one shoutbox.php you can have multiple paths: shoutbox.php?path=1 or shoutbox.php?path=2...