Closed (fixed)
Project:
Node expire
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
1 Jul 2011 at 11:43 UTC
Updated:
11 Jan 2014 at 02:20 UTC
Jump to comment: Most recent
Is it really necessary to load each nodes on every cron job. Because query selects All expired nodes, and it`s may be a big amount of nodes.
May be we can use just 'nid' for Rules, and than each function can load node if necessary ?
Or add some hook to check if we really want to load or skip this node ?
Comments
Comment #1
magpie5212 commentedNot sure of the solution, but I think I am suffering this. When I have the 'content expired' rule enabled in the Triggered Rules the cron fails the first time with a '500' type server error - effectively too much being run.
Comment #2
Nafes commentedThe solution is going to be released soon. See here at #1774402: Allow cron to trigger "Content Expired" rule only once.
Comment #3
Nafes commentedComment #4
Nafes commentedFixed in 7.x-1.0-alpha3.
Comment #5
Nafes commented