Issue Bug Closed

#82033extbase parameters in FLUIDTEMPLATE : configuration lost for extension Form

RVVN no-lastname-given 08/03/17, 16:19 updated 10/14/26, 08:09

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 ?

Reviews 2

History 11

  1. RVVN no-lastname-given commented and changed description <span data-processor="relativetime" data-value="2017-08-03T16:35:21+00:00" > 08/03/17, 16:35 </span>

    I’m using TYPO3 8.7.4

  2. RVVN no-lastname-given commented and changed priority Should have -- undefined -- <span data-processor="relativetime" data-value="2017-08-10T18:54:46+00:00" > 08/10/17, 18:54 </span>

    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. RVVN no-lastname-given changed subject extbase parameters in FLUIDTEMPLATE : configuration lost for extension extbase parameters in FLUIDTEMPLATE : configuration lost for extension Form <span data-processor="relativetime" data-value="2017-08-10T18:57:35+00:00" > 08/10/17, 18:57 </span>

  4. Björn Jacob commented and changed category <span data-processor="relativetime" data-value="2017-09-11T21:54:10+00:00" > 09/11/17, 21:54 </span>

    We will look into this.

  5. RVVN no-lastname-given commented <span data-processor="relativetime" data-value="2017-09-11T23:19:08+00:00" > 09/11/17, 23:19 </span>

    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.

  6. Björn Jacob commented and changed category <span data-processor="relativetime" data-value="2017-09-11T23:27:49+00:00" > 09/11/17, 23:27 </span>

    Thx, maybe “Extbase” is the better category.

  7. Benni Mack commented and changed status New Closed <span data-processor="relativetime" data-value="2026-10-14T08:09:56+00:00" > 10/14/26, 08:09 </span>

    The original exception (#1289843275 “extensionName” is not properly configured) can no longer be reproduced on current versions, so I’m closing this issue.

    - The TypoScript in the report has plugin and extension name swapped. For ext:form it must be extbase.pluginName = Formframework and extbase.controllerExtensionName = Form (see the ext:form docs, “Render through FLUIDTEMPLATE without controller”). The swapped values alone trigger this exception.

    - The “works only if a form plugin was rendered before” behaviour came from stale configuration caching in the Extbase ConfigurationManager (v8). Today ConfigurationManager::setConfiguration() resets its caches, and the FLUIDTEMPLATE request uses the same shared instance.

    - This exact setup (FLUIDTEMPLATE + extbase.* + formvh:render, as cached COA, uncached COA_INT and through custom Extbase plugins) is covered by the ext:form functional tests in form_caching_tests.

    The remaining problem in this area, extbase.controllerActionName being ignored for registered plugins, is handled in #96579. If you still see the problem on v13 or v14 with the correct configuration, please open a new issue with a reproducible setup.