Posted by sprite on February 14, 2006 at 12:02am
Jump to:
| Project: | Checkout (Content locking) |
| Version: | 4.6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | joel_guesclin |
| Status: | closed (fixed) |
Issue Summary
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
#1
I'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?
#2
Clearing out the issue queue. Feel free to open a new issue if the problem persists.