Feature #89182

Extend TSconfig configuration to allow restrictions (where) for fields

Added by Sybille Peters about 1 month ago. Updated about 1 month ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Linkvalidator
Target version:
-
Start date:
2019-09-16
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Some checks should only be performed if content is relevant.

For example:

tt_content.bodytext : depends on ctype (e.g. is usually not relevant for plugins)
pages.url : depends on doktype

The problem is currently, if page or content element type is change, the content is not removed from the fields which are now no longer relevant, so in older sites where this had been changed, you may get a lot of "broken links" for content that is not rendered in FE and is irrelevant.

If it were possible to (optionally) add restrictions to the query via TSconfig, this would solve tI have seen this problemhe problem.

In order to be backwards compatible, we could do something like:

mod.linkvalidator {

searchFields = {

  pages = media,url
}

searchRestrictions = {

  pages.url {
    ...
  }
}

Related issues

Related to TYPO3 Core - Feature #89177: Change TsConfig Defaults of Linkvalidator and Enable all core fields containing links New 2019-09-15

History

#1 Updated by Sybille Peters about 1 month ago

  • Related to Feature #89177: Change TsConfig Defaults of Linkvalidator and Enable all core fields containing links added

#2 Updated by Georg Ringer about 1 month ago

  • Description updated (diff)

Also available in: Atom PDF