How does the Tracker Module work? I want to make pages not get picked up (ver 4.4.2)

By TheoGB on 25 May 2005 at 07:51 UTC

Hi,

This seemed the best forum to ask this. Basically I want to add content to our site but I don't want the tracker to pick up the pages as new/changed. We use the tracker to provide a way for users to quickly see what's received comments and been posted that isn't obvious on the front page.

However, this means that whenever I adjust any content, that page appears in the list. Really I want the facility to bring some pages out of the tracker's clutches, or 'spoof' them with incredibly ancient edit times so they go to the bottom of the list.

Can anyone help me understand how the tracker works? If it's a simple database adjust after the fact then I'll settle for that, rather than an actual mod. In fact, that's what I assume it will be.

Cheers
Theo

Comments

been asked a number of times on here...

Dublin Drupaller commented 25 May 2005 at 11:23

Hi Theo,

that has been asked on numerous occasions..i.e. how to "hide" or specify which node types the tracker.module lists...and it has been reported "fixed" on some of the threads listed below, but, I was never able to get it working.

Threads dicussing how to to "hide" certain node types / content from the tracker module. (here's just a few...there maybe some tips on how to actually do what you want in the threads below)

http://drupal.org/node/22881

http://drupal.org/node/5909

http://drupal.org/node/13462

http://drupal.org/node/22988

http://drupal.org/node/3532

Probably best to post a feature request here:
http://drupal.org/node/17119

Not sure if this is of any use, but, I was trying to get the RECENT FORUM TOPICS link just displaying RECENT FORUM TOPICS and came up with a php snippet workaround/hack. i.e. instead of just linking back to the tracker.module that displays everything, the php snippet just displays a list of RECENT FORUM TOPICS. You could probably hack that snippet to just display recent node types by changing it to display recent "forum" nodes, to "unhidden" nodes.

http://drupal.org/node/23234

If you come up with a solution...there are a lot of users out there who are lookig for one..so please post back up on the forum. or specifically in this link http://drupal.org/node/17119 which seems the most current.

Dub

DUBLIN DRUPALLER
___________________________________________________
A drupal user by chance and a dubliner by sheer luck.
Using Drupal to help build Artist & Band web communities.

Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate

Cheers.I did try a search

TheoGB commented 25 May 2005 at 15:11

Cheers.

I did try a search but I found it very hard to work out what to search for. Clearly I was being a muppet.

I'll check these out. Much obliged. :-)

no worries....

Dublin Drupaller commented 25 May 2005 at 15:24

No worries Theo...FWIW I spent a lot of time trying to work out how to limit the tracker to specific node types but didn't get anywhere...I'm note very experienced in sql/php

would be great if you could chip in any ideas you might have...I'm still looking for a solution.

Dub

DUBLIN DRUPALLER
___________________________________________________
A drupal user by chance and a dubliner by sheer luck.
Using Drupal to help build Artist & Band web communities.

Currently in Switzerland working as an Application Developer with UBS Investment Bank...using Drupal 7 and lots of swiss chocolate

Well the comment that is

TheoGB commented 25 May 2005 at 15:56

Well the comment that is 5909 in your list above (the second of the first block) actually gave me a partial answer.
http://drupal.org/node/5909

The code the Shane proposes almost works in that it can block based on both title and author, but for some reason the 'type' doesn't work. I used Flexinode to create a new type (Band Page) and when I put that in it was the ONLY type that showed up. All attempts to use other types just refused to limit it at all.

I have no idea why this fails. It's annoying because type would be useful but in the event I have created a new user called 'I Shot the Deputy' (the site is http://www.ishotthedeputy.com you see) and I have assigned that to the pages I would rather the Tracker did not pull up and this works.

Hmm. Actually it hasn't

TheoGB commented 26 May 2005 at 07:40

Hmm. Actually it hasn't worked entirely: The entries are still getting counted even if they're being ignored which means that I am getting less entries on the page that would contain them, quite noticable when you've just made a bunch of them.

I'll have to look harder.

Presumably you could alter these initial selects:

  if ($id) {
    $sql = "SELECT n.nid, n.title, n.type, n.changed, n.uid, u.name, MAX(GREATEST(n.changed, c.timestamp)) AS last_activity FROM {node} n LEFT JOIN {comments} c ON n.nid = c.nid INNER JOIN {users} u ON n.uid = u.uid WHERE n.uid = '". check_query($id) ."' AND n.status = 1 GROUP BY n.nid, n.title, n.type, n.changed, n.uid, u.name";
    $sql .= tablesort_sql($header);
    $sresult = pager_query($sql, 10, 0, "SELECT COUNT(nid) FROM {node} WHERE status = 1 AND uid = '". check_query($id) ."'");

  }
  else {
    $sql = "SELECT n.nid, n.title, n.type, n.changed, n.uid, u.name, MAX(GREATEST(n.changed, c.timestamp)) AS last_activity FROM {node} n LEFT JOIN {comments} c ON n.nid = c.nid INNER JOIN {users} u ON n.uid = u.uid WHERE n.status = 1 GROUP BY n.nid, n.title, n.type, n.changed, n.uid, u.name";
    $sql .= tablesort_sql($header);
    $sresult = pager_query($sql, 10, 0, "SELECT COUNT(nid) FROM {node} WHERE status = 1");
  }

So that a given n.type was excluded, but also change the non-user-specific version to exclude a certain user as I am doing now?