tag, set this to 1. If the value is 2 then the <title> tag is not printed at all. Please take note that this tag is required for (X)HTML compliant output, so you should only disable this tag if you generate it manually already. Default 0 .. _setup-config-noscaleup: noScaleUp """"""""" .. container:: table-row Property noScaleUp Data type boolean Description Normally images are scaled to the size specified via TypoScript. This also forces small images to be scaled to a larger size. This is not always a good thing. If this property is set, images are **not** allowed to be scaled up in size. This parameter clears the $this->mayScaleUp var of the class TYPO3\CMS\Core\Imaging\GraphicalFunctions (often referred to as "Gifbuilder"). .. _setup-config-pagegenscript: pageGenScript """"""""""""" .. container:: table-row Property pageGenScript Data type resource Description Alternative page generation script for applications using \\TYPO3\\CMS\\Frontend\\Http\\RequestHandler for initialization, caching, stating and so on. This script is included in the global scope of \\TYPO3\\CMS\\Frontend\\Http\\RequestHandler and thus you may include libraries here. Always use include\_once for libraries. Remember not to output anything from such an included script. **All content must be set into $TSFE->content.** Take a look at typo3/sysext/frontend/Classes/Page/PageGenerator.php. **Note:** This option is ignored if :: ['FE']['noPHPscriptInclude'] => 1; is set in LocalConfiguration.php. Default typo3/sysext/frontend/Classes/Page/PageGenerator.php .. _setup-config-pagerenderertemplatefile: pageRendererTemplateFile """""""""""""""""""""""" .. container:: table-row Property pageRendererTemplateFile Data type string Description Sets the template for page renderer class TYPO3\CMS\Core\Page\PageRenderer. **Example**:: pageRendererTemplateFile = fileadmin/test_pagerender.html .. _setup-config-pagetitle: pageTitle """"""""" .. container:: table-row Property pageTitle Data type :ref:`stdWrap <stdwrap>` Description stdWrap for the page title. This option will be executed *after* all other processing options like config.titleTagFunction and config.pageTitleFirst. .. _setup-config-pagetitlefirst: pageTitleFirst """""""""""""" .. container:: table-row Property pageTitleFirst Data type boolean Description TYPO3 by default prints a title tag in the format "website: page title". If pageTitleFirst is set (and if the page title is printed), then the page title will be printed IN FRONT OF the template title. So it will look like "page title: website". Default 0 .. _setup-config-pagetitleseparator: pageTitleSeparator """""""""""""""""" .. container:: table-row Property pageTitleSeparator Data type string /:ref:`stdWrap <stdwrap>` Description The signs which should be printed in the title tag between the website name and the page title. If pageTitleSeparator is set, but *no* sub-properties are defined, then a space will be added to the end of the separator. stdWrap is useful to adjust whitespaces at the beginning and the end of the separator. **Examples**:: config.pageTitleSeparator = . This produces a title tag with the content "website. page title":: config.pageTitleSeparator = - config.pageTitleSeparator.noTrimWrap = | | | This produces a title tag with the content "website - page title":: config.pageTitleSeparator = * config.pageTitleSeparator.noTrimWrap = ||| This produces a title tag with the content "website*page title". Default : *(colon with following space)* .. _setup-config-prefixlocalanchors: prefixLocalAnchors """""""""""""""""" .. container:: table-row Property prefixLocalAnchors Data type string Description If set to one of the keywords, the content will have all local anchors in links prefixed with the path of the script. Basically this means that <a href="#"> will be transformed to <a href="path/path/script?params#">. This procedure is necessary if the <base> tag is set (e.g. if the "realurl" extension is used to produce speaking URLs). See property "config.baseURL". You can enable this function by setting it to one of the following keywords: **all:** The content is always processed before it is possibly stored in cache (or not stored in cache). **cached:** The content is only processed, if the page will be put into the cache. **output:** The content is processed just before it is echoed out. **Note:** This property is deprecated since TYPO3 7! If you still use it for now, you need to install the extension "compatibility6". In the long run, you are advised to use absolute links with config.absRefPrefix instead. .. _setup-config-removedefaultcss: removeDefaultCss """""""""""""""" .. container:: table-row Property removeDefaultCss Data type boolean Description Remove CSS generated by :ref:`\_CSS\_DEFAULT\_STYLE <setup-plugin-css-default-style>` configuration of extensions. (\_CSS\_DEFAULT\_STYLE outputs a set of default styles, just because an extension is installed.) .. _setup-config-removedefaultjs: removeDefaultJS """"""""""""""" .. container:: table-row Property removeDefaultJS Data type boolean / string Description If set, the default JavaScript in the header will be removed. The default JavaScript is the decryption function for email addresses. **Special case:** If the value is "**external**", then the default JavaScript is written to a temporary file and included from that file. See "inlineStyle2TempFile" below. **Examples**:: config.removeDefaultJS = external config.removeDefaultJS = 1 Default external .. _setup-config-removepagecss: removePageCss """"""""""""" .. container:: table-row Property removePageCss Data type boolean Description Remove CSS generated by :ref:`\_CSS\_PAGE\_STYLE <setup-plugin-css-page-style>` configuration of extensions. (\_CSS\_PAGE\_STYLE renders certain styles not just because an extension is installed, but only in a special situation. E.g. some styles will be output, when a textpic element with an image positioned alongside the text is present on the current page.) .. _setup-config-rendercharset: renderCharset """"""""""""" .. container:: table-row Property renderCharset Data type string Description Charset used for the internal rendering of the page content. It is highly recommended that this value is the same as the charset of the content coming from the main data source (e.g. the database). Thus you don't need to do any other conversion. All strings from locallang files and locale strings are (and should be) converted to "renderCharset" during rendering. If you need another output charset than the render charset, see "metaCharset" above. TYPO3 internally always uses UTF-8 by default. **Note:** This property is deprecated since TYPO3 7! Use UTF-8 properly in your installation instead. Default utf-8 .. _setup-config-sendcacheheaders: sendCacheHeaders """""""""""""""" .. container:: table-row Property sendCacheHeaders Data type boolean Description If set, TYPO3 will output cache-control headers to the client based mainly on whether the page was cached internally. This feature allows client browsers and/or reverse proxies to take load off TYPO3 websites. The conditions for allowing client caching are: - page was cached - No \*\_INT or \*\_EXT objects were on the page (e.g. USER\_INT) - No frontend user is logged in - No backend user is logged in If these conditions are met, the headers sent are: - Last-Modified [SYS\_LASTCHANGED of page id] - Expires [expire time of page cache] - ETag [md5 of content] - Cache-Control: max-age: [seconds til expiretime] - Pragma: public In case caching is not allowed, these headers are sent to avoid client caching: - Cache-Control: private Notice that enabling the browser caches means you have to consider how log files are written. Because when a page is cached on the client it will not invoke a request to the webserver, thus not writing the request to the log. There should be ways to circumvent these problems but they are outside the domain of TYPO3 in any case. **Tip:** Enabling cache-control headers might confuse editors seeing old content served from the browser cache. "Shift-Reload" will bypass both browser- and reverse-proxy caches and even make TYPO3 regenerate the page. Teach them that trick! Thanks to Ole Tange, www.forbrug.dk for co-authoring this feature. .. _setup-config-sendcacheheaders-onlywhenlogindeniedinbranch: sendCacheHeaders\_onlyWhenLoginDeniedInBranch """"""""""""""""""""""""""""""""""""""""""""" .. container:: table-row Property sendCacheHeaders\_onlyWhenLoginDeniedInBranch Data type boolean Description If this is set, then cache-control headers allowing client caching is sent only if user-logins are disabled for the branch. This feature makes it easier to manage client caching on sites where you have a mixture of static pages and dynamic sections with user logins. The background problem is this: In TYPO3 the same URL can show different content depending on whether a user is logged in or not. If a user is logged in, cache-headers will never allow client caching. But if the same URL was visited without a login prior to the login (allowing caching) the user will still see the page from cache when logged in (and so thinks he is not logged in anyway)! The only general way to prevent this is to have a different URL for pages when users are logged in. Another way to solve the problem is using this option in combination with disabling and enabling logins in various sections of the site. In the page records ("Advanced" page types) you can disable frontend user logins for branches of the page tree. Since many sites only need the login in a certain branch of the page tree, disabling it in all other branches makes it much easier to use cache-headers in combination with logins; Cache-headers should simply be sent when logins are not allowed and never be send when logins are allowed! Then there will never be problems with logins and same-URLs. .. _setup-config-setjs-mouseover: setJS\_mouseOver """""""""""""""" .. container:: table-row Property setJS\_mouseOver Data type boolean Description If set, the over() and out() JavaScript functions are forced to be included .. _setup-config-setjs-openpic: setJS\_openPic """""""""""""" .. container:: table-row Property setJS\_openPic Data type boolean Description If set, the openPic JavaScript function is forced to be included .. _setup-config-spamprotectemailaddresses: spamProtectEmailAddresses """"""""""""""""""""""""" .. container:: table-row Property spamProtectEmailAddresses Data type "ascii" / -10 to 10 Description If set, then all email addresses in typolinks will be encrypted so spam bots cannot detect them. If you set this value to a number, then the encryption is simply an offset of character values. If you set this value to "-2" then all characters will have their ASCII value offset by "-2". To make this possible, a little JavaScript code is added to every generated web page! (It is recommended to set the value in the range from -5 to 1 since setting it to >= 2 means a "z" is converted to "\|" which is a special character in TYPO3 tables syntax – and that might confuse columns in tables. Now hardcoded range) Alternatively you can set this value to the keyword "ascii". This way every character of the "mailto:" address will be translated to a Unicode HTML notation. Have a look at the example to see how this works. **Example**: mailto:a@b.c will be converted to mailto:a@b.c The big advantage of this method is that it does not need any JavaScript! .. _setup-config-spamprotectemailaddresses-atsubst: spamProtectEmailAddresses\_atSubst """""""""""""""""""""""""""""""""" .. container:: table-row Property spamProtectEmailAddresses\_atSubst Data type string Description Substitute label for the at-sign (@). Default (at) .. _setup-config-spamprotectemailaddresses-lastdotsubst: spamProtectEmailAddresses\_lastDotSubst """"""""""""""""""""""""""""""""""""""" .. container:: table-row Property spamProtectEmailAddresses\_lastDotSubst Data type string Description Substitute label for the last dot in the email address. **Example**: (dot) Default . *(just a simple dot)* .. _setup-config-sword-nomixedcase: sword\_noMixedCase """""""""""""""""" .. container:: table-row Property sword\_noMixedCase Data type boolean Description Used by the parseFunc-substitution of search Words (sword): If set, the words MUST be the exact same case as the search word was. .. _setup-config-sword-standalone: sword\_standAlone """"""""""""""""" .. container:: table-row Property sword\_standAlone Data type boolean Description Used by the parseFunc-substitution of search Words (sword): If set, the words MUST be surrounded by whitespace in order to be marked up. .. _setup-config-sys-language-isocode: sys\_language\_isocode """""""""""""""""""""" .. container:: table-row Property sys\_language\_isocode Data type string Description ISO 639-1 language code for the according language. By default this is being set by :typoscript:`TSFE:sys_language_isocode`. The value is derived from the ISO code that is stored within the sys_language record. You can override the value, which was retrieved that way, with this setting. The ISO code is also used for the language attribute of the HTML tag. Therefore the setting config.htmlTag_langKey is not needed anymore, if it is the same as the ISO code. See the example at sys\_language\_isocode\_default! .. _setup-config-sys-language-isocode-default: sys\_language\_isocode\_default """"""""""""""""""""""""""""""" .. container:: table-row Property sys\_language\_isocode\_default Data type string Description ISO 639-1 language code for the default language (that is :typoscript:`sys_language_uid = 0`). **Example**:: # Danish by default config.sys_language_uid = 0 config.sys_language_isocode_default = da [globalVar = GP:L = 1] # ISO code is filled by the respective DB value from sys_language (uid 1) config.sys_language_uid = 1 # You can override this of course config.sys_language_isocode = fr [GLOBAL] Default en .. _setup-config-sys-language-mode: sys\_language\_mode """"""""""""""""""" .. container:: table-row Property sys\_language\_mode Data type string Description Setting various modes of handling localization. The syntax is "[keyword] ; [value]". Possible keywords are: [default] - The system will look for a translation of the page (from "Alternative Page Language" table) and if it is not found it will fall back to the default language and display that. **content\_fallback:** Recommended. The system will always operate with the selected language even if the page is not translated with a page overlay record. This will keep menus etc. translated. However, the *content* on the page can still fall back to another language, defined by the value of this keyword, e.g. "content\_fallback ; 1,0" to fall back to the content of sys\_language\_uid 1 and if that is not present either, to default (0). **strict:** The system will report an error if the requested translation does not exist. Basically this means that all pages with gray background in the Web > Info / Localization overview module will fail (they would otherwise fall back to default language in one way or another). **ignore:** The system will stay with the selected language even if the page is not translated and there's no content available in this language, so you can handle that situation on your own then. An in-depth discussion is found in the :ref:`Frontend Localization Guide <t3l10n:localization-modes>`. .. _setup-config-sys-language-overlay: sys\_language\_overlay """""""""""""""""""""" .. container:: table-row Property sys\_language\_overlay Data type boolean / keyword Description If set, records from certain tables selected by the CONTENT cObject using the "languageField" setting will select the default language (0) instead of any language set by sys\_language\_uid / sys\_language\_mode. In addition the system will look for a translation of the selected record and overlay configured fields. The requirements for this is that the table is configured with "languageField" and "transOrigPointerField" in the [ctrl] section of $GLOBALS['TCA']. Also, exclusion of certain fields can be done with the "l10n\_mode" directive in the field-configuration of $GLOBALS['TCA']. For backend administration this requires that you configure the "Web > Page" module to display content elements accordingly; That each default element is shown and next to it any translation found. This configuration can be done with Page TSconfig for a section of the website using the object path "mod.web\_layout.defLangBinding = 1". Keyword: **hideNonTranslated:** If this keyword is used a record that has no translation will not be shown. The default is that records with no translation will show up in the default language. .. _setup-config-sys-language-softexclude: sys\_language\_softExclude """""""""""""""""""""""""" .. container:: table-row Property sys\_language\_softExclude Data type string Description Setting additional "exclude" flags for l10n\_mode in TCA for frontend rendering. Works exactly like sys\_language\_softMergeIfNotBlank (see that for details - same Syntax!). Fields set in this property will override if the same field is set for "sys\_language\_softMergeIfNotBlank". .. _setup-config-sys-language-softmergeifnotblank: sys\_language\_softMergeIfNotBlank """""""""""""""""""""""""""""""""" .. container:: table-row Property sys\_language\_softMergeIfNotBlank Data type string Description Setting additional "mergeIfNotBlank" fields from TypoScript. Background: In TCA you can configure :ref:`"l10n_mode" property <t3tca:columns-properties-l10n-mode>` (localization mode) - for each field. Two of the options affect how the frontend displays content (the values "exclude" and "mergeIfNotBlank"). The first ("exclude") means that the value from the translated record will not be overlaid the value from the record in the default language. The second ("mergeIfNotBlank") means that it will be overlaid *only* if it has a non-blank value. Since it might be practical to set up fields for "mergeIfNotBlank" on a per-site basis this option allows you to override additional fields from tables. **Syntax:** [table]:[field], [table]:[field], [table]:[field], ... **Example**:: config.sys_language_softMergeIfNotBlank = tt_content:image , tt_content:header This setting means that the header and image field of content elements will be used from the translation only if they had a non-blank value. For the image field this might be very practical because it means that the image(s) from the default translation will be used unless other images are inserted! See also the :ref:`Frontend Localization Guide <t3l10n:localized-content-fine-tune-overlays>`. .. _setup-config-sys-language-uid: sys\_language\_uid """""""""""""""""" .. container:: table-row Property sys\_language\_uid Data type integer Description This value points to the uid of a record from the "sys\_language" table and if set, this means that various parts of the frontend display code will select records which are assigned to this language. See ->SELECT Internally, the value is depending on whether an Alternative Page Language record can be found with that language. If not, the value will default to zero (default language) except if "sys\_language\_mode" is set to a value like "content\_fallback". .. _setup-config-titletagfunction: titleTagFunction """""""""""""""" .. container:: table-row Property titleTagFunction Data type function name Description Passes the default <title> tag content to this function. No TypoScript parameters are passed though. .. _setup-config-tx-extension-key-with-no-underscores: tx\_[extension key with no underscores]\_[\*] """"""""""""""""""""""""""""""""""""""""""""" .. container:: table-row Property tx\_[extension key with no underscores]\_[\*] Data type - Description Configuration space for extensions. This can be used – for example – by plugins that need some TypoScript configuration, but that don't actually display anything in the frontend (i.e. don't receive their configuration as an argument from the frontend rendering process). **Example**:: config.tx_realurl_enable = 1 .. _setup-config-typolinkcheckrootline: typolinkCheckRootline """"""""""""""""""""" .. container:: table-row Property typolinkCheckRootline Data type boolean Description If set, then every "typolink" is checked whether it's linking to a page within the current rootline of the site. If not, then TYPO3 searches for the first found domain record (without redirect) in that rootline from out to in. If found (another domain), then that domain is prepended the link, the external target is used instead and thus the link jumps to the page in the correct domain. .. _setup-config-typolinkenablelinksacrossdomains: typolinkEnableLinksAcrossDomains """""""""""""""""""""""""""""""" .. container:: table-row Property typolinkEnableLinksAcrossDomains Data type boolean Description This option enables to create links across domains using current domain's linking scheme. If this option is not set, then all cross-domain links will be generated as :samp:`https://example.com/index.php?id=12345` (where 12345 is page id). Setting this option requires that domains, where pages are linked, have the same configuration for: \- linking scheme (i.e. all use RealURL or CoolURI but not any mixture) \- all domains have identical localization settings (config.sys\_language\_XXX directives) \- all domains have the same set of languages defined This option implies "config.typolinkCheckRootline=1", which will be activated automatically. Setting value of "config. typolinkCheckRootline" inside TS template will have no effect. Disclaimer: it must be understood that while link is generated to another domain, it is still generated in the context of current domain. No side effects are known at the time of writing of this documentation but they may exist. If any side effects are found, this documentation will be updated to include them. Default 0 .. _setup-config-typolinklinkaccessrestrictedpages: typolinkLinkAccessRestrictedPages """"""""""""""""""""""""""""""""" .. container:: table-row Property typolinkLinkAccessRestrictedPages Data type integer (page id) / keyword "NONE" Description If set, typolinks pointing to access restricted pages will still link to the page even though the page cannot be accessed. If the value of this setting is an integer it will be interpreted as a page id to which the link will be directed. If the value is "NONE" the original link to the page will be kept although it will generate a page-not-found situation (which can of course be picked up properly by the page-not-found handler and present a nice login form). See "showAccessRestrictedPages" for menu objects as well (similar feature for menus) **Example**:: config.typolinkLinkAccessRestrictedPages = 29 config.typolinkLinkAccessRestrictedPages_addParams = &return_url=###RETURN_URL###&pageId=###PAGE_ID### Will create a link to page with id 29 and add GET parameters where the return URL and original page id is a part of it. .. _setup-config-typolinklinkaccessrestrictedpages-addparams: typolinkLinkAccessRestrictedPages\_addParams """""""""""""""""""""""""""""""""""""""""""" .. container:: table-row Property typolinkLinkAccessRestrictedPages\_addParams Data type string Description See "typolinkLinkAccessRestrictedPages" above .. _setup-config-username-substtoken: USERNAME\_substToken """""""""""""""""""" .. container:: table-row Property USERNAME\_substToken Data type string Description The is the token used on the page, which should be substituted with the current username IF a front-end user is logged in! If no login, the substitution will not happen. Default  .. _setup-config-useruid-substtoken: USERUID\_substToken """"""""""""""""""" .. container:: table-row Property USERUID\_substToken Data type string Description The is the token used on the page, which should be substituted with the current users UID IF a front-end user is logged in! If no login, the substitution will not happen. This value has no default value and only if you specify a value for this token will a substitution process take place. .. _setup-config-xhtmldoctype: xhtmlDoctype """""""""""" .. container:: table-row Property xhtmlDoctype Data type string Description Sets the document type for the XHTML version of the generated page. If config.doctype is set to a string then config.xhtmlDoctype must be set to one of these keywords: **xhtml\_trans** for XHTML 1.0 Transitional doctype. **xhtml\_frames** for XHTML 1.0 Frameset doctype. **xhtml\_strict** for XHTML 1.0 Strict doctype. **xhtml\_basic** for XHTML basic doctype. **xhtml\_11** for XHTML 1.1 doctype. This is an example to use MathML 2.0 in an XHTML 1.1 document:: config.doctype ( <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0//EN" "http://www.w3.org/Math/DTD/mathml2/xhtml-math11-f.dtd"> ) config.xhtmlDoctype = xhtml_11 Default *(same as config.doctype if set to a keyword)* .. _setup-config-xmlprologue: xmlprologue """"""""""" .. container:: table-row Property xmlprologue Data type string Description If empty (not set) then the default XML 1.0 prologue is set, when the doctype is set to a known keyword (e.g. xhtml\_11):: <?xml version="1.0" encoding="[config.renderCharset]"> If set to one of the following keywords then a standard prologue will be set: **xml\_10:** XML 1.0 prologue (see above) **xml\_11:** XML 1.1 prologue **none:** The default XML prologue is *not* set. Any other string is used as the XML prologue itself. .. ###### END~OF~TABLE ######

LOGIN .. _setup-config-beloginlinkiplist-logout: beLoginLinkIPList\_logout """"""""""""""""""""""""" .. container:: table-row Property beLoginLinkIPList\_logout Data type HTML Description HTML code wrapped with the logout link, see above .. _setup-config-cache: cache """"" .. container:: table-row Property cache Data type array Description Determine the maximum cache lifetime of a page. The maximum cache lifetime of a page can not only be determined by the start and stop times of content elements on the page itself, but also by arbitrary records on any other page. However, the page has to be configured so that TYPO3 knows the start and stop times of which records to include. Otherwise, the cache entry will be used although a start/stop date already passed by. To include records of type on page into the cache lifetime calculation of page , add the following TypoScript: config.cache. =

Displaying workspace named "%s" (number %s)!

config.message_preview_workspace =

Displaying workspace number %2$s named "%1$s"!