Closed (fixed)
Project:
Link checker
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Jul 2014 at 01:02 UTC
Updated:
6 Feb 2023 at 02:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
hass commentedNot yet possible. Why should we implement this? It sounds not helpful.
Comment #2
StephenOTT commentedUse case: Drupal large scale migrations with enterprise clients you often run into the scenario where you are migrating multiple website content into the various content types. For recording keeping purposes we keep the "legacy" / original URL of where the content came from as a field on the node. So then when link checker runs its checks it checks this field and this field should not be checked. The user is alerted to a broken link that is not really "broken" because it is there for legacy purposes only.
There are multiple scenarios where we have come across the need for only specific fields to be checked.
Additionally it is helpful from a reporting perspective to be able to run reports against which fields have the broken links. (In large enterprise deployments you have the scenario where certain users are responsible for certain fields).
Comment #3
hass commentedWell, that is these one edgecase... I do not think this has anything to do with the size of your project or enterprise or not. Not sure why you save the old link... It looks not like something that you absolutly require to run your new website.
Function _linkchecker_parse_fields() should be the best place to skip the fields. We could add a setting into the field form.
Until today You are the second who is asking for these edge case solution. If you'd like to get this done by me you need to sponsor this feature.
Comment #4
hass commentedNo feedback.
Comment #5
dshields commentedI think this would be a useful feature for exactly the reasons Stephen outlined. I'll take a stab at patching this over the next few days and contribute a solution back here.
Comment #6
dshields commentedThis patch seems to take care of it.
This adds an option on every field's settings page to exclude that specific field from being scanned by Link Checker.
Please test and let me know if this is a decent solution to the challenge StephenOTT outlined above.
Comment #7
dshields commentedComment #9
dshields commentedOops. Bad formatting in patch in #6.
Hopefully, this passes
Comment #10
hankvanzile commentedThanks, dshields! Patch #9 worked great for me and solved my use case perfectly.
Comment #11
dshields commentedComment #13
vladimirausThank you for contributions. Committed! 🍻
Comment #14
vladimiraus