When content is viewed by a user. Add a delay between tracks of a user.

Hello Jerad Bitner,

Thank you for suggetion! I will try to use these hooks. Could we leave this post, so I will be able to add an example of code here?

--
Best regards,
Sergei

There is a mistake in DEVELOPER.txt, as well as on http://drupal.org/node/626914:

Example:
/**
* Implementation of hook_activity_records_alter().
*/
function example_activity_records_alter(&$record, $context) {
// If we have a story node rather than another type, we can change the
// token pattern.
if ($object->type == 'story') {
$author_pattern = $context['author-pattern'] .' - [node-type]';
$record->author_message = token_replace($author_pattern, $record->type, $context[$record->type]);
}
}

The name of function should be example_activity_record_alter() instead of example_activity_recordS_alter()

Unfortunately, record is always recorded to DB. There is the code:

  // allow other modules to manipulate the record before insertion
  drupal_alter('activity_record', $record, $context);
  drupal_write_record('activity', $record);

Even if I unset the $record in my hook, the empty record would be recorded by drupal_write_record().

It could be great to add a condition and verify the $record after the call of drupal_alter():

  // allow other modules to manipulate the record before insertion
  drupal_alter('activity_record', $record, $context);

  // record could be cleared by other modules to avoid tracking.
  if (!isset($record)) {
    return;
  }

  drupal_write_record('activity', $record);

I've tried to use the hook_activity_message_recorded(). Unfortunately I can't avoid tracking from this hook because the table {activity_access} is filled after it:

  // after this is recorded, another module might want the aid
  module_invoke_all('activity_message_recorded', $record, $context);

  $grants = activity_get_grants($record);

  foreach ($grants as $realm => $values) {
    foreach ($values as $value) {
      // insert one by one. In D7 we can use the DBTNG to insert multiple
      $perm = new stdClass();
      $perm->aid = $record->aid;
      $perm->realm = $realm;
      $perm->value = $value;
      drupal_write_record('activity_access', $perm);
    }
  }

So, in hook_activity_message_recorded() I can verify a tracked activity (by $record->aid) and remove it, but I can't remove records from {activity_access}.

I added the condition which checks if $record is empty after the call of hook_activity_record_alter(). Now it works well.

The patch is attached. It could be great if you can check and test it.

PS: Eclipse cleared whitespaces, so patch is a bit long :( The changes, which I made, are located in lines 78-81.