I am using Workbench Moderation and Workbench Access, and having a really hard time setting this up to work correctly. I tried numerous times using Menu Scheme but kept running into issues. I know created a Taxonomy for my Workbench Access which I have roles applied to certain levels.

The issue I am running into is that, my author sets the node to Needs Review, my editor receives the email that a node needs review. My editor goes into the node sets the node to Published and as soon as I do that. The page displays a "Access Denied" screen. My User 1 can still see the page. I have checked the permissions and both roles are set to view published and unpublished nodes, also checked a lot of other permissions.

Can anyone assist me in figuring out why my page goes to "Access denied" on published even if my roles are set to view published nodes? This Workbench suite is very complex and needs more video tutorials.

Comments

cabplan’s picture

I found out in the drupal chat:

https://drupal.org/irc

that I needed to rebuild my permissions on content, which is found in the Status Report page. Because I changed around Workbench permissions/roles a few times.

cabplan’s picture

I am finding though that every time when I publish a node, it goes to a Access Denied, and I have to rebuild the permissions in order for it to be viewable again by that role. Why would I have to do this every time??

ryivhnn’s picture

Can happen if you have "interesting" permissions setup. Are you using TAC with Workflow or something entertaining like that?

And dumb question because I always have to ask the dumb questions: do you have all the caching off while developing?

works at bekandloz | plays at technonaturalist

cabplan’s picture

Thank you for asking, actually I was using Content Access with Workbench, once I disabled that, it seems like that fixed the publishing. Not sure if I should post another issue but I do have another, could be related to Workbench and Access.

So every time I edit a node as a "Author" who can just place node in "Needs Review" state, the URL path that was originally set, gets changed/truncated to have the word "Array" in the path, so for example:

if the original URL was: www.domainname.com/level1/level2/level3
when editing with Author it gets changed to: www.domainname.com/Array/level3

I have no idea why this is happening. I have tried changing the URL Aliases back and trying again but this keeps happening. I have checked my URL patterns and I have it set to: [node:menu-link:parent:url:path]/[node:title] which means it should show the parent path of the node being edited, and this was working. Would anyone know why this is happening? I do not want the Author to have the ability to change the URL alias

***EDIT: so even going in and editing as User 1, removing all the URL redirects and getting rid of the auto path with "Array", still produces that Array path, the only way to get the path back to normal with User 1 is I have to edit each URL redirect to be the correct path, again any insights on why this is happening would be most appreciated. Is it a Workbench thing? URL patterns thing? I am completely out of ideas

cabplan’s picture

So after more investigation, I tried to recall all the modules I installed in my dev vs staging, I realized I had a module activated called "Menu Views" when I was trying to get a View as part of the menu, I got that working with that module but did not turn it off. Apparently that was the culprit when it saves the "Array" to the node path, hope this helps others.

ryivhnn’s picture

Glad you figured it out :)

If you're getting Array in your urls it means it's probably trying to do a render array. Sometimes you need to use the :raw values for urls so make sure they're safe :)

works at bekandloz | plays at technonaturalist