You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we declare a custom facet package with the FacetRegistry, the type is right stored in $classMap property. But with TYPO3 12, the class is declared as shared in services.yml so the class is not used as a Singleton anymore and all custom facets types registered with FacetRegistry are lost.
We expect to receive the CustomFacet object in the CustomFacet template but we receive the default "OptionFacet".
Reason
The FacetRegistry extends the AbstractClassRegistry class which implements the TYPO3 SingletonInterface.
As TYPO3 12 now use the Symfony container manager, this class must not be declared as shared in Services.yml.
Solution
Exclude the FacetRegistry class in Services.yml so won't be shared:
Describe the bug
If we declare a custom facet package with the FacetRegistry, the type is right stored in $classMap property. But with TYPO3 12, the class is declared as shared in services.yml so the class is not used as a Singleton anymore and all custom facets types registered with FacetRegistry are lost.
To Reproduce
Declare a custom facet package:
Use this facet type:
Expected behavior
We expect to receive the CustomFacet object in the CustomFacet template but we receive the default "OptionFacet".
Reason
The FacetRegistry extends the AbstractClassRegistry class which implements the TYPO3 SingletonInterface.
As TYPO3 12 now use the Symfony container manager, this class must not be declared as shared in Services.yml.
Solution
Exclude the FacetRegistry class in Services.yml so won't be shared:
Used versions (please complete the following information):
The text was updated successfully, but these errors were encountered: