Users create drafts, but they don't show up under "Manage Content" or even "My Drafts." However, when an administrator logs in, the administrator can see that user's drafts under "Manage Content." If the user that created the draft publishes it, then the node shows up under Manage Content, but drafts never do show up. Why can't users find their own drafts under "Manage Content?" Please help!

Comments

MrSasquatch’s picture

MrSasquatch commented
Priority: Normal » Major
MrSasquatch’s picture

MrSasquatch commented

We have a test server that is almost identical to the server that is having this problem. The test server is not experiencing this problem. The only differences between the two servers is that the main server was recently updated in the past week as follows...

Added Modules
============
Advanced Forum
ACL
Chain Menu Access

Updated Modules
=============
Custom Tokens
Entity Reference
FileField Sources
SMTP Authentication Support
Token

I'm not sure this has anything to do with the problem, but I thought I should mention it. Please help, is this bug is undermining the acceptance of Drupal and Workbench in our organization. Thank you very much for any assistance that anyone can provide.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Category: bug » support
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

There isn't any Workbench Access specific information reported here.

What kind of access scheme are you using?

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

Note however that ACL suggests that you are using an additional access control mechanism that might be interfering.

MrSasquatch’s picture

MrSasquatch commented

We're using Workbench, Workbench Moderation, and Workbench Access with the taxonomy scheme, not the menu scheme.

And like I mentioned, we had recently installed ACL module to support the Forum Access module.

It appears ACL is incompatible with Workbench, or vice versa. I disabled ACL, and the problem immediately disappeared, and immediately I was able to view my unpublished drafts under both "Manage Content" and "My Drafts." I tried adding ACL back in. Just enabling the ACL module did not cause any problems for Workbench Access/Moderation. But upon enabling ACL, I'm asked to "rebuild permissions." As soon as I do, that's when the Workbench Access/Moderation functionality breaks and I can no longer see my drafts under "My Drafts." I can only see published nodes when looking at "Manage Content" through Workbench. Once again, removing ACL module eliminates this problem. So it appears ACL is incompatible with Workbench, or vice versa.

I'm confused as to why ACL would interfere with Workbench Access. Supposedly ACL does nothing. It only provides functionality for other modules to use, kind of like an API.

So I'm concerned about the possible incompatibility between Workbench Access and other access control modules, because Workbench Access on its own does not "get it done." Workbench Access is great for controlling editing, but it does nothing to control viewing.

So for example, if I want to use the very popular "Content Access" module to control view access on a node-by-node basis, I can't as long as I'm using Workbench Access, because Content Access requires ACL to do the node-by-node view access. So then what do I use to control viewing of nodes on a node-by-node basis if I'm using Workbench Access?

So again, I would like to urge the maintainers of Workbench Access to add the following features:
- Section View by Role (similar to section editing by role that already exists)
- Section View by Person (similar to section editing by person that already exists)
- Node View by Role (like how Content Access does it when used in conjunction with ACL)
- Node View by Person (I'm not aware of a solution for this yet, but it would round out the feature set nicely)

Thoughts?

Thanks,
John

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Postponed (maintainer needs more info) » Active

Those Views features are in development.

ACL might break things if it starts storing empty records in {node_access}. Look there for the breakage. See if you can figure out how the Views queries are being rewritten by ACL, which I never use.

MrSasquatch’s picture

MrSasquatch commented

My Drupal development skills are not at that level. I am a site builder and a manager. So as much as I would like to help troubleshoot this incompatibility, it is not realistic, as I would probably not be helpful in that regard anytime soon.

That said, what we have here is a case where two very popular modules are not compatible. That seems to be an issue for the maintainers of ACL and Workbench. I just happen to be affected. In a case like this, how are such incompatibilities addressed? Seems to me that it would be in the best interests of both teams to resolve this issue, especially since Workbench users have been advised to use other access control solutions for view access, since Workbench only handles edit access.

Finally, what is the likelihood of the Workbench team adding those features I mentioned? Here they are again for your convenience...
- Section View by Role (similar to section editing by role that already exists)
- Section View by Person (similar to section editing by person that already exists)
- Node View by Role (like how Content Access does it when used in conjunction with ACL)
- Node View by Person (I'm not aware of a solution for this yet, but it would round out the feature set nicely)

I realize that last paragraph is kind of outside the scope of this issue, but since we're on the subject, I thought I would mention it.

As always, thanks much for all assistance and cooperation.

Thanks,
John

spouilly’s picture

spouilly commented

Hi there,

Having a similar issue, but quite different configuration :
- using Workbench Moderation only (e.g not using Workbench, neither Workbench Access),
- using my own access module (using hook_node_grant, etc.) (i.e. not using ACL),
- using my own views to list content to moderate,

Experiencing the same kind of issues :
a) admin can see the list of nodes to review, can navigate to the node and change the moderation status.
b) moderator can not see the nodes in the list to review, but can navigate to the node and change the moderation status.

