node_revision_delete 7.x-2.6

Small release discovered after releasing 7.x-2.5 that fixes a non-critical but annoying bug on the report that is generated once Node Revision Delete has finished when using Drush or the Administration Interface to delete old revisions.

Note: the external issue with Field Collection module is still open. Beware. See #2000690: Deleting revisions via node_revision_delete wrongly deletes entire field collection for more details.

What was fixed?

The module was not using the $context['results'] setting in order to show the list of revisions deleted per node at the end of the process. With the hotfix in this release the output is the following:

$ drush node-revision-delete --show-deleted article 2 -v
Deleted 2 revisions for node with nid 289                                                                                                  [status]
Deleted 14 revisions for node with nid 300                                                                                                [status]
Command dispatch complete                                                                                                                     [notice]

The above message can be seeing in the browser when revisions are asked to be deleted at http://mysite/admin/config/content/node_revision_delete.