create new revision by default

Posted by omjn on March 9, 2006 at 5:25am

Is it possible to set Drupal up such that all edits are created as new revisions by default? I find that I check this option more often than not so eliminating this step from my workflow would be convenient. On a related note, if this is possible, would this allow RSS items updated from an aggregator2 feed, where a post already exists for that title, to be updated as revisions rather than overwritten?

thanks
michael

Comments

Sure

Posted by styro on March 9, 2006 at 5:36am

In 4.6:
/admin/node/configure/types

In 4.7:
/admin/settings/content-types

--
Anton
New to Drupal? Please read this
Also: Forum posting tips

--
Anton

yup, thanks, I found this

Posted by omjn on March 9, 2006 at 5:39am

yup, thanks, I found this just after I posted my question. Should look a little harder next time...

I'm not surprised. I can't

Posted by sepeck on March 9, 2006 at 7:45am

I'm not surprised. I can't think of making this pages title descriptive enough for those options
http://drupal.org/node/29084

there are to many concepts on that page to summarize nicely. Any ideas?

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
_{Drupal Best Practices Guide -|- Black Mountain}

I have this revision issue too...

Posted by kpatrickdj on March 9, 2006 at 8:00am

I have similar issue. Changing the publish option through admin menu does not stay when I edit a node. It does reflect when I create a new node. Do you have this issue or am I misssing something? I run Drupal 4.7.0beta5 on Apache2/Php5.1/MySQL.

this was a bug in 4.7 beta5, recently fixed in HEAD

Posted by dww on March 9, 2006 at 9:04am

Changing the publish option through admin menu does not stay when I edit a node. It does reflect when I create a new node.

this was a bug in how 4.7 handles revisions that i recently reported. it has now been fixed and committed to the HEAD of cvs. so, it'll be fixed in beta6 or the 4.7 release candidate, whatever comes first. ;)

if you update directly from CVS, this problem will go away, and drupal will honor the setting in admin/settings/... if you enable "Create new revision" as the default.

__________________________________________________________________
My professional services are available through 3281d Consulting

Back in 5.1

Posted by hgmichna on July 19, 2007 at 7:13am

In Drupal 5.1 the default setting of Create new revisions for pages immediately affects all existing pages. Moreover, the setting cannot be changed for individual pages. More precisely, I can change it, but when I save and re-open the page, the setting has reverted back to its default.

Hans-Georg Michna

Mandaroty "new revision"?

Posted by mercmobily on March 9, 2006 at 7:49am

Hello,

I have an additional question about this one.
Is it possible to configure drupal so that some roles can ONLY create new revisions (rather than editing) for some specific nodes?

I am thinking specifically about Free Software Magazine: when authors edit their articles, the editor wants to be able to know what was changed!

Bye,

Merc.

yes, this is possible

Posted by dww on March 9, 2006 at 9:12am

Is it possible to configure drupal so that some roles can ONLY create new revisions (rather than editing) for some specific nodes?

yes. if the role in question does not have "administer nodes" permission, you use the latest CVS copy of 4.7 (or 4.6, which didn't have the bug i mentioned above), and set "Create new revision" as the default for a given content type, there's no way for these authors to unselect the "Create new revision" box, and all edits become new revisions of the node.

enjoy,
-derek

__________________________________________________________________
My professional services are available through 3281d Consulting

This does not work for me

Posted by marcoBauli on June 22, 2006 at 3:08pm

I am on 4.7.2.

If i masquerade as an autenticated user, i have 'create new revision' as default in the Publishing options, but i can freely uncheck it and check whatever else instead..

Any ideas why is that and how to fix?!

thx

-Marco

--
Professional Drupal Services Italy | Twitter

Check the access control

Posted by Michelle on June 22, 2006 at 3:12pm

You need administer nodes to get access to those checkboxes.

If you're getting it when masquerading as someone without that access, maybe the masquerade module is at fault. Try literally logging on as someone without that access.

Michelle

-----
_{Shell Multimedia - My sporadically updated mostly Drupal blog.}

Serious performance hit

Posted by grcm on March 9, 2006 at 9:53am

Do be very careful doing this with version 4.6 of Drupal.

The nodes are stored in a bizarre mixture of serialised PHP objects and database fields.

When a node is requested, ALL of the node's revisions are fetched from the database and then chopped up in PHP to give the required revision. So, the more revisions you have, the slower it gets. I found this out after having 100 revisions for a page; under load, the time taken for the page was obviously more than other pages. It's just not efficient to ask the database for megabytes more data than required.

Keep pruning the revisions.

Drupal 4.7 apparently used the database more correctly so this performance problem should go away. I'm looking forward to this.

-- Version Control your Drupal web site with The File High Club

-- Version Control your Drupal web site with The File High Club's Free Trial!