TYPO3 Core

Tested with 10.4.9. I cannot reproduce it. Please contact me on TYPO3 Slack @sybille

I don't use Slack, so I give you some more information here:

Do you mean there are broken links in subpages but the report shows only links on current page?

Yes.

Did you verify that the broken links have been detected?

Yes

What happens if you select the subpage? Are the broken links shown?

Yes

I tested it now on a third v10 system and there it works - as on any other system I used before (7, 8, 9).
Because I use no config options for the linkvalidator and there is no error in my sys_log I have no clue how to find out what the problem is. But the behaviour is reproducible on these two v10 systems mentioned above.

Thanks for taking the time.

As already pretty obvious before, it looks like the problem is in the linkvalidator report (not in the checking itself).

I will make some suggestions to track this down - I understand if you don't want to put too much time into it, but if I can reproduce the error, I am pretty sure I would be able to fix it.

I might be able to create a "debug version" with some more logging and test output in the next few days.

Alternatively: I understand if you don't want to muck about in the code or debug in production. Also, I don't know if you are a developer, but if you are, you might be able to do this:

1. debug - I don't debug our production site, I usually work on a copy. Debugging this (e.g. with xdebug + PhpStorm) would actually be the fastest way to track down the error. If you could do this and set a breakpoint here you could step through it and might be able to see the problem pretty quickly.

Check the variables:

• $pages - should be an array of all pages (current page and subpages)
• $linktypes should be an array ['external', 'db', 'file']
• $brokenLinks should be an array of all broken links found on current page and subpages

2. You checked the sys_log. Not all is logged in sys_log. Can you also check the logfiles written by the logging framework , found in typo3temp/var/log (non-Composer) or ../var/log (in Composer based installations). (I don't expect this to yield results, but it is worth a try

3. Alternatively you could add log messages with the logging framework.

You can also contact me via email: You can see my email address in the commit messages: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66146/3//COMMIT_MSG

Thank you for your explanation how to debug. Today I wanted to check the validator, but the error is gone... Perhaps it has to do with the security update (v10.4.10), which I did yesterday? If the error occurs again, I will report.