Home/ Questions/Q 719473
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T05:38:45+00:00

I’ve been looking for a good way to handle revisions in Drupal, but I

  • 0

I’ve been looking for a good way to handle revisions in Drupal, but I am yet to succeed. For some reason there is no built in way to save a draft (that I’ve found so far), and the modules I’ve tried so far do not seem to fully work. First I tried save_as_draft, which seemed to do almost what I wanted, and if I’m not mistaken, also handles CCK fields. Sadly it seems to be broken somehow, so I can’t edit a page once I’ve saved it as a draft.. maybe I could fix it by going through the code, but that would not be my preferred solution. The other module I tried is aptly named draft, but from what I can tell, this module only handles the title and body fields, and does this in a way that appear odd to me.

Is there some common practice to solve this? I couldn’t imagine that nobody had to solve this before, but I haven’t found any good solution to it yet.

Clarification
I need this functionality for already existing content, that is, I want to be able to create and edit a draft version of an already published page, while the “old” version would
still be available to anonymous users.

Example
On my Drupal site I have a page with current information about something, for example an event occuring this week. There is also an event occuring next week, and the information will be located on the same page (node). What I want to do is to be able to create a new revision of this event page, update it, upload new images etc, and when the time is right I want to make this new revision the current one. To achieve this the presently current revision will have to remain published the whole time, and available to anonymous users. At the same time there would be a second, unpublished revision that editors can access and edit, and publish when desired.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    FYI, if you use Publish/Unpublish, admins need Administer Nodes in order to see unpublished nodes and that is usually too much access for non-root (user 1) admins, which would be a problem if your site or any site had more than one person accessing the backend. It is not meant to be a ‘wiki’ like function.

    There is a Revisions module and a Content Moderation module that may suit your needs.

    http://drupal.org/project/revisioning

    http://drupal.org/project/content_moderation

    • 0