-
Notifications
You must be signed in to change notification settings - Fork 1
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
solution #1
Comments
Cool, thanks a lot for providing the solution to the problem. I will add an example to the TYPO3 docs so this is documented. |
I was happy to find this hint and tried it in v12 with my own xlcassed version of
Without the extra line in Services.yaml I get the error with something like Am I doing something wrong or has something changed in V12? Does the new tagging of the controller with |
I have the same issue like @stoppeye and did not find a solution. Any hints would be appreciated. I am currently working on a v12 compatible upgrade of EXT:be_acl and need to modify the PermissionController, |
@mschwemer @stoppeye If you have autowire and autoconfigure enabled for your classes try to disable them for the XClass namespaces, also they should be private. I did not tested this with all variants but it helped if the base class had private services in DI |
@lukasniestroj: thanks for your hint! Unfortunately I can't really test the use case I had, when I made my comment. I have found a completely different solution for my problem that doesn't require XClass anymore. |
Hi @derhansen ,
I stumbled upon the same issue today.
After some research I came to the solution to add a reference to the Services.yaml.
TYPO3\CMS\Belog\Controller\BackendLogController: '@Derhansen\XclassDi\Controller\ExtendedBackendLogController'
In my case I had an overwritten Controller from ext:news.
The text was updated successfully, but these errors were encountered: