Help! I just upgraded our Drupal site and upgraded Revisioning & Module Grants to latest (6.x-2.2 and 6.x-2.3 respectively). We have no workflow in place, just different roles who have different permissions set.
From "My Content", I can see "pending" content, but when I click on the date stamp, I cannot edit a node -- I have to click on the list of revisions, click on the revision I want to change, and manually replace "view" to "edit" as in the following: /node/3661/revisions/8376/view -> /node/3661/revisions/8376/edit
In addition, I cannot publish content -- I get no option to do so, even when logged in with full-permissions User 1.
I have flushed all caches and rebuilt all permissions tables for good measure.
Do I need to install TAC lite and create workflow to now be able to use Revisioning? That was not the case previously.
Thanks!
TC
Comments
Comment #1
rdeboerHi TC,
You don't need to install TAC Lite unless you want content access control by taxonomy (i.e. content that is subdivided by department or country or similar). You don't need Workflow either, if you want to keep things really simple (and make a few concessions w.r.t fine-grained access control).
If you don't use any modules that operate on the node access table (like in the basic Revisioniong tutorial), then you must grant the roles in question the "view revisions" and "edit own/any content" permissions (for selected content types) in the
node modulesection of the User management >> Permissions page.Note however, that if you do have Workflow or TAC-Lite (or both) installed, then you must switch off the "edit own/any content" permissions, because these permissions will override anything those modules attempt to do regarding content access restrictions.
Do you have any other modules enabled that may affect content access?
For the options (links) to "Edit this revision" and "Publish this revision" to appear you must tick the "edit revisions", "publish revisions" permissions on the User management >> Permissions page, section
revisioning module."I cannot publish content -- I get no option to do so, even when logged in with full-permissions User 1."
Well that's very strange, as an administrator you should automatically get all edit and publication options...
Beats me.
Comment #2
ifbyphone1 commentedRik,
Thank you for the explanation re: Workflow & TAC. I am not using anything else that affects content access. Our "Admin" role has every possible permission ticked.
Here's a little more info -- and an interesting finding:
- On PROD, I'm running Revisioning 6.x-1.2 and Module Grants 6.x-1.2. Looking at a particular node, I get my familiar three options: Edit, Publish, and Delete all Revisions. All Good.
- On DEV, I'm running Revisioning 6.x-2.2 and Module Grants 6.x-2.3. Same node. No such options.
- On both, I'm using Acquia theme for all administrative pages and a custom theme for public display. Create a node in the Acquia theme, and from then on, the node always appears on our custom theme.
For kicks, I tried turning off our custom theme on DEV. The Edit, Publish, and Delete links now appear, looking quite nice. Of course, our site then looks like crap...
So it looks like a lot changed between 1.2 and 2.2 with respect to theming the administrative functions of Revisioning and I'll need to do some catching up. Any way to avoid creating a subtheme to be able to show the Administrative controls (as they were in 1.2)?
Thanks,
TC
Comment #3
rdeboerAh... now I understand what's going on. It's not a permissions problem, it's a theming problem.
Yes, the later versions of Module Grants and Revisioning are themeable (no longer is the message area abused for hard-coded controls).
The controls are prepended to the $content template variable (rather than $message).
This looks like the same issue (but for a different theme template): #447348: Revisioning links not appearing when using custom node templates
That is, your theme probably uses a
node.tpl.phpfile (in /sites/all/themes/) with a line that looks something like:
Replace that line by
Let us know how you went.
Comment #4
rdeboerComment #5
rdeboerComment #6
rdeboer