I have been receiving a "Permission Restrictions Deny..." message on the broken links page and I have tracked it down to content that is moderated with the Workbench Moderation module. Here are a some helpful comments I have found about how the save routine with Workbench Moderation: 1811468#comment-9110519, 2244789, 1807460#comment-7999497.

I am not familiar enough with the Workbench Moderation process to say that this is the cleanest solution, but I have been testing for a month without problems. I appreciate any feedback and hope it will help others.

Brian

CommentFileSizeAuthor
#7 moderation-permission-restrictions-2872686-7.patch932 bytes.bert
#2 moderation-permission-restrictions-2872686-1.patch828 bytesnairb

Comments

nairb created an issue. See original summary.

nairb’s picture

nairb commented
StatusFileSize
new moderation-permission-restrictions-2872686-1.patch828 bytes
nairb’s picture

nairb commented
Issue summary: View changes
hass’s picture

hass commented
Status: Active » Needs review

Could you explain how to test / verify it? I'm not sue what condition your are covering with this change. Can we add this to the code, please?

Workbench moderation 3.x or 1.x or both? It should work for both as 3.x is a bit broken currently.

nairb’s picture

nairb commented

Sorry... I'm using Workbench Moderation 7.x-3.0

After fixing a broken link in moderated content, I see a "Permissions restrictions deny you access..." message on the Broken Links report page. I modified the Link Checker module to display more information with that message (lid, url, nid) so I could verify where it was coming from. What seems to be happening is that linkchecker_isdefaultrevision is not checking against the published revision. It seems that workbench_moderation['updating_live_revision'] is from Workbench Moderation 1.x and workbench_moderation['published'] is new to 3.x.

hass’s picture

hass commented

It seems that workbench_moderation['updating_live_revision'] is from Workbench Moderation 1.x and workbench_moderation['published'] is new to 3.x.

That is possible. I'm still on 1.4 because of the many issues with 3.x and have not made any tests about this yet. Looks like 3.x is not moving to stable... :-(

Version specific testing may be really hard to test. We should add comments to the code at least. While you are reroling, please fix the code style and add a space after "if"s.

2668	Expected 1 space after IF keyword; 0 found
2668	There should be no white space before a closing ")"
2669	Expected 1 space after IF keyword; 0 found
2672	Use "elseif" in place of "else if"
.bert’s picture

.bert commented
StatusFileSize
new moderation-permission-restrictions-2872686-7.patch932 bytes

A bit late for this, but here's a re-rolled version of the patch.

Not sure how this could be tested across versions, but I can confirm that the patch works well in our environment using Workbench Moderation 3.x. Really helps remove a lot of noise.

eiriksm’s picture

eiriksm
he/him
Primary language Norwegian Bokmål
Location Norway
commented

Thanks for the patch! 🙏

Can you update the issue summary with some specific steps to reproduce from a vanilla Drupal 7 install?🕵️

quadrexdev’s picture

quadrexdev
Location Lutsk
commented
Status: Needs review » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.