tabs don't appear
richsb - March 7, 2007 - 17:36
| Project: | Revision tags |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
seems that when revisions are done on nodes that are audio or have node images attached, the revision tabs don't appear. but if an administartor edits these types of nodes, the tab will appear. any ideas? thanks -rb
#1
actually it seems that only users with admin node access can see the tabs. is there a way for users who have view revision rights to see the tabs? thanks -rb
#2
I don't think it is the tab you're looking for... after all the idea is that only people with with the 'tag revisions' can make revision tags. These are usually administrators. People with 'view tagged revisions', however, can view the different revisions that you've tagged. The method for browsing these is the block that comes with the module, so make sure and go to blocks administration and turn that block on. Then, for any node that has 2 or more tagged revisions, the block will appear.
#3
hi robert-
is it possible with this module to allow a non admin user to login, edit their own content, immediately see the revision tab so that they can track their own revsions? or does it already do this and i'm being really dense today....
#4
These are the preconditions to seeing the revision tags tab:
1. The node needs 2 or more revisions.
2. The user needs the 'view tagged revisions' to see revision tags.
3. The user needs the 'tag revisions' to actually tag them.
4. The Tagged Revisions block needs to be enabled.
Now, interestingly, on my test installation with 5.1, even without this module enabled, my test user cannot create any revisions. I'm going to assume that this is a weird bug related to some non-core module I have installed, but will check up on it tomorrow. The node gets updated, but the revision id doesn't. So every time my test user edits a node, the latest version is indeed the most recent, but it comes at the expense of overwriting the previous revision. This means that there can never be two revisions (condition #1). You can help me test and verify this by making a clean Drupal install, and seeing if a normal user without any revision permissions (and without this module) can succeed in making revisions.
#5
hi robert,
i've got a fresh drupal install with only the core modules.
my test user can edit content but the previous version does get over written and no revisions are shown. the admin can edit content and the revisions are shown. if the regular user is given administer node permission, then it will work.
#6
well, congratulations! You've found a core bug.
#7
This bug has been fixed in Druapl 6 and for Drupal 5.2. Until 5.2 is released, you can get the dev tarball here: http://drupal.org/drupal-5.x-dev
#8
thanks for the info!
#9