Revision tagging module

Events happening in the community are now at Drupal community events on www.drupal.org.

This group should probably have more organizers. See documentation on this recommendation.

This is the specification for a Drupal 5.0 module that I would like to see built. Jeremy Crowe has volunteered to build the module as a means of learning about Drupal. This group is the working group to support the efforts and to discuss the implementation of the module. Anyone interested in Drupal's revision system or in learning about how to create Drupal modules is welcome to participate.

mlncn's picture

Why a Taxonomy group

Posted by mlncn on June 19, 2007 at 10:10pm

At long last, a group exists to discuss all things taxonomy, especially managing taxonomy. The clamor can subside!

Seriously, why hasn't taxonomy had a home on groups.drupal.org before now? What can we do to ensure taxonomy is used and developed to its potential?

4 comments ⋅ Categories: taxonomy, taxonomy management

Revision tagging now a reality.

Posted by robertdouglass on February 4, 2007 at 9:36pm
Last updated by robertdouglass on Mon, 2007年02月12日 21:18

The code got a bit messed up from the marksmarty filter (would be nice to have a simple input filter). Here it is as an attachment. You have to download it and then remove the .txt file ending (and then unzip it). What hoops we jump through :p

3 comments

robertdouglass's picture

The revision tagging module

Posted by robertdouglass on November 17, 2006 at 11:30am

The revision system.

Drupal has a great feature whereby editing a node can create a revision of that node. Whenever create new revisions is checked under Publishing options, editing a node will result in a new revision. Users with the view revisions or administer nodes permissions will see a Revisions tab on node viewing pages. The Revisions tab interface allows you to view the individual revisions, revert to an earlier revision, and delete revisions.

One interesting detail of the system is the behavior of the reverting mechanism. Let's say you have revisions {1,2,3,current}. If you revert to revision #2, a copy of #2 is made and the copy is set as the current revision. Thus, after reverting you'll have {1,2,3,4,current}, where current is a clone of #2, and #4 is the previous current revision.