{"type":"rich","version":"1.0","provider_name":"phorkie","provider_url":"https:\/\/p.cweiske.de\/","title":"TYPO3: ext_localconf.php vs. ext_tables.php","author_name":"Christian Weiske","cache_age":86400,"width":900,"height":900,"html":"\n\n
\n
\n
\n \n
\n\n\n

https:\/\/docs.typo3.org\/typo3cms\/ExtbaseFluidBook\/b-ExtbaseReference\/Index.html<\/a> says:<\/p>\n

\nYou 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>\n

Also see https:\/\/docs.typo3.org\/typo3cms\/CoreApiReference\/ExtensionArchitecture\/ConfigurationFiles\/Index.html#extension-configuration-files<\/a><\/p>\n<\/div>\n\n <\/div>\n

\n view raw source<\/a>\n help.rst<\/a>\n <\/div>\n<\/div>\n<\/div>\n"}