Bug #82033

extbase parameters in FLUIDTEMPLATE : configuration lost for extension Form

Added by RVVN no-lastname-given over 3 years ago. Updated about 3 years ago.

Status:
New
Priority:
Must have
Assignee:
-
Category:
Extbase
Target version:
-
Start date:
2017-08-03
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

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 ?


Related issues

Related to TYPO3 Core - Bug #72600: Singleton ConfigurationManager creates problems with nested extbase pluginsNew2016-01-08

Actions
#1

Updated by RVVN no-lastname-given over 3 years ago

  • Description updated (diff)

I'm using TYPO3 8.7.4

#2

Updated by RVVN no-lastname-given over 3 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.

#3

Updated by RVVN no-lastname-given over 3 years ago

  • Subject changed from extbase parameters in FLUIDTEMPLATE : configuration lost for extension to extbase parameters in FLUIDTEMPLATE : configuration lost for extension Form
#4

Updated by RVVN no-lastname-given about 3 years ago

  • Priority changed from -- undefined -- to Must have
#5

Updated by Bjoern Jacob about 3 years ago

  • Category set to Form Framework

We will look into this.

#6

Updated by RVVN no-lastname-given about 3 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.

#7

Updated by Bjoern Jacob about 3 years ago

  • Category changed from Form Framework to Extbase

Thx, maybe "Extbase" is the better category.

#8

Updated by Benni Mack 8 months ago

  • Related to Bug #72600: Singleton ConfigurationManager creates problems with nested extbase plugins added

Also available in: Atom PDF