#85006Reduce falsely reported broken links
Description
Falsely reported broken links are currently a main factor that makes link fixing with Linkvalidator tedious and annoying: there is no way to remove them from the list of broken links. When searching for links to fix, you have to check several that are not really an error. Furthermore, these stay in the list while the real broken links will disappear, so after fixing more links the ratio of falsely reported broken links to real broken links worsens.
By “falsely reported broken links” we mean links that Linkvalidator shows as broken but that are either not broken or that cannot be edited by the editor or some other reason why they are either irrelevant or cannot be fixed.
We already have several issues and open patches addressing these issues. This EPIC serves to give an overview.
Main reasons for false broken links
- external link checking may fail. This means we will get false negatives links that actually work but are evaluated as “broken” by linkvalidator). We already improved here, but it still may happen. (see #89488, #86918)
- Some links are not broken, but will not return HTTP Status Code 200. This are for example pages that require a login (403, 401).
- broken links are in some fields that are no longer relevant, e.g. in tt_content.bodytext for content elements that do not use bodytext. This may happen if tt_content.ctype is changed (e.g. to plugin), which may often happen on older sites. (see #89182)
- FIXED: the editor has no permission to edit the field or the record (#84214)
- the broken link information is “stale”, meaning, the broken link has already been fixed but linkvalidator has not rechecked the field or the record has been deleted (see #89426, #83847)
Ideas for reducing false broken links
do not check some external links
- Make it possible to exclude URLs from link checking in the configuration (TSconfig), e.g. URLs starting with http://intranet.mysite.com/
- Make it possible to exclude a specific link from link checking (in the RTE)
- For more ease of use: In the list of broken links: add an action button to click on which will add the URL to the ignore URLs
check sooner
- ideally, the broken link information should be updated as soon as a record is changed (e.g. broken links in list of broken links removed, as soon as record is deleted), e.g. by using NEW / UPDATE / DELETE events
- alternatively, link checking could be done incrementally and more often, only checking the records that changed (see #92220)
do not check some fields
- only check fields that will be rendered, e.g. not tt_content.bodytext for ctype=‘plugin’, etc. (see #89182)
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Subtasks 8
- Feature #83847Linkvalidator should remove repaired links from report after editing record
- Bug #84214Linkvalidator should not check records without write permissions
- Feature #85127linkvalidator: Add possibility to exclude specific external URLs / domains or patterns
- Bug #86918Linkvalidator stops working on specific links (external URLs)
- Bug #89182Linkvalidator should only check relevant fields in table
- Bug #89488HTML special characters fool linkvalidator
- Feature #92297Make it possible to mark specific links to not get checked by linkvalidator
- Bug #101670Linkvalidator reports some external URLs as "false positives"
Related issues 6
- Task #89287Make linkvalidator crawling polite
- Feature #92822Ignore button for link targets
- Feature #96447Linkvalidator concept & open decisions
- Feature #96525Add the possibility to repport only 404 errors (Don't show 403, 999 LinkedIn and SSL problems)
- Bug #97937Linkvalidator: Links and in tt_content.bodytext cause problems in UrlSoftReferenceParser
- Bug #99909False positive broken links by parsing URLs not inside <a> tags
Files 1
History 24
-
Riccardo De Contardi changed category <span data-processor="relativetime" data-value="2018-05-27T17:53:23+00:00" > 05/27/18, 17:53 </span>
-
Sybille Peters changed subject
Improve broken link handling in TYPO3 / linkvalidator rewriteEpic: Improve broken link handling in TYPO3 / linkvalidator rewrite <span data-processor="relativetime" data-value="2018-05-31T13:09:37+00:00" > 05/31/18, 13:09 </span> -
Patrick Broens changed Related to #84016 <span data-processor="relativetime" data-value="2018-07-16T16:09:49+00:00" > 07/16/18, 16:09 </span>
-
Patrick Broens changed Related to #85576 <span data-processor="relativetime" data-value="2018-07-16T16:10:15+00:00" > 07/16/18, 16:10 </span>
-
Lina Wolf changed Related to #89177 <span data-processor="relativetime" data-value="2019-09-15T13:38:12+00:00" > 09/15/19, 13:38 </span>
-
Sybille Peters changed Related to #86918 <span data-processor="relativetime" data-value="2019-09-23T19:55:39+00:00" > 09/23/19, 19:55 </span>
-
Sybille Peters changed subject
Epic: Improve broken link handling in TYPO3 / linkvalidator rewriteEpic: Improve broken link handling in TYPO3 / linkvalidator <span data-processor="relativetime" data-value="2019-10-18T15:18:31+00:00" > 10/18/19, 15:18 </span> -
Sybille Peters changed subject
Epic: Improve broken link handling in TYPO3 / linkvalidatorReduce falsely reported broken links description <span data-processor="relativetime" data-value="2019-11-10T09:05:21+00:00" > 11/10/19, 09:05 </span> -
Sybille Peters changed
Related to #84016<span data-processor="relativetime" data-value="2019-11-10T09:27:09+00:00" > 11/10/19, 09:27 </span> -
Sybille Peters changed
Related to #85576<span data-processor="relativetime" data-value="2019-11-10T09:27:33+00:00" > 11/10/19, 09:27 </span> -
Sybille Peters changed
Related to #89177<span data-processor="relativetime" data-value="2019-11-10T09:27:42+00:00" > 11/10/19, 09:27 </span> -
Sybille Peters commented <span data-processor="relativetime" data-value="2019-11-10T09:28:52+00:00" > 11/10/19, 09:28 </span>
-
Sybille Peters changed description <span data-processor="relativetime" data-value="2019-11-10T09:37:35+00:00" > 11/10/19, 09:37 </span>
-
Sybille Peters changed attached ignore-url.png description <span data-processor="relativetime" data-value="2020-09-12T18:51:00+00:00" > 09/12/20, 18:51 </span>
-
Sybille Peters changed removed the assignee <span data-processor="relativetime" data-value="2021-04-19T13:36:59+00:00" > 04/19/21, 13:36 </span>
-
Rémy DANIEL changed Related to #99909 <span data-processor="relativetime" data-value="2023-08-06T06:46:00+00:00" > 08/06/23, 06:46 </span>
-
Rémy DANIEL changed Related to #96525 <span data-processor="relativetime" data-value="2023-08-06T06:46:23+00:00" > 08/06/23, 06:46 </span>
-
Rémy DANIEL changed Related to #92822 <span data-processor="relativetime" data-value="2023-08-06T06:46:47+00:00" > 08/06/23, 06:46 </span>
-
Rémy DANIEL changed Related to #89287 <span data-processor="relativetime" data-value="2023-08-06T06:47:16+00:00" > 08/06/23, 06:47 </span>
-
Sybille Peters changed description <span data-processor="relativetime" data-value="2023-08-13T06:33:22+00:00" > 08/13/23, 06:33 </span>
-
Sybille Peters changed subtask #101670 <span data-processor="relativetime" data-value="2023-08-13T06:39:37+00:00" > 08/13/23, 06:39 </span>
-
Ralf Hettinger changed Related to #97937 <span data-processor="relativetime" data-value="2024-03-20T15:43:38+00:00" > 03/20/24, 15:43 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-10-23T06:58:21+00:00" > 10/23/26, 06:58 </span>closing the issue to cleanup forge a bit. I set a relation to the main issue #96447
-
Georg Ringer changed Related to #96447 <span data-processor="relativetime" data-value="2026-10-23T06:58:32+00:00" > 10/23/26, 06:58 </span>
I changed, title, description and subtask to make this EPIC more focused.