By ckclarke on

A quick question from an administrator point of view - where I can I find the revision history of a node/flexinode so that I can rollback if necessary?

I can see the table for revision history in PHPAdmin, so I know it's there, and I do have the access control set so that I, as administrator have the ability to view and do a rollback. I just can't see where to access the history in the admin interface.

Thanks!

⋅ Categories: Drupal 4.7.x

Comments

sepeck’s picture

sepeck commented

On the node itself. IF there are no revisions for that node and you do not have edit node rights, I don't hink you will see a tab.

-sp
---------
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

ghoti’s picture

ghoti commented

Howdy.

Logged in as my 'admin' user, I see no revisions tab on any node, and I get an "access denied" error when I try to visit any /node/#/revisions .

I've gone into administer>access control and turned on "view" and "revert" revisions for node module, to no avail. I also tried creating a new "role" with revision permission, also without effect. I even trued opening the permissions up to unauthenticated users, also without effect. So I'm pretty confident I've covered the access control basics. I must be missing something else, but I don't know where to look for further information. I'm using 4.7.2.

Any hints?

sepeck’s picture

sepeck commented

If the node has no revisions, then there will be no tab. When you edit the node, the box labeled revision must be checked.

-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

ghoti’s picture

ghoti commented

But I've found it!

To be more clear (for others searching on this topic), we're looking at the Publishing options section, the last checkbox of which is labelled "Create new revision".

Finally! Geez, took me long enough to find that....

And a reminder for others whose searches find this thread: you can configure the default stats of this checkbox under administer > settings > content types >configure.

marcoBauli’s picture

marcoBauli commented

Does anyone have an idea of how to let create new revision be the ONLY choice for users who want to edit content on a site?!

I checked "create new revision" box for my content type in admin/settings/content-types: now this option is checked by default in my node submission form. but still users are able to uncheck it and mess around if they want...

Any idea about how to make this more restrictive?

thanks lot

BSherm’s picture

BSherm commented

Go to Administer>Access Control

Node Module section, the option is Administer Nodes. You can also give folks the permission to revert or not. This is set by user role. This locks out changing ANY of the publishing options (Published, In moderation queue, Promoted to front page, Sticky at top of lists, Create new revision).

HTH

mfh’s picture

mfh commented

i think your answer is not correct.
if I understand well, the question is :
the webmaster wants ANY edit to create necessarily a revision, (in order to be able to revert ANY edit made by the users)
If you give them permissions, this means they MAY create a new revision, but they also may not.

manerhabe’s picture

manerhabe commented

I believe you can make "create new revision" be the default by going to content management > content type > content name > and checking "create new revision" under "Default options."

motoservo’s picture

motoservo commented

If I'm understanding this thread correctly, no one has adequately answered the original question. Can Drupal be set so that any editing forces a new revision, not just makes it the default option?

sepeck’s picture

sepeck commented

Setting it as default does that. If a person has Edit nodes rights, then they can prevent a revision being creted

-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