Module should use the core Batch API to avoid timing out

This is now an old issue, but in case anyone is asking the same question I have successfully used this module (in normal mode) to delete 70,000 CCK nodes, each containing over 50 fields, plus related taxonomy terms, url aliases etc.

I found that the module deleted about 1000 nodes at a time before crashing. So effectively this meant going back and pressing the delete button many times. This was tedious but easier than doing this with views bulk operations, or deleting the content type and recreating each field, or trying to delete the records directly through the database.

Ideally this module would incorporate a batch delete function so it could cope better with very large numbers of nodes- which is where it is most useful/ essential.

I agree that this as a crucial module and should ultimately be in core. Thanks for maintaining it

Altering the title slightly to what I think the issue is. Correct me if I'm wrong. Will try it out this afternoon.

I found that the module deleted about 1000 nodes at a time before crashing. So effectively this meant going back and pressing the delete button many times. This was tedious...

Please see this comment, if you would like to delete more than 1000 nodes at a time: http://drupal.org/node/466942#comment-2675220

Changing this to a feature request.

Patches welcome.

Yes, Batch API could be a solution, as the title says.

However, I would like to mention that using Batch API and still calling the original node_delete() will result in a lot of watchdog and drupal_set_message calls, which you might want to avoid.

You're much better off using Views Bulk Operations instead. It uses batch API for deletion.

I just needed to use this module hoping it will help me to delete all the contents in a node type (~7000 nodes) but this module didn't hand up. But it took a very long time so my guessing is that it will run as long as memory limit or max_execution_time hits.

I'm working on a batch api project so I managed to use batch API so I could use batch api for this.
I will post a patch with modifications soon.
(Drupal 7).

Please let me know if you guys are need to go with VBO. I'll happily stop it :)

Please review the patch.
I have added a new option "Batch API" to methods, and in the submit function, if the batch_api option is selected, it will run a batch_set() to perform the action on chosen nodes.
It can count processed rows and dsm() after finishing.

I have applied the patch provided in #9 and it works well!

Coding standards need work: http://drupal.org/coding-standards/

If someone wants to give this patch another try, and clean it up for coding standards, then I will commit it.

Sorry for taking much time for a clean up. To be honest, I'm not an expert in code standards subject so please be bear with me in this. I will post a new patch soon with clean ups I can find.
Thanks.

Sure thing, take your time.

Duplicate of #2116349: Implement Batch API