Bug #82033
openextbase parameters in FLUIDTEMPLATE : configuration lost for extension Form
0%
Description
Hi,
I have a formvh:render ViewHelper in a Fluid template. I created a simple FLUIDTEMPLATE content element in typoscript and apply extbase parameters according to Form documentation (source : https://docs.typo3.org/typo3cms/extensions/form/Concepts/FrontendRendering/Index.html#render-through-fluidtemplate-without-controller ) like this :
page.999 = COA_INT page.999 { 10 = FLUIDTEMPLATE 10 { file = path/to/fluid/template/file extbase.pluginName = Form extbase.controllerExtensionName = Formframework extbase.controllerName = FormFrontend extbase.controllerActionName = perform } }
I get the following exception from Extbase RequestBuilder class.
#1289843275: "extensionName" is not properly configured. Request can't be dispatched!
The configuration retrieved by loadDefaultValues function doesn't contain 'extensionName' nor 'pluginName' keys.
However the configuration is OK just after $configurationManager->setConfiguration(...) and before calling RequestBuilder->build().
If I omit the FLUIDTEMPLATE extbase parameters, the resulting generated form action misses plugin and controller, as following :
url/of/form/page/?tx__%5Baction%5D=perform&tx__%5Bcontroller%5D=Standard&cHash=ef4c51cd374b8ae9622a59f6b467f49b#testForm
Any help ?
Updated by RVVN no-lastname-given over 7 years ago
- Priority changed from Should have to -- undefined --
Hi everyone,
I have new information about this issue :
If I insert a form plugin on a page BEFORE (in the sense of content order) my previous TypoScript code, the exception doesn't occur.
Updated by RVVN no-lastname-given over 7 years ago
- Subject changed from extbase parameters in FLUIDTEMPLATE : configuration lost for extension to extbase parameters in FLUIDTEMPLATE : configuration lost for extension Form
Updated by RVVN no-lastname-given about 7 years ago
- Priority changed from -- undefined -- to Must have
Updated by RVVN no-lastname-given about 7 years ago
Thanks.
However this is not only related to Form Framework. The issue seems to occur with any extension/plugin. I've tried with "news" extension and got the same error.
Updated by Björn Jacob about 7 years ago
- Category changed from Form Framework to Extbase
Thx, maybe "Extbase" is the better category.
Updated by Benni Mack over 4 years ago
- Related to Bug #72600: Singleton ConfigurationManager creates problems with nested extbase plugins added
Updated by Garvin Hicking 4 months ago
- Related to Bug #96579: FLUIDTEMPLATE always uses default action to find the template added