EXT: Config, Metatag & SEO Features¶

Description

This enables some new subcategories in the constant editor used by the extension template of this extension. Technically this is managed by xclassing the 'class.t3lib_tsparser_ext' class. This is just a cosmetical feature so you can read subcategories like: 'Speaking URL Management' , 'Administrative settings', or 'Administrative settings' in the constant editor.

Description

Applying this patch will replace a function in the 'class.tslib_menu', which then adds a feature which is only available with Typo3 v4.3. This feature is the 'reverseOrder' property for the rootline hmenu. This featue is used for the reverse-rootline in the title-tag generator. With the release of typo3 4.3 this patch will become obsolete und should not be used anymore as the new version of tslib_menu might have some more features incorporated at that point.

Description

With this setting turned on, you globaly disallow the use of the no_cache parameter. This means, even if a pages setting says to not cache the page or a config.no_cache=1 is somewhere in the setup, this will be disobeyed and the page cache will only be cleared when the regular cache timeout is due or you explicitly clear the cache.

Description

If this setting is checked, all pages with no translation won't show up in the menu if the language setting is not L=0 (which would be the default language). Hiding untranslated pages is neccessary if you use the config option 'sys_language_mode = strict' which would result in a 404 if a page isn't translated yet. and 'sys_language_mode = fallback' is no good idea at all, because of the double content which would be created if the language overlay sends out the untranslated content when calling the page in a language which is not the default (L=0). Changing this setting eventually changes the behaviour the a setting under Web->Page->Page properties->Localization settings-> from 'Hide page if no translation for current language exists' to 'Show page even if no translation exists'. That in mind you should check this setting on pages where you manually changed them earlier, because they will behave exactly oposite.

Description

comma separated list of sitemaps to create (realurl needs to be enabled [cooluri config will follow soon]). see manual for sitemap integration and configuration reference. valid values would be 'sitemap.xml:1234,anothersitemap.xml:2345,...' where the item in front of the colon is the name and behind is the typeNum which you can refer to in your setup. if this field is not empty, also a realurl config will be added. see manual for avoiding possible pitfalls.

Description

you can choose to hide the fields [Author, Email, Abstract, Keywords, Description] in the [metatags] section of the pages module. these are STANDARD fields of Typo3 and might be used with this extension. NOTE: disabling this option only hides the field, the underlying data is left unaffected and will be displayed if configured.

Description

you can choose to hide the fields [Alttitle, Geotags, Copyright, Publisher, Robots, Importance] in the [metatags] section of the pages module. these are NEW fields that come with this extension. NOTE: disabling this option only hides the field, the underlying data is left unaffected and will be displayed if configured.

The Robots field might also be used for excluding different pages from appearing in the sitemap. The importance field is only used in conjunction with the sitemap feature.

Description

This enables the post processor for processing the generated (x)html content. The post processing will only apply to the typeNum = 0 page object, so no other pagetypes will be affected. It does various things and apart from some features which depend on each other you can switch them on and of in a way which works for your specific setup. It is highly recommended to test the features thoroughly in your environment to decide if the result is ok on all kind of pages on your site.

Description

This switches on the Unicode flag in the case you are using UTF-8 content and only get a white page as result. As there are some replacements done by regex, some might terribly fail if supplied with unicode strings and not havnig the 'u' flag set. This setting takes care of that. Should left unchecked for non-unicode content, though.

Description

Postprocessing: Enabling this will remove ALL html comments apart from those nested in <script> or <style> tags. At this stage of development, also the indexed search comments will be removed, so this is to be used with precaution. This option is simply implemented for obfuscation hence security considerations in mind.

Description

Postprocessing: If you enable one of these options: [remove ALL html comments] or [sort headertags], the typo3 copyright notice ('... This website is brought to you by TYPO3 …') injected as html comment within the <head> tag will get removed by this process. This option turned on enables the reinjection of this copyright notice. It is strictly spoken legally not necessary to leave this comment in the output produced by typo3 but it is highly encouradged to leave this option enabled anyway. it is a friendly turn to place this notice within the header and it is a confession, too. if you leave this option enabled, the comment will get reinjected in any case.

Description

Postprocessing: If some extension produces additional comment tags inside cdata markings like so: '/*<![CDATA[*/ <!-- .... // --> /*]]>*/' the '<!--' and '// -->' part will get removed if this option is selected. The point is if they remain within style tags, the gecko engine is moaning about invalid selectors which is actually not an error but an avoidable warning. the flipside would be that if you turn this feature on, really very old browser might display the content of inline script and style tags, because they're not able to interprete these. if you have concerns about this or you don't encounter these sort of cdata + htmlcomment in your code, you might simply leave this feature unselected. this feature is only active if the 'remove all html comments' feature is also activated, anyway.

Description

Postprocessing: This option removes all empty lines which are lines with whitespace (space char, tab, or linefeed) only as content.

Description

Postprocessing: This option removes the surrounding whitespace on each line (tabs & spaces)

Description

Postprocessing: Enabling this option turns on the sorting of the tags inside the <head> section of the output. Technically this means that all tags in the head will be rearranged in order of appearance following this priority scheme 'base > title > meta > link > style > script', which leads to the result that the base tag (if any) appears on top, followed by the title, then all meta tags in their original order will be stacked below and so forth. You should though keep in mind that at this stage of developement everything else residing within the <head> tag will be removed.

Description

Postprocessing: If this feature is enabled, then all blank lines and surrounding whitespace will be removed first to apply a simple but nice indentation to the whole content. It even indents inline script and style content (if selected below). Content in between <textarea> tags will be omitted from the indentation, though.

Description

Postprocessing: This is an additional indentation feature. If enabled, the indenter will also indent script and css content like curly braces inline code { }.

Description

Postprocessing: The indenter will use this character(set) to indent. It's either a tab, or 2, 4 or 6 spaces.

Description

If you've got other pages configured whose content you want to push through the postprocessor insert the respective pageTyp values as a coma separated list, eg.: 700,3005 (this means: pages with pageTyp=700 or pageTyp=3005 would get postprocessed, too)

Description

This writes the <base> tag in the header of the document. Set this to the value that is expected to be the URL, and append a '/' to the end of the string. This value goes to config.baseURL and config.absRefPrefix.

Description

The config.doktype value. If set, then a document type declaration (without an XML prologue!) will be generated

Description

This is the charset used for internal rendering and output (config.renderCharset, config.metaCharset). default is utf-8. you should use utf-8 as database and collation charset and $TYPO3_CONF_VARS[BE][forceCharset] = utf-8 or chamge the setting here to whatever charset you are using.

Description

HTTP_GET_VARS, which should be passed on with links in TYPO3. this should be set to L in a multilanguage environment. Affected value: config.linkVars.

Description

This setting determins the reading direction which, if set to 'none', in most countries defaults to 'ltr' anyway. This is useful only if you use a language with an rtl direction.

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 (eg. "-2" -> all chars will have their ASCII value offset by "-2"). To make this possible, a little JavaScript code is added to every generated web page. 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 and no additional JS code is needed.

The '@' Subst and 'Last Dot' Subst parameters are as they suggest a replacement character to substitute these two characters to even more obfuscate email addresses on the webpage.

Description

If set, the default JavaScript in the header will be removed. The default JavaScript is the blurLink function and browser detection variables. Special case: if the value is "external" then the default JavaScript is written to a temporary file and included from that file.

You should change that option to 'leave in document' or 'external' if you use 'Spam Protect eMail' with a numeric value, because the defaultJS is used for the email decryption script in that case.

Description

If set, the inline styles TYPO3 controls in the core are written to a file, typo3temp/stylesheet_[hashstring].css, and the header will only contain the link to the stylesheet.

Description

Turns Simulate Static Documents on/off. This is the Typo3 builtin url beautyfication method. Should be explicitly turned off, if you use realurl or cooluri.

Description

If not zero, TYPO3 generates urls with the title in. select the number of chars the title is limited to.

Description

Turns RealURL on/off. If you use this, make sure, 'simulateStaticDocuments' is turned to off, because they would interfere with each other.

Description

Turns CoolURI on/off. Turns RealURL on/off. If you use this, make sure, 'simulateStaticDocuments' is turned to off, because they would interfere with each other.

Description

show/hide the admin panel on the frontend

Description

Switches the template cache off (for developement purposes). on production systems the setting should always be 'FE cache ON').

Description

With this setting the cache always expires at midnight of the day, the page is scheduled to expire.

Description

As its not the most useful thing and turned on if not set, you can gain a little performance if you switch it off here.

Description

These are the modes how typo3 deals with language overlays, especially with untranslated content. [default] if a translation of the page is not found a fall back to the default language will be displayed. [strict] an error will be reported if the requested translation does not exist. [content_fallback] the selected language will always be displayed even if the page is not translated (this will keep menus etc. translated). the content on the page can still fall back to another language, defined by the value of the 'Content Fallback Options'

