Add optional capability to create new node revision and enter log message [#932522]

There are a couple related topics which lead to some enhancements in this space:
http://drupal.org/node/478152
http://drupal.org/node/689498

However, we'd still like to see the ability within VBO to optionally force a new node revision and the ability to enter a log message for the change. Our particular use-case is when mass updating taxonomies.

Thanks!

Comments

Comment #1

infojunkie

Vancouver

CreditAttribution: infojunkie commented 5 October 2010 at 20:37

Here's what I imagine for this feature:

* 2 new VBO settings:
- Force new revision
- Require log message

* If the "Require log message" is selected, a new step is added before the confirmation screen, asking for the log message.

* If the "Force new revision" is selected, or the current content type's default behaviour is to add a new revision, then a new revision is added.

Please confirm that this covers your need. As for when I can get to it, I cannot guarantee a specific time ATM :-(

Comment #2

stacysimpson CreditAttribution: stacysimpson commented 6 October 2010 at 14:29

Yep, that should cover it. Many thanks and awesome module, BTW!!!

Comment #3

Quarantine CreditAttribution: Quarantine commented 4 December 2010 at 03:11

Sorry if I'm bumping this unnecessarily, but I'm looking for the revision log feature as well.

But thanks for the awesome module infojunkie! It has definitely saved me a LOT of time.

Comment #4

_vid CreditAttribution: _vid commented 4 March 2011 at 21:06

I'd be interested in seeing this too.

Comment #5

Encarte CreditAttribution: Encarte commented 5 March 2011 at 17:38

subscribing

Comment #6

colan

he/him

English

Toronto 🇨🇦

CreditAttribution: colan commented 22 June 2012 at 15:20

Version:

6.x-1.9

» 7.x-3.x-dev

I thought this was what #1177428: Bulk operations on node revisions is broken was for, but alas, new revisions are still not being created.

Comment #7

JMTorres CreditAttribution: JMTorres commented 4 December 2014 at 22:40

Issue summary:

View changes

I just realized that VBO does not create new revisions when modifying entity values. We track all changes to our entities and just got bit when an ajax view resulted in the wrong nodes being modified. I was unable to determine the previous values because of the overwritten revision. I hope that someone can look into this request. If not, I'll try to see what's involved when I have more time.