rich1.0phorkiehttps://p.cweiske.de/Christian Weiske86400900900<!-- embedding all files of https://p.cweiske.de/342 --> <link rel="stylesheet" href="https://p.cweiske.de/css/embed.css"/> <div class="phork" id="342"> <div class="phork-file"> <div class="phork-content"> <div class="document"> <p><a class="reference external" href="https://docs.typo3.org/typo3cms/ExtbaseFluidBook/b-ExtbaseReference/Index.html">https://docs.typo3.org/typo3cms/ExtbaseFluidBook/b-ExtbaseReference/Index.html</a> says:</p> <blockquote> You may wonder why you need to edit both, file ext_localconf.php and file ext_tables.php, to configure a plugin. The reason lays in the architecture of TYPO3: file ext_localconf.php is evaluated in the frontend and file ext_tables.php in the backend. Therefore, in file ext_tables.php we add the entry to the plugin list (for the backend). In addition, the list of controller / action combinations is required at runtime in the frontend - and therefore this must be defined in the file file ext_localconf.php.</blockquote> <p>Also see <a class="reference external" href="https://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/ConfigurationFiles/Index.html#extension-configuration-files">https://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/ConfigurationFiles/Index.html#extension-configuration-files</a></p> </div> </div> <div class="phork-meta"> <a href="https://p.cweiske.de/342/rev-raw/2e69770c8ff4ed8e006b8c6115f7acd31fa64cdd/help.rst" style="float: right">view raw source</a> <a href="https://p.cweiske.de/342#help.rst">help.rst</a> </div> </div> </div>