Timeline for Delete 13000 nodes
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2013 at 10:30 | comment | added | Clive♦ | @develkar For a few hundred nodes that might be fine, but the drush extension uses exactly the same functions as the on-site version so it's still just as susceptible to timeouts unfortunately | |
| Jun 14, 2013 at 10:24 | comment | added | AjitS |
@Clive With drush support if I get to do drush delete-all article to delete articles I'd go for this solution.
|
|
| Jun 14, 2013 at 9:53 | comment | added | Clive♦ | @Letharion No pain, no gain ;) You're right of course, I though I'd just better slap a disclaimer on this as this module could make things messy if in the wrong hands! | |
| Jun 14, 2013 at 9:51 | comment | added | Letharion | Could still be useful if you know what you're doing, and take backups. Deleting thousands of nodes while invoking all hooks and apis can be painfully slow. :( | |
| Jun 14, 2013 at 9:45 | comment | added | Clive♦ |
I'd strongly recommend not using this module - it sets a time limit of 30 seconds on the script, and runs through each and every node individually, calling node_delete() (it doesn't even bother to use node_delete_multiple()). Even more worryingly, it has an option that deletes data directly from the database tables without using the field API, and without using hooks. No batch jobs at all, it just runs until the script dies. Very dangerous module IMHO.
|
|
| Jun 14, 2013 at 9:42 | history | answered | AjitS | CC BY-SA 3.0 |