--- title: "TYPO3 Exception 1237823695" manual: "TYPO3 Exceptions" version: "main" permalink: "https://docs.typo3.org/permalink/t3exceptions:typo3-exception-1237823695" source: "Exceptions/1237823695.rst" rendered: "2026-10-02T18:04:37+00:00" --- # TYPO3 Exception 1237823695 {#typo3-exception-1237823695} > [!NOTE] > Below, the TYPO3 community may have provided additional information or > solutions for this exception. However, these may or may not apply to your > particular case. If you can provide more information, you should come back > here and add your experience and solution steps to this issue once you have > resolved it. > > General TYPO3 troubleshooting tips can be found in the *Troubleshooting* > section in the menu. You can also ask questions and receive support in the > [TYPO3 Questions category on talk.typo3.org](https://talk.typo3.org/c/typo3-questions/). > > To add your experience, click "Edit on GitHub" above and follow the > ["Edit on GitHub" workflow](https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/Howto/EditOnGithub.html#docs-contribute-github-method). > Also check out > [our tip on Coding Style and reST](https://docs.typo3.org/permalink/t3exceptions:tip-about-rest-coding-style). ## General {#general} [Register arguments of viewhelpers](https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/Fluid/DevelopCustomViewhelper.html#fluid-viewhelper-custom-initializearguments) describes how to register own Arguments for viewHelpers. Never denying that I might have made a fault I never had success with the simple notation by using several parameters in the render-function. I succeeded with the solution to register the arguments in the function initializeArguments() which is automatically called if present in the viewHelper. ## PHPStorm {#phpstorm} The error shown is “Argument "xmlns:f" was not registered”. PHPStorm sometimes adds a xmlns attribute to the very first tag in a Fluid Template, if you use auto completion (eg. type in »f:comm« and hit enter to autocomplete to »\\«). If the first tag in your template happens to be a Fluid tag, then the Fluid parser will throw the execption, that »xmlns« is in fact not a valid attribute of the current Fluid tag. Issue on Forge: [https://forge.typo3.org/issues/56481](https://forge.typo3.org/issues/56481) ### Solution 1 - Remove the attribute {#solution-1-remove-the-attribute} Just remove the wrong xmlns attribute from your Fluid tag --- ``` Wrong (xmlns isn't a valid attribute for this tag): Right: ``` ### Solution 2 - Register the namespace {#solution-2-register-the-namespace} PHPStorm needs to know about the fluid namespace, then it will not add those attributes by itself anymore. Wrap your template into a DIV like this: --- ```
``` See [http://buzz.typo3.org/teams/extbase/article/howto-autocompletion-for-fluid-in-phpstorm/](http://buzz.typo3.org/teams/extbase/article/howto-autocompletion-for-fluid-in-phpstorm/) & [https://fluidtypo3.org/documentation/templating-manual/appendix/fluid-autocompletion.html](https://fluidtypo3.org/documentation/templating-manual/appendix/fluid-autocompletion.html) ## Fluid 6.1 select ViewHelper {#fluid-6-1-select-viewhelper} `Argument "prependContent" was not registered` `` `` `` - prependContent="TRUE" should be available since 6.1 [https://forge.typo3.org/issues/26595](https://forge.typo3.org/issues/26595) - No documented solution yet ## EXT:news {#ext-news} If you get this problem in the "**news**" extensions, it might be linked to the viewhelper => "hsc". Try with the original template form the extension. ## EXT:roq_newsevent {#ext-roq-newsevent} After update of roq_newsevent, (or for no apparent reason) the error appears in relation with roq_newsevent template : /Partials/EventList/item.html The viewhelper linking to single view have to be updated : Original version : \{newsItem.title}\ Updated and working version : \{newsItem.title}\ See on TYPO3 Forge here : [https://forge.typo3.org/issues/53921](https://forge.typo3.org/issues/53921) ## Upgrade to TYPO3 7.6.2 {#upgrade-to-typo3-7-6-2} The Extension Manager does not work and gives this error message: ``` Uncaught TYPO3 Exception #1237823695: Argument "jQueryNamespace" was not registered. (More information) TYPO3\CMS\Fluid\Core\Parser\Exception thrown in file /var/www/html/developer/typo3_src-7.6.2/typo3/sysext/fluid/Classes/Core/Parser /TemplateParser.php in line 604. 19 TYPO3\CMS\Fluid\Core\Parser \TemplateParser::abortIfUnregisteredArgumentsExist(array, array) /var/www/html/developer/typo3_src-7.6.2/typo3/sysext/fluid/Classes/Core/Parser/TemplateParser.php: 00563: // The following three checks are only done *in an uncached template*, and not needed anymore in the cached version 00564: $expectedViewHelperArguments = $viewHelper->prepareArguments(); 00565: $this->abortIfUnregisteredArgumentsExist($expectedViewHelperArguments, $argumentsObjectTree); 00566: $this->abortIfRequiredArgumentsAreMissing($expectedViewHelperArguments, $argumentsObjectTree); 00567: $this->rewriteBooleanNodesInArgumentsObjectTree($expectedViewHelperArguments, $argumentsObjectTree); ``` Solution: Start the Install Tool and press the button "Clear all cache". ## Removal of deprecated code in sysext fluid {#removal-of-deprecated-code-in-sysext-fluid} See [Breaking: #53542 - Removal of deprecated code in sysext fluid](https://docs.typo3.org/typo3cms/extensions/core/Changelog/7.0/Breaking-53542-DeprecatedCodeRemovalInFluid.html) For example: f:be.container arguments Error *Argument "addCssFile" was not registered* Use *includeCssFiles* instead of *addCssFile* and adapt value from string to array `addCssFile="{f:uri.resource(path:'Css/backend.css')}"` `includeCssFiles="{0:'{f:uri.resource(path:\'Css/backend.css\')}'}"`