for some (not all) link, we get the message :
"Permission restrictions deny you access to this broken link."

in fact, that means that this link is in a node which is using another language that the one you are actually using.

an exemple :
i choose french on my home page : all links coming from french nodes are correctly checked and shown.
if i have broken links in an english or german or ... written node, i'll get this message for each one.

the solution is :
back to mainpage, choose english and check links ... back to main page, choose german ... and so on

If anybody has the solution for arabic or chinese ;-D

This joke could be not only a joke :
i mean is it really a bug ?
because when you don't speak chinese or arabic, do you really need to see the link ?
May be a little change in the message :
"Permission restrictions or a language different from that of the user deny you access to this broken link."

Comments

hass’s picture

Status: Active » Postponed (maintainer needs more info)

Normally this should only happen, if the link is in a field with limited permissions and You have no access to this field. Is this possible?

asPagurus’s picture

Status: Postponed (maintainer needs more info) » Active

I have the same problem - part of rows tells me: "Permission restrictions deny you access to this broken link"
But I don't know why - I am admin and switch on all checkboxes in linkchecker's permissions.
I have 2 languages on my site - russian and english, but switching from one to anothe in my user account doesn't change situation.

hass’s picture

Status: Active » Postponed (maintainer needs more info)

Subscribing is not more info. Do you have site admin permissions?

asPagurus’s picture

Status: Postponed (maintainer needs more info) » Active

Yes I have admin permissions. Tell me please where I have to look for..

hass’s picture

Try again as user 1 please. Same?

stg11’s picture

I have the same problem when logged on as user 1

stg11’s picture

question: is this message generated for unpublished nodes?

hass’s picture

Priority: Minor » Normal

No, not for unpublished nodes. It's about a broken link in a field or node you have no permission for or at least the current code give a wrong result. Must be a bug caused by the security fixes. User 1 must have all permissions. Can you debug this on your machine, please?

stg11’s picture

I don't have a debugger but I temporarily hacked the module to print the $result under this condition and it gave me resource id 153 which if matches lid in the database took me to a node instance of type book which did not have any added fields. However the taxonomy connection was missing after upgrade from D5 on this content type. I think this was all a red herring because when I cleared the linkchecker and reran the analysis, all these messages went away. I suspect that this condition is happening when nodes are edited to clean up the broken links but not all of the links in a node are corrected. I'm pretty sure this was the case, but I did not do testing to see whether or not I could reproduce the problem based on this scenario. My recommendation to users of this module for now is: try running the maintenance to clear the linkchecker results and re-analyze and see if this eliminates these errors for you.

hass’s picture

This is a very good start to better understand the source if the issue! It's enough to re-analyze only - no need to clear! This will fix any inconsistencies... I only wonder how this inconsistency came in... :-( was the link 153 in your book page?

The main reason could be that i fixed a number of bugs regarding local paths and relative paths... Damn... Everyone should better run the re-analysis :-(

hass’s picture

Title: "permission restrictions" in reports -> run re-analyze only task once after upgrade » "permission restrictions" in reports -> run re-analyze only task

Setting to support.

Everyone in here, please re-analyze only and see if this fixes the issue. If not, reopen the case, please.

In last case, also try to add some prints and check if the lid url is in the content of the referencing content. You can find out by selecting lid on linkchecker_nodes/comment/block table to find the node id's.

hass’s picture

Title: "permission restrictions" when using module "internationalization" » "permission restrictions" in reports -> run re-analyze only task once after upgrade
Category: bug » support
Status: Active » Fixed
asPagurus’s picture

Yes! It works)
After clicking on "Reanalyze content for links" all "Permission..." had gone out.
---
And thank you very much for your module))

uschwantag’s picture

Title: "permission restrictions" in reports -> run re-analyze only task » "permission restrictions" in reports -> run re-analyze only task once after upgrade
Status: Fixed » Active

After the upgrade to 2.5, all broken links showed as "Permission restrictions deny you access to this broken link." Re-analyzing or clearing did not help. Eventually, I disabled linkchecker, uninstalled, then re-enabled. Now approximately half of all links show as "Permission restrictions...". I re-analyzed again, no change. I am doing all this as user 1. For debugging, I changed the code to append $link->lid to the Permission message. I found that some of the links are broken images on anonymously available pages. Other links do not appear on the nodes where the linkchecker_nodes table says they should appear. i18n is enabled on this site. Can you help? Thanks.

hass’s picture

Status: Active » Fixed

As others confirmed that this re-analyze works and I do understand very well why, you need to debug yourself. You must have any other issue than this here. So open a new case please.

tinker’s picture

For those running multilingual sites using i18n, where reanalyze does not work, you may want to look at issue #1488572: i18n: "Permission restrictions deny" all broken links in other languages

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

mc0e’s picture

The "Permission restrictions deny you access to this broken link." message also appears when using the Domain Access module if the node is in a different domain to the one currently being viewed.

mofdi’s picture

Issue summary: View changes