title: My registered namespace stops to work after logout from BE
body: <p>I have my site package extension <code>toolbox</code> with a lot of custom ViewHelpers. For not violating DRY rule I registered my own namespace (with <a href="https://docs.typo3.org/m/typo3/book-extbasefluid/master/en-us/8-Fluid/8-developing-a-custom-viewhelper.html#global-namespace-import" rel="nofollow noreferrer">global namespace import tip</a>) for recognizing it within Fluid instead placing at the beginning of each template as usually in <code>typo3conf/ext/toolbox/ext_tables.php</code> and in general that works:</p>
  <pre class="lang-php prettyprint-override"><code>$GLOBALS['TYPO3_CONF_VARS']['SYS']['fluid']['namespaces']['toolbox'] = ['BIESIOR\Toolbox\ViewHelpers'];
  </code></pre>
  <p>I can (or rather could) use my VH's like <code>&lt;toolbox:someViewHelper /&gt;</code>, however after moving page  from development to production (the same machine, just switched domains) suddenly I get an exception like:</p>
  <p><code>TYPO3Fluid\Fluid\Core\Parser\UnknownNamespaceException</code></p>
  <blockquote>
  <p><code>Fluid parse error in template Standard_action_Orangeheader_2c41396366318874342b894b22eff7acb311cc0c, line 2 at character 1. Error: Unknown Namespace: toolbox (error code 0). Template source chunk: {toolbox:containerEscape(condition: data.tx_mask_escape, start: 'true')}</code></p>
  </blockquote>
  <p>What's frustrating this problem disappears when I'm logged to BE as an admin and preview the FE in the same browser, as fast I'll logout from BE <em>and/or</em> visit required FE page in another browser, the exception comes back.</p>
  <p>As mentioned during development this problem didn't occur, after logout.</p>
  <p>ViewHelper is used in page's template included in main TypoScript with <code>FLUIDTEMPLATE</code> cObject.</p>
  <p>Had somebody such weird behaviour?</p>