- * @param string $main The main module key, $sub is the submodule key. So $main would be an index in the $TBE_MODULES array and $sub could be an element in the lists there.

- * @param string $sub The submodule key. If $sub is not set a blank $main module is created.

- * @param string $position Can be used to set the position of the $sub module within the list of existing submodules for the main module. $position has this syntax: [cmd]:[submodule-key]. cmd can be "after", "before" or "top" (or blank which is default). If "after"/"before" then submodule will be inserted after/before the existing submodule with [submodule-key] if found. If not found, the bottom of list. If "top" the module is inserted in the top of the submodule list.

- * @param string $path The absolute path to the module. If this value is defined the path is added as an entry in $TBE_MODULES['_PATHS'][ main_sub ] = $path; and thereby tells the backend where the newly added modules is found in the system.

- * Adds an entry to the "ds" array of the tt_content field "pi_flexform".

- * This is used by plugins to add a flexform XML reference / content for use when they are selected as plugin or content element.

- *

- * @param string $piKeyToMatch Plugin key as used in the list_type field. Use the asterisk * to match all list_type values.

- * @param string $value Either a reference to a flex-form XML file (eg. "FILE:EXT:newloginbox/flexform_ds.xml") or the XML directly.

- * @param string $CTypeToMatch Value of tt_content.CType (Content Type) to match. The default is "list" which corresponds to the "Insert Plugin" content element. Use the asterisk * to match all CType values.

- * When adding a frontend plugin you will have to add both an entry to the TCA definition of tt_content table AND to the TypoScript template which must initiate the rendering.

- * Since the static template with uid 43 is the "content.default" and practically always used for rendering the content elements it's very useful to have this function automatically adding the necessary TypoScript for calling your plugin. It will also work for the extension "css_styled_content"

- * Call this method to add an entry in the static template list found in sys_templates

- * "static template files" are the modern equivalent (provided from extensions) to the traditional records in "static_templates"

- * FOR USE IN ext_localconf.php FILES

- *

- * @param string $extKey Is of course the extension key

- * @param string $path Is the path where the template files (fixed names) include_static.txt (integer list of uids from the table "static_templates"), constants.txt, setup.txt, and include_static_file.txt is found (relative to extPath, eg. 'static/'). The file include_static_file.txt, allows you to include other static templates defined in files, from your static template, and thus corresponds to the field 'include_static_file' in the sys_template table. The syntax for this is a commaseperated list of static templates to include, like: EXT:css_styled_content/static/,EXT:da_newsletter_subscription/static/,EXT:cc_random_image/pi2/static/

- * Adds $content to the default TypoScript setup code as set in $GLOBALS['TYPO3_CONF_VARS'][FE]['defaultTypoScript_setup']

- * Prefixed with a [GLOBAL] line

- * FOR USE IN ext_localconf.php FILES

- *

- * @param string $content TypoScript Setup string

- * @return void

- */

