TypoScript Configuration Reference¶
Table of Contents
The TypoScript options configure the behaviour of the frontend plugin.
They are registered in plugin.tx_fecookies.
Tip
Most of the options are set up with constants, you’d rather want to change the values of the constants than those in setup.
Constants¶
Edit the constants in the TYPO3 Constants Editor or directly in a
sys_template record.
Templating¶
These options define the paths of the template files to be used for the
rendering. This is the well known setup for fluid-based rendering, the
options are defined in plugin.tx_fecookies.view.
Option
templateRootPath
Data type
string
Description
The template root path.
Default value: empty
Option
partialRootPath
Data type
string
Description
The partial root path.
Default value: empty
Option
layoutRootPath
Data type
string
Description
The layout root path.
Default value: empty
Settings¶
These options s are defined in plugin.tx_fecookies.settings.
Option
includeCssApi
Data type
bool
Description
If this option evaluates to true, the “CSS API” will be included in the page rendering.
Default value: 0
Option
enableCloseButton
Data type
bool
Description
If this option evaluates to true, the “close-button” will be shown by the plugin.
Default value: 0
Setup¶
As stated above, most of the options are defined using constants. The option names are the same in constants as in setup, refer to the constants documentation above. The following options have no constants configuration.
Option
settings.beforeBlocks
Data type
cObject
Description
In the dfefault template, this cObject will be rendered right before the message block records. It is invoked by:
<f:cObject typoscriptObjectPath="plugin.tx_fecookies.settings.beforeBlocks" />
Default value: TEXT (empty)
Option
settings.afterBlocks
Data type
cObject
Description
In the dfefault template, this cObject will be rendered right after the message block records. It is invoked by:
<f:cObject typoscriptObjectPath="plugin.tx_fecookies.settings.beforeBlocks" />
Default value: TEXT (empty)
Default style¶
The default style is included in the static template “Frontend Cookies:
Default style”, which only defines
plugin.tx_fecookies._CSS_DEFAULT_STYLE.
Other configurations¶
In the static template “Frontend Cookies: Base”, there are some further
definitions. We assume, that the default PAGE object is configured as
page = PAGE. If you use some other naming (eg. mypage = PAGE),
be sure to register the needed scripts for it as well to get the frontend
plugin to work correctly.
Example:
mypage = PAGE
// ...
mypage.includeJSFooterlibs.fe_cookies < page.includeJSFooterlibs.fe_cookies
mypage.includeCSSLibs.fe_cookies < page.includeCSSLibs.fe_cookies