Document importance of the 'save revision' checkbox when editing nodes
Aren Cambre - December 19, 2007 - 00:33
| Project: | Diff |
| Version: | 5.x-1.1 |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
How to reproduce:
- Fresh new install of Drupal. Make sure you're only logged in as user 1.
- Enable diff 1.1 and no other modules. (At this point, the only configuration changes should be setting up user 1 and enabling that module.)
- Create a story with the following body: This is revision 1 of my story.
- Edit the same story, but change the 1 to a 2: This is revision 2 of my story.
- Notice how the Revisions tab does not show after saving the second revision.
Are there any dependencies that aren't clearly stated?
#1
you have to check the 'save revision' checkbox when editing a node. if you don't you get the behavior you do now
#2
Thanks. Changing to a documentation request to get this in the documentation.
#3
#4
Any way to get it in the user interface in addition to the documentation?
#5
we could throw a warning in hook_requirements() if none of your content types default to saving revisions.
#6
#5: "add a warning" would be nice, and preferably add a line like the below to the description section of the readme.txt?
"After enabling the module, make sure the desired content types are set to save revisions by default. (admin/content/types)"