- static public function addTypoScriptSetup($content) {

- self::appendToTypoConfVars('FE', 'defaultTypoScript_setup', '

-[GLOBAL]

-' . $content);

- }

-

- /**

- * Adds $content to the default TypoScript constants code as set in $GLOBALS['TYPO3_CONF_VARS'][FE]['defaultTypoScript_constants']

- * Prefixed with a [GLOBAL] line

- * FOR USE IN ext_localconf.php FILES

- *

- * @param string $content TypoScript Constants string

- * @return void

- */

- static public function addTypoScriptConstants($content) {

- self::appendToTypoConfVars('FE', 'defaultTypoScript_constants', '

-[GLOBAL]

-' . $content);

- }

-

- /**

- * Adds $content to the default TypoScript code for either setup or constants as set in $GLOBALS['TYPO3_CONF_VARS'][FE]['defaultTypoScript_*']

- * (Basically this function can do the same as addTypoScriptSetup and addTypoScriptConstants - just with a little more hazzle, but also with some more options!)

- * FOR USE IN ext_localconf.php FILES

- *

- * @param string $key Is the extension key (informative only).

- * @param string $type Is either "setup" or "constants" and obviously determines which kind of TypoScript code we are adding.

- * @param string $content Is the TS content, prefixed with a [GLOBAL] line and a comment-header.

- * @param string $afterStaticUid Is either an integer pointing to a uid of a static_template or a string pointing to the "key" of a static_file template ([reduced extension_key]/[local path]). The points is that the TypoScript you add is included only IF that static template is included (and in that case, right after). So effectively the TypoScript you set can specifically overrule settings from those static templates.

+ * @param string $main The main module key, $sub is the submodule key. So $main would be an index in the $TBE_MODULES array and $sub could be an element in the lists there.

+ * @param string $sub The submodule key. If $sub is not set a blank $main module is created.

+ * @param string $position Can be used to set the position of the $sub module within the list of existing submodules for the main module. $position has this syntax: [cmd]:[submodule-key]. cmd can be "after", "before" or "top" (or blank which is default). If "after"/"before" then submodule will be inserted after/before the existing submodule with [submodule-key] if found. If not found, the bottom of list. If "top" the module is inserted in the top of the submodule list.

+ * @param string $path The absolute path to the module. If this value is defined the path is added as an entry in $TBE_MODULES['_PATHS'][ main_sub ] = $path; and thereby tells the backend where the newly added modules is found in the system.

+ * Adds an entry to the "ds" array of the tt_content field "pi_flexform".

+ * This is used by plugins to add a flexform XML reference / content for use when they are selected as plugin or content element.

+ *

+ * @param string $piKeyToMatch Plugin key as used in the list_type field. Use the asterisk * to match all list_type values.

+ * @param string $value Either a reference to a flex-form XML file (eg. "FILE:EXT:newloginbox/flexform_ds.xml") or the XML directly.

+ * @param string $CTypeToMatch Value of tt_content.CType (Content Type) to match. The default is "list" which corresponds to the "Insert Plugin" content element. Use the asterisk * to match all CType values.

+ * When adding a frontend plugin you will have to add both an entry to the TCA definition of tt_content table AND to the TypoScript template which must initiate the rendering.

+ * Since the static template with uid 43 is the "content.default" and practically always used for rendering the content elements it's very useful to have this function automatically adding the necessary TypoScript for calling your plugin. It will also work for the extension "css_styled_content"

+ * Call this method to add an entry in the static template list found in sys_templates

+ * "static template files" are the modern equivalent (provided from extensions) to the traditional records in "static_templates"

+ * FOR USE IN ext_localconf.php FILES

+ *

+ * @param string $extKey Is of course the extension key

+ * @param string $path Is the path where the template files (fixed names) include_static.txt (integer list of uids from the table "static_templates"), constants.txt, setup.txt, and include_static_file.txt is found (relative to extPath, eg. 'static/'). The file include_static_file.txt, allows you to include other static templates defined in files, from your static template, and thus corresponds to the field 'include_static_file' in the sys_template table. The syntax for this is a commaseperated list of static templates to include, like: EXT:css_styled_content/static/,EXT:da_newsletter_subscription/static/,EXT:cc_random_image/pi2/static/

+ * Adds $content to the default TypoScript setup code as set in $GLOBALS['TYPO3_CONF_VARS'][FE]['defaultTypoScript_setup']

+ * Prefixed with a [GLOBAL] line

+ * FOR USE IN ext_localconf.php FILES

+ *

+ * @param string $content TypoScript Setup string

+ * @return void

+ */

+ static public function addTypoScriptSetup($content) {

+ self::appendToTypoConfVars('FE', 'defaultTypoScript_setup', '

+[GLOBAL]

+' . $content);

+ }

+

+ /**

+ * Adds $content to the default TypoScript constants code as set in $GLOBALS['TYPO3_CONF_VARS'][FE]['defaultTypoScript_constants']

+ * Prefixed with a [GLOBAL] line

+ * FOR USE IN ext_localconf.php FILES

+ *

+ * @param string $content TypoScript Constants string

+ * @return void

+ */

+ static public function addTypoScriptConstants($content) {

+ self::appendToTypoConfVars('FE', 'defaultTypoScript_constants', '

+[GLOBAL]

+' . $content);

+ }

+

+ /**

+ * Adds $content to the default TypoScript code for either setup or constants as set in $GLOBALS['TYPO3_CONF_VARS'][FE]['defaultTypoScript_*']

+ * (Basically this function can do the same as addTypoScriptSetup and addTypoScriptConstants - just with a little more hazzle, but also with some more options!)

+ * FOR USE IN ext_localconf.php FILES

+ *

+ * @param string $key Is the extension key (informative only).

+ * @param string $type Is either "setup" or "constants" and obviously determines which kind of TypoScript code we are adding.

+ * @param string $content Is the TS content, prefixed with a [GLOBAL] line and a comment-header.

+ * @param string $afterStaticUid Is either an integer pointing to a uid of a static_template or a string pointing to the "key" of a static_file template ([reduced extension_key]/[local path]). The points is that the TypoScript you add is included only IF that static template is included (and in that case, right after). So effectively the TypoScript you set can specifically overrule settings from those static templates.