-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUGFIX] Create contentRecordRenderer via API #431
Conversation
Replace the Implementing of the ContentRecordRenderer with API. T3-Version-Switch not necessary.
Thanks for PR, but CI is not happy,
|
This fix works for me. |
Resolves: #433 |
@achimfritz - please merge |
$contentRecordRenderer->setContentObjectRenderer($cObj); | ||
$contentRecordRenderer->setRequest($this->getRequest()); | ||
$contentRecordRenderer = $cObj->getContentObject('RECORDS'); | ||
if ($contentRecordRenderer === null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ervaude when can this occure? (cannot imaging?) i would prefer to remove this check, and the Exception?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The check is only "useful" for phpstan because $cObj->getContentObject('RECORDS');
could return null
.
But if the RECORDS
cObject is not registered TYPO3 would not function at all.
When we remove the check we'll need a phpstan ignore-error entry.
Replace the Implementing of the ContentRecordRenderer with API. T3-Version-Switch not necessary.