I want to be able to select on node type, so I can parcel out checking to people responsible for that content type. Or select on onsite vs offsite links. Off site links (especially newspaper articles) go bad frequently and people sort of expect some of them to be broken. But they expect that our own site has no internal breakage and we should prioritize fixing those.

Perhaps a better solution is to expose all the table entries to views and then I can role my own favorite scheme of parceling out the work of fixing links.

Comments

hass’s picture

hass commented

Responsibiltiy per node type sounds like a useful feature. I'm currently not sure how many code changes this requires.

#965720: Views integration for Broken Links report is the case for views integration.

Aside, have you seen the ignore domain feature? This way you could add the newspaper urls and you never get notified if they are broken. If we could #503040: Implement a trigger mechanism to call actions based on link checker test results you could also implement a much more flexible solution based on your own rules.

Not sure if we should close this case for now in favor of these two cases.

yktdan’s picture

yktdan commented

It looks like the views solution is almost there. What is needed to push it over the finish line? That would solve my problems. The trigger solution is less attractive to me.

hass’s picture

hass commented

The views patch is missing a custom access handler. Currently this allow access bypass and is a security problem.

hass’s picture

hass commented
Category: feature » support
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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