Delete all archived revisions instead of delete all

Hello Henry and may I welcome you to the Drupal forum as the first receiver of your post!

First of all thanks for the detailed description and use of italic and bold fonts. Most feature requests aren't this clearly formulated and formatted and I sometimes waste time trying to understand what people want to say. Not in your case.

As for your issue, I agree on both counts.
1. Not being a native English speaker I've been thinking about the right label for the "Delete all % revisions" button too. I wanted to make it clear that it didn't just mean, "delete a revision". "Delete content" is good. Would "Delete all this content" be over the top? "Delete content (% revisions)", maybe?
2. I've been thinking of putting in a "Delete archived revisions" option myself -- I don't think we'd want to include pending revisions in that delete operation, do you?

As an added extra, here's the answer to your final question. These links are added by function _revisioning_generate_node_links_according_to_permissions(), file revisioning_theme.inc. This function is called from function theme_revisioning_revisions_summary(), which is in the same file. That function passes, indirectly, the revision summary table and the links above it to the revisions-summary.tpl.php template for final rendering.

Drupal's theming engine is a topic in itself, but I hope this helps you on the road to exploring PHP and Drupal further!

Rik

My recommendation would be simply:

Unpublish/publish current | Delete archived | Delete all

Some of my users are not very clear on what a "revision" is, and tend to assume that the published revision is not a revision. Just use the terms that are already applied to each item, don't confuse them by making them think about revisions, since everything in the table is a revision anyway and the title clearly states "revisions for xxx".

I think "delete content" would be more confusing, because the term "content" is not used anywhere in that table. I know at least some of my users will take that to mean "delete all content", for the whole site!

Thank you both for your insights...
Decisions, decisions...

+1

Implemented and checked into repository, master branch.

Will be available in next release, 7.x-1.1

Cheers for that. What are the chances of a backport to 6.x?

@John Pitcairn, #6:
That should be fairly straightforward....
But time is precious...

Of course. I nostly want it for my own management rather than for my clients to use, so I have no budget at present, but if one of them requests it I'll happily take a look at a backport myself, and provide a patch if so.

I will probably have some time next week to backport a couple of D7 goodies to D6. But no firm guarantee...

Available in 6.x-3.13 and 7.x-1.2

EDIT: works as expected