Actions
Bug #101343
closedEditor frontend preview fails when having TYPO3\CMS\Extbase\Core\Bootstrap->run added to PAGE
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2023-07-13
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
12
PHP Version:
8.2
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Adding anything to PAGE like:
with ordinary ext_localconf.php
still works when:
I am logged in as admin
Not logged in in BE
But does NOT work when Im logged in BE as editor....
For some reason this comes up:
10 = USER
10 {
userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
extensionName = TcSeo
controller = Sitemap
pluginName = SeoXml
}
with ordinary ext_localconf.php
ExtensionUtility::configurePlugin(
'TcSeo',
'SeoXml',
[SitemapController::class => 'xml']
);
still works when:
I am logged in as admin
Not logged in in BE
But does NOT work when Im logged in BE as editor....
For some reason this comes up:
The default controller for extension "TcSeo" and plugin "SeoXml" can not be determined. Please check for TYPO3\CMS\Extbase\Utility\ExtensionUtility::configurePlugin() in your ext_localconf.php.
- We've tried with the newly introduced EXTBASEPLUGIN as well, which yields the same result
- Additionally I've found that it stems from the ConfigurationManager instance used, being wrong. When logged in as a non-admin user, when it injects the TYPO3\CMS\Extbase\Configuration\ConfigurationManager no TYPO3_REQUEST is found and therefore the concreteConfigurationManager is set to BackendConfigurationManager which of course does not contain the correct information about the plugins
Updated by Claus Harup about 1 year ago
Local mis-configuration - just close the issue :-)
Updated by Riccardo De Contardi 7 months ago
- Status changed from New to Closed
- Target version deleted (
Candidate for patchlevel)
@Claus Harup sorry for this late reply and thank you for your update!
I am closing this issue in agreement with the reporter.
If you think that this is the wrong decision please reopen it or open a new issue with a reference to this one.
Thank you.
Actions