#89177Change TsConfig Defaults of Linkvalidator and Enable all core fields containing links
Description
The linkvalidator’s default PageTsConfig currently contains fields that cannot be checked by the linkvalidator anyway like pages:media. And fields that you would expect to work automatically like pages:canonical_url and sys_file_reference:link are missing. At least those core fields that might have an inpacto on the frontend should be in the default PageTsConfig
In the time being only files containing softrefs are working. So the list below shows fields with soft an hardrefs. Some of the hardrefs should be easy to implement as you can already get the expected type (i.e. group of pages or inline of sys_refs) other would require additional configuration to tell you what kind of content is expected and should be testes for (like fe_users:www or sys_filemounts:path)
The following fields in core tables may contain links to pages, files or external urls:
be_groups- lockToDomain softref substitute
- email softref email[subst]
- lockToDomain softref substitute
- felogin_redirectPid hard, group of pages
- lockToDomain hard, trimmed input
- email hard, trimmed input
- image hard, inline, sys_file_reference
- lockToDomain hard, trimmed input
- www, hard, trimmed input
- canonical_link, softref, typolink
- content_from_pid, hard, group, pages
- email softref email[subst]
- media, hard, inline, sys_file_reference
- mount_pid, hard, group of pages
- og_image, hard, inline, sys_file_reference
- twitter_image, hard, inline, sys_file_reference
- url softref url
- path hard, select itemsProcFunc
- files hard, inline sys_file_reference
- folder hard, select itemsProcFunc
- link, softref, typolink
- bodytext softref typolink_tag,email[subst],url
- file_collections hard group sys_file_collection
- header_link, softref typolink
- image, hard, inline, sys_file_reference
- media, hard, inline, sys_file_reference
- pages, hard, group of pages
- author_email, hard, input
- wsdl_url, hard, input
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
Related issues 4
History 7
-
Lina Wolf changed Related to #83835 <span data-processor="relativetime" data-value="2019-09-15T13:36:34+00:00" > 09/15/19, 13:36 </span>
-
Lina Wolf changed Related to #52912 <span data-processor="relativetime" data-value="2019-09-15T13:37:56+00:00" > 09/15/19, 13:37 </span>
-
Lina Wolf changed Related to #85006 <span data-processor="relativetime" data-value="2019-09-15T13:38:12+00:00" > 09/15/19, 13:38 </span>
-
Sybille Peters changed Related to #89182 <span data-processor="relativetime" data-value="2019-09-16T17:49:16+00:00" > 09/16/19, 17:49 </span>
-
Sybille Peters changed
Related to #85006<span data-processor="relativetime" data-value="2019-11-10T09:27:42+00:00" > 11/10/19, 09:27 </span> -
Sybille Peters changed Related to #92542 <span data-processor="relativetime" data-value="2020-10-25T01:01:02+00:00" > 10/25/20, 01:01 </span>
-
Georg Ringer commented and changed status
NewClosed <span data-processor="relativetime" data-value="2026-09-29T15:29:55+00:00" > 09/29/26, 15:29 </span>
I checked it against the current main branch; most of what can reasonably be done here is done already.
Already solved
mod.linkvalidator.searchFields { pages = link, media, canonical_link tt_content = bodytext, header_link, records sys_file_reference = link sys_redirect = target }link(e.g.tt_content.header_link,pages.canonical_link,sys_file_reference.link) are checked directly as typolink, without a soft reference parser.Not covered by this issue anymore
type=group,inline,filesuch aspages.mount_pid,pages.content_from_pid,tt_content.pages,tt_content.records, file references): the LinkAnalyzer only evaluates fields with soft references and fields of typelink. Supporting relations would be a new feature of the analyzer, not a change of the default configuration. The most relevant case, shortcut pages, is already tracked in #92542.email,www,lockToDomain): email addresses are not validated by the linkvalidator, andlockToDomainhas been removed from the core.pages.mediaandtt_content.recordsare still listed in the defaults for forward compatibility. They are skipped silently, as they are not supported yet.I’m closing this issue therefore. If checking relations (group/inline/file) is still wanted, please open a new, focused feature request for it, ideally in combination with #92542.