Project

General

Profile

Actions

Bug #91207

closed

SiteFinder: Call to undefined method phpDocumentor\Reflection\DocBlock\Tags\InvalidTag::getType

Added by Stefan Bublies about 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2020-04-27
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Problem/Description

I hope the bug report is in the right place. If you want to use the Core siteFinder in an extension (extbase controller) you get an error that occurs in the interaction between symfony and phpDocumentor.

Affected TYPO3 versions at the time of issue-creation

10.4.0

I haven't tested it in older versions

ToDo

It is a bug in phpDocumentor. Here is ja link to the bug report: https://github.com/phpDocumentor/phpDocumentor/issues/2317 . I have currently implemented the following patch https://github.com/symfony/symfony/issues/36049 .

Actions #1

Updated by Georg Ringer about 4 years ago

  • Status changed from New to Needs Feedback

Thanks for creating the issue.

Which lines in the core code are affected and should be changed to avoid the bug? thanks for some clarification

Actions #2

Updated by Stefan Bublies about 4 years ago

Thanks for creating the issue.

Which lines in the core code are affected and should be changed to avoid the bug? thanks for some clarification

I'm sorry but I'm not very familiar with core code. I think its not a problem in the core code, it is a problem in the core code from phpDocumentor version 5.1. The quickfix in the phpDocumentor-Issue is: downgrade to version 4.3.x but typo3 10.4.x required phpDocumentor version 5.1.x.

If you use the TYPO3\CMS\Core\Site\SiteFinder in your own extbase controller with e.g. getAllSites() function you get the error. I hope this helps.

Actions #3

Updated by Gregor Agnes about 4 years ago

I downgraded phpdocumentor

"phpdocumentor/reflection-docblock": "4.3.4 as 5.1.0"

error is gone, no further issues so far.

Actions #4

Updated by Benni Mack almost 4 years ago

  • Status changed from Needs Feedback to Closed

We updated to 5.2.0 and solved the issue with the latest 10.4.6 release.

Actions

Also available in: Atom PDF