-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
Wrong ConfigurationManager initialized in TYPO3 v11 #74
Comments
Thank you for opening this issue. Can you tell me a bit more about the impact of this? Does it affect to default CRUD handler and custom handlers? It looks like you already put some research into this. Could you give me a hint on where this should be set? Maybe as a workaround we could set |
I think he meant the following behavior:
Because the middleware is listed before the set, the ConfigurationManager loads the BackendConfigurationManager and therefore the settings set by the user cannot be loaded. Because of this I had an access "Deny" for all my urls. As a solution I set the variable "$GLOBALS['TYPO3_REQUEST']" in the middleware "RestMiddleware".
|
Thank you for the clarification. I added the code in the v6 branch. |
The global TYPO3_REQUEST is not yet present in the middleware when the ConfigurationManager gets initialized.
Threfore Extbase can not determine correctly the application mode and the BackendConfigurationManager is loaded.
This leads to issues when using extbase plugins. Extbase doesn't load the plugin configurations...
Quick solution is a middleware which sets the global variable before the rest middleware.
The text was updated successfully, but these errors were encountered: