Project

General

Profile

Actions

Bug #93820

closed

$contentObject = $this->configurationManager->getContentObject(); is deprecated

Added by Martin Weymayer about 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2021-03-26
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Remote Sprint

Description

Since TYPO3 9.5.25 in following was added in FormRuntime.php:

$contentObject = $this->configurationManager->getContentObject();

This occures error:
Core: Exception handler (WEB): Uncaught TYPO3 Exception: Call to a member function getContentObject() on null | Error thrown in file /var/www/vhosts/secon.users.aboliton.at/httpdocs/typo3_src-9.5.26/typo3/sysext/form/Classes/Domain/Runtime/FormRuntime.php in line 549.

But this seems deprecatet https://docs.typo3.org/c/typo3/cms-core/master/en-us/Changelog/8.0/Deprecation-68748-DeprecateAbstractContentObjectgetContentObject.html

Actions #1

Updated by Björn Jacob over 2 years ago

  • Sprint Focus set to Remote Sprint
Actions #2

Updated by Ralf Zimmermann over 2 years ago

  • Status changed from New to Needs Feedback

The deprecation affects \TYPO3\CMS\Frontend\ContentObject\AbstractContentObject (https://review.typo3.org/c/Packages/TYPO3.CMS/+/42272/12/typo3/sysext/frontend/Classes/ContentObject/AbstractContentObject.php) and not \TYPO3\CMS\Extbase\Configuration\ConfigurationManager (https://github.com/TYPO3/typo3/blob/9.5/typo3/sysext/extbase/Classes/Configuration/ConfigurationManager.php#L87).

The error messag says "Call to a member function getContentObject() on null" which means $this->configurationManager could not be injected.
The ConfigurationManager was introduced with this commit https://github.com/TYPO3/typo3/commit/66b75cecaba51df1526821dda113dc071b482d94#diff-5ac9459e18016e900b3ecc0bf1df2551bf0ca8b38b2428ec5d61e861803fafe6R198.

I'm guessing it's a caching problem. Did you clear all the system caches after the update?

Actions #3

Updated by Riccardo De Contardi over 2 years ago

  • Status changed from Needs Feedback to Closed

No feedback since the last 90 days => closing this issue.

If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.

Thank you and best regards

Actions

Also available in: Atom PDF