Hello,

The issue is really with Aggregation module: #411274 at March 23, 2009 & #834322 of June 22, 2010.

In summary: in order to purge feed items older than a specific no, of days, Aggregation would handle that thru cron but it seems anonymous cron runs we not purge old feed items. If cron (or supercron) is invoked manually, old feed items will be purged.

However, as there were no response, and we are using Supercron, we are approaching you for suggestions.

Regards.

Comments

liren.zhu’s picture

liren.zhu commented

Take a look at this article: http://drupal.org/node/218104

I applied it to supercron.php copy in the drupal root folder. Worked out well for me.

tcibah’s picture

tcibah commented

Many thanks liren.zhu.

It worked...

For other users, use the safe way described there. The code should be applied within the supercron.php file.

While logged in as user 1 , running the modified supercron.php manually will log off user 1.

hefox’s picture

hefox commented

http://drupal.org/project/tokenauth may also work.

ernest.park’s picture

ernest.park commented
Version: 6.x-1.3 » 6.x-2.x-dev

http://drupal.org/node/482960

File not found error. I noticed on install that Supercron had the incorrect base path . . .

When defining the location of the Supercron.php file . . .

should be . . .

drive:\apache directory\drupal_root

Instead, it came up as . . .

drive:\apache directory\drupal_root\drupal_root

where the drupal root was repeated twice. I corrected it as "other", and put the correct path.

When Supercron started, it kept looping until I killed the HTTPD on the server.

MisterSpeed’s picture

MisterSpeed commented

I love this; we'll carefully look into it. Thanks for the research.

cor3huis’s picture

cor3huis commented
Component: Miscellaneous » Code
Category: support » task
Status: Active » Needs work

Bump, helpful info in http://drupal.org/node/218104

And for the path there is another issue #1025474: Crontab configuration tab gives whitescreen and more all related to wrong paths...

BTW I would not mind if you look into it Ferociously instead of

; we'll carefully look into it

;)

rukaya’s picture

rukaya commented

In case anybody else is considering this, I have implemented the solution described in #1 for my Drupal 6 build and it seems to be working fine