1) Presently, VBO gives the option to create a new revision and even to wright a revision summary when operation *Modify node fields* is used. Wouldn't it be great to have this option for all operations allowing information to be kept about who/when/why the operation was performed?

2) Force creation of revision:

I have some node types that get a new revision whenever any user edits it (like a wiki). When using VBO the same should happen: a new revision should always be created, according to the node type settings.

Comments

infojunkie’s picture

infojunkie
Location Vancouver
CreditAttribution: infojunkie commented
Assigned: Unassigned » infojunkie

1) Good idea.

2) Yes it should.

I'll probably work on these features next week.

gpk’s picture

gpk CreditAttribution: gpk commented
Title: Diff support » Node revisions support

Just another vote for this! I was looking for a "Save new revision" operation (ideally with the opportunity to set the log message) since I needed to re-save a batch of nodes. Something like this would be ideal.

In my case I can't use "Modify node fields" because of #580090: Date_repeat - do not require UNTIL on empty date field.

infojunkie’s picture

infojunkie
Location Vancouver
CreditAttribution: infojunkie commented
Component: Code » Core
Status: Active » Closed (duplicate)

Fixed revision support lately: #689498: Using VBO to change a taxonomy value causes strange revisions on nodes with previous revisions.