I just tried to set my nodes to expire after 1 hour. I have published date mapped to published date. Though, published date is always the time of import or update. So I have a node item that does not update because it has been removed from the external source. So an hour after the published date of said node, node still there.

So nothing ever expires, that feature does not work.

Or does it work in some other situations?

Comments

info@cgfix.com’s picture

info@cgfix.com commented

Seriously, they don't expire.

alex_b’s picture

alex_b commented
Priority: Critical » Normal
Status: Active » Closed (works as designed)

Is your importer configured to 'update existing' or 'replace existing' ?

alex_b’s picture

alex_b commented
Status: Closed (works as designed) » Postponed (maintainer needs more info)

Sry, didn't mean to close.

info@cgfix.com’s picture

info@cgfix.com commented

tried both update and replace. I tested by waiting for node to expire. Then tried by changing the authored on date back later then the expiration time.

What triggers the expiration any way? I noticed that Ical feeds don't carry in a published date, so the published date is always set to the current date when the feed updates.

I have the Ical published date mapped to the node published date but it doesn't seem to do anything.

bignall’s picture

bignall commented

I am also seeing this behavior. It was originally set to not expire but changed to expire after 1 day. However the nodes are not expiring. It is set to Replace existing nodes.

Thanks for the help!

Edit: oh btw, I am using the most recent 6.x-1.x dev version.

bignall’s picture

bignall commented

What additional information is needed on this one? I'll try to help. I need it to work properly ;)

hwasem’s picture

hwasem commented

I'm using the 7.x alpha 4 version, and I'm also having problems with my nodes not expiring. My importer is set to expire after one hour.

I don't have a publish date mapped in the Node Processor Mapping, but the Nodes do have a publish date of the time the nodes were imported. Happy to try anything or provide more info.

pauln600’s picture

pauln600 commented
Priority: Normal » Major
Status: Postponed (maintainer needs more info) » Active

I have the same problem - the node importer is set to expire nodes after one hour, but they never expire... in fact, I don't seem to be able to get rid of them by any automatic method. Running cron adds new items, but doesn't clear the expired items.

This is a show-stopper issue for my use of this module...

Thanks,
Paul N.

jgoodwill01’s picture

jgoodwill01 commented

I'm experiencing the same Issue. I can't seem to get the nodes to expire. Has anyone resolved this? Any suggestions to get it working?

sydneyshan’s picture

sydneyshan commented
Version: 6.x-1.0-beta9 » 6.x-1.0-beta12

Same issue here. 'Expire nodes' is set to 'after 1 hour' and 'Update existing nodes' is set to 'Replace existing nodes'. The nodes are not getting deleted after 1 hour despite cron running every 2 minutes over the last 6 hours... No publish dates are being mapped.

hwasem’s picture

hwasem commented

I was finally able to get the nodes to expire with the Update existing Nodes set to 'replace existing nodes' option. My expire is set to one week. I can't remember if there was another patch or something I used (9 months ago), but I did finally get it to work after literally a week of plugging away at different options. Sorry, I'm sure that is not much help. Again, I am using version 7.x-2.0-alpha4.

ajayg’s picture

ajayg commented

I am still seeing this in latest 6.x beta. Anyone has figured this out. This is open for quite a while.

damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Marked #1161820: Expired nodes - they dont expire as a duplicate.

twistor’s picture

twistor commented
Issue summary: View changes
Status: Active » Closed (outdated)