Description

If the Language Mode is set to 'content_fallback', this coma separated lists of language id's determines the languages to search for fallback content. translated content is searched for within these languages if there's no content with the requested language available. eg.: assuming '1,0' as fallback options here... request for L=2 - no translated content available, system looks for L=1. if there's also no content then system looks for L=0 which is the default language.

Description

this is the language for L=0 the default language, and the value for the attributes "xml:lang" and "lang" in the <html> tag.

Description

this is the LC_ALL setting for L=0 the default language

Description

the following are the settings for language L=[UID], where UID is the value you choose. If you choose 'none' then this section is simply inactive.

The same as for the Default settings goes for the respective '2nd', '3rd' and '4th' values

Description

If set to 1, the content of the extra 'title' field in the page settings (if filled) or alternatively the 'subtitle' will be the first item in the title string, like: 'this is a special title << your :: page :: root ...'. If set to 0, no extra page title or subtitle will be prepended.

Description

This is the string used to divide the extra/subtitle from the rootline. by default it's '<<' which results in 'subtitle << level3 :: level2 ... '. the dividerstring will only be displayed if there's content for the field available.

Description

If set to 1, a reverse rootline will be generated, listing the pages from the curent level (which is the actual page 'title') down to the root from left to right, which is a more convenient way to read than the usual bottom to top style. If set to 0, only the current level i.e. the current page title will be rendere here.

Description

This is the string used to divide the rootline levels. by default it's '::' which results in ' level3 :: level2 :: level1 '.

Description

If set to 1, the sitename will be appended like so: ' :: yoursitename', 0 turns this off.

Description

This is the string which will be prepended to the sitetitle (if applied). by default it's '::' which results in '... :: yoursitename'.

Description

This is the default content of the 'author' metatag which will be displayed sitewide if filled in here. can be overridden by each pages 'author' tag

Description

This is the default content of the 'email' metatag which will be displayed sitewide if filled in here. can be overridden by each pages 'email' tag.

Description

This is the content of the sitewide 'copyright' metatag. It will be displayed sitewide if filled in here.

Description

This is the content of the sitewide 'publisher' metatag. It will be displayed sitewide if filled in here.

Description

You can choose the content of the 'distribution' metatag, which will be displayed if you select a value out of: global (valid for all), local (valid only local or regional), Internal Use (IU = valid for Internal Use only), blank - no tag is generated

Description

This is the default content of the 'robots' metatag which will be displayed sitewide if filled in here. can be overridden by checkboxes in the pages 'meta' section. Leave empty if you want no default 'robots' tag.

Description

If display date is selected, then the date metatag will be rendered with the last modified date or, if not available, the page creation date.

Description

If you've got a google verify-v1 tag, this is the place to enter the hash eg.:PCiRPCiR4tHR4ss4jTZd8E4jDjEJd39dDhE80iiE= .

Description

This is the global setting for creating a GEO.POSITION and ICBM metatag if any value is enterd here (page specific values do overrie this global setting, though). enter your position in the form 'latitude%SEMICOLON%longtitude' (see: http://mygeoposition.com/?lang=de)

Description

This is the global setting for creating a GEO.REGION metatag if any value is enterd here (page specific values do overrie this global setting, though). enter your region code like 'DE-NW' here. described in ISO_3166-2 (see: http://de.wikipedia.org/wiki/ISO_3166-2).

Description

This is the global setting for creating a GEO.PLACENAME metatag if any value is enterd here (page specific values do overrie this global setting, though). enter your placename like your city or region or whatever, it's free text : 'Köln, Nordrhein-Westfalen'.

Description

This is the global setting for creating the respective COUNTRY, STATE, CITY, ZIP metatag if any value is enterd in any of the corresponding fields.

Description

You can prevent the each of these metatag to appear within your head section, even if filled (and maybee used for other purposes) if you disable them here. All but KEYWORDS and DESCRIPTION are disabled by default.

Description

If [show date] is selected, then the DATE metatag will be rendered with the last modified date or - if not available - the page creation date. You can also choose to not display a DATE metatag, which is the default.

Description

if this option is enabled, the DESCRIPTION metatag field (if displayed on the webpage) will be filled with the contents of the ABSTRACT field from the page module (if the corresponding DESCRIPTION field is empty). this applies ONLY if the ABSTRACT metatag is NOT displayed on the webpage!