Does anyone use the Tools page (delete all nodes of a given content type)? It seems to me that the sorts of developers likely to use this probably would have Views Bulk Operations, which is more useful. My inclination is to drop it - if it is to be retained, it needs to implement the batch API for large operations.

Add a +1 if use it and would like it retained in the Migrate module.

Thanks.

Comments

vrteach’s picture

I have used the tools page to clean out stuff that I had migrated before the naming change of the map tables. If there is something else available (I have heard of but never used the views bulk operations) then I'm OK with dropping it. It is fine with me if Migrate narrows the focus to migration.

csc4’s picture

+1

I've used it - and think it's useful , made prototyping really easy.

VBO may be more useful but it's also quite obscure for non developers, if tools was removed detailed documentation on how to do the same thing would be needed otherwise the support tickets would be bound to rise!

Couldn't it use the same Cron batching rules as the import if performance is a concern?

moshe weitzman’s picture

I actually think it is useful.

mikeryan’s picture

Title: Remove Tools page? » Use Batch API for bulk node deletion
Category: task » feature

OK, transmogrifying - if we're to keep it, we need to support the batch API for deleting large numbers of nodes.

mikeryan’s picture

Priority: Normal » Minor
mikeryan’s picture

Title: Use Batch API for bulk node deletion » Remove tools page
Assigned: Unassigned » mikeryan
Category: feature » task

Going back to the original plan - bulk deletion is now supported via drush, which is a better place for it anyway (not subject to timeouts). Those who really want to be able to do this via the browser can use VBO. So, I will be removing the Tools page.

mikeryan’s picture

Status: Active » Fixed

Committed as part of #650472: Workflow refactoring.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.