I currently have a website that has 1403 feeds brought in via the FeedAPI module. The newly created nodes are associated with over 800 Taxonomy terms.

The website is called "Non Stop Events" at http://nonstopevents.com

I had problems with the FeedAPI saving nodes using version 6.x-1.3, so I had to revert back to version 6.x-1.2 and everything seemed to be working fine.

A month later I noticed the following problem:

In the beginning, during the initial Feed setup, I set all the feed settings to "Delete news items older than" to 2 weeks.

Its been about a month and none of the nodes created with the FeedAPI module have been deleted after 2 weeks.

The first node created by FeedAPI was http://nonstopevents.com/?q=node/1405 created back in mid September.

As of this posting today, October 14, 2008, the last node created is http://nonstopevents.com/?q=node/67278

All the mid September nodes created, i.e. 1405, 1406, 1407, etc.. are still present and have not been deleted.

By the way, I have set my web server set to cron every 20 minutes, the FeedAPI setting "Cron time for FeedAPI [%]:" is set to 75% and to "Allow all HTML tags".

Is this a bug?

If I upgrade to the newly released 6.x-1.4 version, with this problem be taken care of?

Thanks for your time and a great module,

Sam

Comments

Sam308’s picture

Does anybody have an answer?

How does the "Delete news items older than" feature actually work?

If the "Delete news items older than" feature does not work, is there another way to automatically delete the nodes created by FeedAPI that are older than 2 weeks for drupal 6.x?

I need an answer, otherwise I will have to permanently take down the website because it will be filled too much out dated content and the database will grow into gigabyte proportions.

Sam308’s picture

Any Answer?

aron novak’s picture

Status: Active » Postponed (maintainer needs more info)

See the SQL query at feedapi_node.module _feedapi_node_expire(). Execute it manually with proper values and see if there are the outdated items or not.
Make sure you have the proper setting at the feed. Go to the feed node, edit it and then see processor settings.
I just tested it at FeedAPI 1.4 and i could not reproduce the problem.

aron novak’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)

I'm sure that it's the same ticket as this: http://drupal.org/node/329752
Expect a fix soon for the problem.