If I can find the time, I will try to investigate. As a workaround, you can disable the SQL rewriting for the view.

  • go to the view used to manage moderation status
  • in advanced -> query options -> check "disable SQL rewriting"

Beware : this is the equivalent of running your view as admin ... so you need to ensure that you have set the proper filters in place to prevent your moderators from accessing unauthorized content.

Cheers,

S.

MrSasquatch’s picture

MrSasquatch commented

As agentrickard mentioned in #6, features are under development that would eliminate the need for us to develop our own view access module to work with Workbench. It sounds like these new features might be module that is part of the Workbench family of modules. Agentrickard, can you confirm that? And can you let us know *about* when such a module might become a reality? I am personally willing to help float the bill for that module in order to make it available to the entire Drupal community ASAP, rather than just one one customer. Please advise.

spouilly, my point in all of this is that, if you didn't have to use your own access module, you would probably eliminate your module conflicts, just like I did. I stopped using ACL and my problems went away.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented

I would think we'll have releasable code by the end of November. It would be a submodule of Workbench Access.

MrSasquatch’s picture

MrSasquatch commented

Yay!!! Thank you so much, agentrickard!!!

petednz’s picture

petednz commented

In case it sheds light, rather than just adding noise, I seem to be seeing something similar (with Domain Access perhaps being the culprit this time) where a user who saves something as a draft can access node/#/edit but can't see it under My Drafts.
Only issue really is how to make it easy for them to find their own 'unpublished material' - thought I might sidestep it by putting a view in place for them - but same outcome (of course) namely their 'my draft blogs' page i made shows them nothing.

Not sure if this has changed on that site (haven't had to help them wrt Workbench) for over a year.

petednz’s picture

petednz commented
Title: Allow drafts to show up under "Manage Content" » Users create drafts, but they don't show up under "Manage Content"
Version: 7.x-1.x-dev » 7.x-1.0
Component: Code » User interface
Category: feature » support
Status: Closed (won't fix) » Active

Embarrassed - we don't have Domain Access on that site. But despite Author having
Node:
View published content
View own unpublished content
View content revisions
create [content type] content
edit own [content type] content
Workbench Moderation:
View the moderation messages on a node
Use "My Drafts" workbench tab

They still can't see any of their unpublished content admin/content or workbench/drafts guess I need to go sniffing around some other issues

devin carlson’s picture

devin carlson commented
Title: Users create drafts, but they don't show up under "Manage Content" » Allow drafts to show up under "Manage Content"
Version: 7.x-1.0 » 7.x-1.x-dev
Component: User interface » Code
Category: support » feature

The default "managed content" page included with core Node module does the following:

  if (!user_access('bypass node access')) {
    // If the user is able to view their own unpublished nodes, allow them
    // to see these in addition to published nodes. Check that they actually
    // have some unpublished nodes to view before adding the condition.
    if (user_access('view own unpublished content') && $own_unpublished = db_query('SELECT nid FROM {node} WHERE uid = :uid AND status = :status', array(':uid' => $GLOBALS['user']->uid, ':status' => 0))->fetchCol()) {
      $query->condition(db_or()
        ->condition('n.status', 1)
        ->condition('n.nid', $own_unpublished, 'IN')
      );
    }
    else {
      // If not, restrict the query to published nodes.
      $query->condition('n.status', 1);
    }
  }

Which limits the unpublished nodes displayed in the table to only those that the user created, unless the user has the "bypass node access" permission. User 1 (the site administrator) would automatically have this permissions which is why they can see draft nodes from all users instead of just their own.

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Closed (won't fix)

Status: Active » Closed (won't fix)

Correcting issue status, see #2125263: Issue status not taken from last comment during D7 migration.

Aaron23’s picture

Aaron23 commented
Issue summary: View changes

I need view draft link for viewer role..Viewer role must contain only if some edit content. Can some one help me out?