Closed (fixed)
Project:
Checkout (Content locking)
Version:
4.6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
14 Feb 2006 at 00:02 UTC
Updated:
2 Dec 2007 at 06:45 UTC
checkout.module and Aggregator2.module do not play well together.
When Aggregator2 performs its cronjob driven feed updates, if checkout is active, all the feed items accessed during the feed update are left checked out. After a large aggregator2 feed run hundreds of nodes are left checked out!
Obviously I have disabled checkout for now ....
I noticed that people working on a re-write of this module are already generally aware of the problems created by the various alternate code paths that cause node modifications other than user-interactive changes.
Comments
Comment #1
joel_guesclin commentedI'll be happy to work on this when I get the time - do you know any simple way of telling whether the nodeapi hook is being called online or from a cron job?
Comment #2
smk-ka commentedClearing out the issue queue. Feel free to open a new issue if the problem persists.