Closed (fixed)
Project:
Comment Revisions
Version:
6.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
21 Jan 2009 at 02:58 UTC
Updated:
28 Feb 2011 at 23:35 UTC
Jump to comment: Most recent file
We found some bugs we hopefully fixed with our patch. The handling of permissions to administer the module was not correctly implemented. The module forgot some of its variables.
Now you can can set the maximal user revisions to unlimited, too. And you can decide if you want log messages. And the buttons to delete/revert only appear if you have the neccessary rights (reducing the number links leading to an "access denied" page).
Thanks for this wonderful module, it will help us to maintain transparency!
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | comment_revisions.tar_.gz | 12.99 KB | linksunten |
| #1 | comment_revisions.tar_.gz | 12.8 KB | linksunten |
| comment_revisions.module.diff | 9.23 KB | linksunten |
Comments
Comment #1
linksunten commentedWe added the new feature to stash a revision, i.e. make it invisible. Of course, the current revision cannot be stashed and a stashed revision cannot be reverted.
Comment #2
linksunten commentedWe found more bugs and hopefully fixed them.
IMC linksunten
Comment #3
thinkyhead commentedPatch in the OP has been incorporated into current 5.x and 6.x releases. I'm not sure whether it's very valuable to include invisible (stashed) revisions. I'd personally like this module to be as simple as Node revisions, but don't mind additional enhancements as options. Maybe we'll put in all the bells and whistles, then put a "simple revisions" checkbox in the settings for those who want to set and forget...
For now, I'm reviewing all extant patches, and will include all the good stuff in incremental releases.
Comment #4
thinkyhead commented