Closed (fixed)
Project:
Link checker
Version:
6.x-2.0
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
24 Feb 2009 at 08:29 UTC
Updated:
8 Oct 2018 at 11:15 UTC
Jump to comment: Most recent
Comments
Comment #1
hass commentedNo, the broken link is listed in broken links, but there is no longer a reference link shown to the node/comment/block. Keep your cleanup time frame lower if you don't like this. You have set it to 4 weeks - this lists the link for about 4 weeks. I would use a lower value like 1 week or one day.
I'm aware about this usability issue, but I'm also not yet sure how to fix the range_query SQL statement to solve this. Please provide a patch if you know how to solve...
Comment #2
hass commentedComment #3
Anonymous (not verified) commentedHi Alexander
Thanks for the clarification. I had noticed that in some cases the reference link had disappeard after editing. Though if I remember correctly not always, i.e. when there were two links to the same destination on the node ?
I had not realsied that "Cleanup interval for unused links: " was refering to those that had been " Repaired", Does it also include links that still report an issues ?
If the Cleanup only refers to those "Repaired", a better description might be :-
"Cleanup interval for repaired links:"
with a corresponding description of :-
"This interval setting defines how often cron will clean up repaired links, (those with no link source shown)."
I used "link source", as heading of "Operations" for the column in the Broken Links report is not very descriptive, and may better be replaced with Link Source"
Comment #4
hass commentedThis are "unused links"... no longer used in content. If you have two links pointing to the same destination in one node and only repair one link - the link to the node with the broken links is kept until fixed. The cleanup stuff will hopefully go away in near future, but was kept in days where I thought the module can work without SQL subselects... as more as I'm working on it - this becomes impossible for speed reasons.
Comment #5
hass commented