Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Documentation changes in 4.3

From TYPO3Wiki
Jump to: navigation, search
This page belongs to the Core Team (category Core Team)

notice - Note

What you find on this page is what we changed in the official documents. It does not make sense to correct any mistakes here - if you found one, please use the according bug trackers instead to inform us! Thank you!

Contents

TSref (doc_core_tsref)

20930: TYPO3 Core - Give CONTENT.table stdWrap properties [Closed; assigned to Benni Mack]

Benjamin Mack, on behalf of Sebastian Gebhard, 25.09.2009:

Object type CONTENT, property table

  • Changed Datatype: tableName / stdWrap
  • Description: To enhance flexibility of CONTENT the table property was given stdWrap properties

18535: TYPO3 Core - support html-tags in crop function of stdWrap [Closed; assigned to Dmitry Dulepov]

Jochen Rau, 2009-09-01

in [tsref:->stdWrap] add (below "crop"):

  • property: cropHTML
  • type: -
  • description: Crops the content to a certain length. I contrast to stdWrap.crop it respects HTML tags.

It does not crop inside tags and closes open tags. Entities (like ">") are counted as one char. See stdWrap.crop for a syntax description and examples.

  • default: -

20565: TYPO3 Core - Add an opacity option to the GIFBUILDER BOX object [Closed; assigned to Ingo Renner]

Ingo Renner, 2009-07-20

[tsref:->GIFBUILDER.(GBObj).BOX] Property table add

  • property: "opacity"
  • type: posint (1-100)
  • description: Opacity (i.e. inverse of transparency, e.g. 100% opacity = 0% transparency)
  • default: 100

Missing emptyTitleHandling property

Yannick Pavard, 2009-05-08

emptyTitleHandling property was missing for object type IMAGE, FILE and IMGTEXT, as well as function filelink. The sentence "If no titltext is specified, it will use the alttext instead" was removed from the titleText property description.

Note: looking at source code revisions, this feature seems to have been available since TYPO3 4.0

Improve FORM example

Sonja Scholz, 2009-03-19

Change in TSref [tsref:(cObject).FORM]

  • Add to example mailform:
| from_name=hidden | Website XY 
| from_email=hidden | noreply@website.com
| organisation=hidden | Organisation XY
| redirect=hidden | 16
| priority=hidden | 5
  • Replace these example rows:
Name: | *the name = input | Enter your name here
Email: | *email=input | 

with this:

Name: | *replyto_name=input | Enter your name here
Email: | *replyto_email=input
  • Add the following explanations for the example rows:
    • "from_name": With this option you can set the mail header from name, which will be shown in the mail software.
    • "from_email": With this option you can set the mail header from email, which will be shown in the mail software as sender address.
    • "organisation": With this option you can set the mail header organisation param, which won't be shown in the mail but in the mail header.
    • "redirect": With this option you can define a TYPO3 page (page id) or external URL (www.example.com) as redirect url after submit. If this option isn't set the form will be shown again.
    • "priority": With this option you can set the priority of the mail from 1(not important) to 5(very important). Default is 3.
    • "replyto_name": If the field is named like this the value is used as reply to name in the email software and will not be shown in the mail content. Choose another field name like the_name to use the value as a normal field.
    • "replyto_email": If the field is named like this the value is used as reply to email address in the email software and will not be shown in the mail content. To get the value as sender address in the mail software use "email" as field name.

18416: TYPO3 Core - cObj CONTENT should be allowed with static_* tables [Closed; assigned to Martin Kutschker]

Georg Ringer, 2008-03-10

Change in TSref [tsref:Content Objects (cObject)/->CONTENT] Property table

  • NOTE: Only tables allowed are "pages" or tables prefixed with one of these: "tt_", "tx_", "ttx_", "fe_", "user_"

to

  • NOTE: The only tables allowed are "pages" or tables prefixed with one of these: "tt_", "tx_", "ttx_", "fe_", "user_" or "static_"

17788: TYPO3 Core - Enable stdWrap for the image in imageLinkWrap [Closed; assigned to Martin Kutschker]

Georg Ringer, 2007-11-14

TSref [tsref:(functions).imageLinkWrap]

  • Property: stdWrap
  • Data type: stdWrap
  • Description: Enable stdWrap for the image

17681: TYPO3 Core - wrapItemAndSub for GMENU [Closed; assigned to Ernesto Baschny]

Ernesto Baschny, 2008-10-01

TSref [tsref:(cObject).HMENU.(mObj).GMENU.(itemState)]

  • Property: wrapItemAndSub
  • Data type: wrap /+stdWrap
  • Description: Wraps the whole item and any submenu concatenated to it.

19685: TYPO3 Core - Enable stdWrap for expAll [Closed; assigned to Steffen Kamper]

Steffen Kamper

TSref, TMENU

  • Property: expAll
  • Data type: boolean / stdWrap

17742: TYPO3 Core - config.fileTarget for default link target on files [Closed; assigned to Jeff Segars]

François Suter, on behalf of Ralf Hettinger, 2008-10-31

TSref [tsref:config/->CONFIG]

Add after extTarget:

  • Property: fileTarget
  • Data type: target
  • Description: default file link target. Used by typolink if no fileTarget is set.

[tsref:->typolink]

Add after extTarget:

  • Property: fileTarget
  • Data type: target/stdWrap
  • Description: target used for file links

17747: TYPO3 Core - Integrate possibility to reverse order of rootline HMENU [Closed; assigned to Oliver Hader]

Oliver Hader, on behalf of Ralf Hettinger, 2008-11-01

TSref [tsref:(cObject).HMENU.special]

  • Property: reverseOrder
  • Data type: boolean
  • Description: If set to true, the order of the rootline menu elements will be reversed.
  • Default: false

19515: TYPO3 Core - Extend condition operators for globalVar [Closed; assigned to Oliver Hader]

Steffen Kamper

TSref Conditions, globalVars:

  • Change section header from "globalVars:" to "globalVar:"
  • Syntax: - replace with:
[globalVar = var = value1, > value2, < value3, <= value4 , >= value5, != value6, ...]
  • Comparison: - replace table data with:
Operator: Function:
=         Requires exact match       
>         The var must be greater than the value
<         The var must be less than the value
<=        The var must be less or equal than the value
>=        The var mast be greater or equal than the value
!=        The var must be not equal to the value
  • Add new examples below the table:
This will match, if the page-id is higher than or equal to 10:
[globalVar = TSFE:id >= 10] 

This will match, if the page-id is not equal to 316:
[globalVar = TSFE:id != 316] 

This will match the not-existing GP style:
[globalVar = GP:style = ]

17407: TYPO3 Core - get rid of clear.gif with space [Closed; assigned to Thorsten Kahler]

Oliver Hader, on behalf of Susanne Moog, 2008-12-20

TSref [tsref:(functions).stdWrap]

For property "space" change data type to "space / stdWrap"

16665: TYPO3 Core - Enable stdWrap for HMENU.alwaysActivePIDlist [Closed; assigned to Oliver Hader]

Oliver Hader, 2009-01-08

TSref, Content Objects (cObject), HMENU:

For property "alwaysActivePIDlist" change data type to "list of integers / stdWrap"

19973: TYPO3 Core - Add gp as an alternative to gpvar in TS getText for a more consistent naming scheme [Closed; assigned to Ingo Renner]

Steffen Müller, 2009-02-06

TSref, Conditions, globalString:

  • Example:

Change from (old): Caring about this means that you would get values like HTTP_HOST by getenv(), you would retrieve GET/POST values with t3lib_div::GPvar().

Change to (new): Caring about this means that you would get values like HTTP_HOST by getenv(), you would retrieve GET/POST values with t3lib_div::_GP().


TSref, Data types, getText:

Data-type: getText

  • Example:

Change from (old): get input value from query string, (&stuff=) = GPvar : stuff get input value from query string, (&stuff[key]=) = GPvar : stuff | key

Change to (new): get input value from query string, (&stuff=) (use this instead of GPvar) = GP : stuff get input value from query string, (&stuff[key]=) (use this instead of GPvar) = GP : stuff | key


  • Comment:

Change from (old): global : [GLOBAL-var, split with | if you want to get from an array! DEPRECATED, use GPvar, TSFE or getenv]

GPvar: Value from GET or POST method. Use this instead of global

Change to (new): global: [GLOBAL-var, split with | if you want to get from an array! DEPRECATED, use GP, TSFE or getenv] GP: Value from GET or POST method. Use this instead of global

GPvar: usage of “GPvar” is deprecated. Use “GP” instead

19748: TYPO3 Core - ImageMagick generates larger than necessary files [Closed; assigned to Steffen Kamper]

Steffen Kamper, 2009-03-27,

TSref, functions, imgResource

  • Property: stripProfile
  • Data type: Boolean
  • Description: If set, IM-comand will use a stripProfile-command which shrinks the generated thumbs. See install tool for options and details.

If im_useStripProfileByDefault is set in the install tool, you can deactivate it by setting stripProfile=0

  • Example:
10 = IMAGE
10.file = fileadmin/images/image1.jpg
10.file.stripProfile = 1

20207: TYPO3 Core - Integrate possibility to determine maximum of multiple values in GIFBUILDER [Closed; assigned to Oliver Hader]

Oliver Hader, 2009-04-16,

TSref: GIFBUILDER, section "NOTE (+calc)"

Add after first paragraph and before example starts:

On using the special function max(), the maximum of multiple values can be determined. Example: XY: [10.w]+[20.w], max([10.h], [20.h])

20164: TYPO3 Core - Integrate automatic line breaks in GIFBUILDER [Closed; assigned to Oliver Hader]

Oliver Hader, 2009-05-03,

TSref: GIFBUILDER, section "NOTE (+calc)"

Add to first paragraph:

The property "lineHeight" (e.g. "[10.lineHeight]") uses the height a single line of text would take.

TSref: GIFBUILDER, [tsref:->GIFBUILDER.(GBObj).TEXT]:

Add new properties after "text":

  • Property: breakWidth
  • Data type: integer
  • Description: Defines the maximum width for an object, overlapping elements will force an automatic line break.
  • Property: breakSpace
  • Data type: float
  • Description: Defines a value that is multiplied by the line height of
  • the current element.
  • Default: 1.0

20533: TYPO3 Core - stdwrap to override image of imageLinkWrap [Closed; assigned to Christian Kuhn]

Georg Ringer, 2009-05-31

TSref [tsref:(functions).imageLinkWrap]

add somewhere in the beginning the new option file

  • Property: file
  • Data type: stdWrap
  • Description: Override the path of the image which is displayed

19754: TYPO3 Core - define Default GET-vars [Closed; assigned to Steffen Kamper] define Default GET-vars

Steffen

TSref, CONFIG

  • Property: defaultGetVars
  • Data type: array
  • Description:

Allows to set default values for GET parameters. Default value is taken only if the GET parameter isn't defined. Array notation is done with dots, eg: test[var1] will be written as text.var1

  • Example:
config.defaultgetVars {
    test.var1.var2.p3 = 15
    L = 3
}

20661: TYPO3 Core - [Feature] Add class for render HTML header/footer for BE and FE [Closed; assigned to Steffen Kamper]

Steffen Kamper

Documentation of t3lib_pageRenderer-related options

TSref, CONFIG

  • Key: moveJsFromHeaderToFooter
  • Type: boolean
  • Description: If set, all Javascript (includes and inline) will be moved to footer of page, which is after content and before the closing body tag
  • Key: pageRendererTemplateFile
  • Type: String
  • Description: Sets the template for page renderer class (t3lib_PageRenderer).
  • Example:
pageRendererTemplateFile = fileadmin/test_pagerender.html

TSref, PAGE

  • includeCSS, add following to description:

.allWrap - wraps the complete tag, useful for conditional comments. Example:

includeCSS.ie6Style = fileadmin/css/style3.css
includeCSS.ie6Style.allWrap = <!--[if lte IE 7]>|<![endif]-->

.external - If set, there is no file check. Use it for inclusion of external files. Example:

includeCSS.cooliris = http://www.cooliris.com/shared/resources/css/global.css
includeCSS.cooliris.external = 1

includeJS, add following to description: .compressed - boolean flag. This will be used by external compressors to see if the file is already compressed. .forceOnTop - boolean flag. If set, this file will be added on top of the files. .allWrap - wraps the complete tag, useful for conditional comments. .external - If set, there is no file check. Use it for inclusion of external files.

inlineJS: marked as deprecated. Use jsInline instead.

New properties for CSS (TSref, PAGE)

  • Key: cssInline
  • Type: ->CARRAY
  • Description: Use cObjects for creating inline CSS
  • Example:
page.cssInline {
    10 = TEXT
    10.value = h1 {margin:15px;}
    
    20 = TEXT
    20.value = h1 span{color: blue;}
}

New properties for JavaScript (TSref, PAGE)

Note: a new sub-section was introduced for all properties related to JavaScript

  • Key: includeJSFooter.[array]
  • Type: resource
  • Description: Same as includeJS above, except that this block gets included at the bottom of the page (just before the closing body tag).
  • Key: jsInline
  • Type: ->CARRAY
  • Description: Use cObjects for creating inline JavaScript
  • Example:
page.jsInline {
	10 = TEXT
	10.dataWrap = var pageId = {TSFE:id};	
}
  • Key: jsFooterInline
  • Type: ->CARRAY
  • Description: Same jsInline above, except that the JavaScript gets inserted at the bottom of the page (just before the closing body tag).
  • Key: includeJSlibs.[array]
  • Type: resource
  • Description:

Adds JS library files to head of page.

The file definition must be a valid "resource" datatype, otherwise nothing is inserted. This means that remote files cannot be referenced (i.e. using “http://...”), except by using the “.external” property.

Each file has optional properties: .allWrap - wraps the complete tag, useful for conditional comments. .external - If set, there is no file existence check. Useful for inclusion of external files.

  • Example:
page.includeJSlibs.twitter = http://twitter.com/javascripts/blogger.js
page.includeJSlibs.twitter.external = 1
  • Key: includeJSFooterlibs.[array]
  • Type: resource
  • Description: Same as includeJSlibs above, except that this block gets included at the bottom of the page (just before the closing body tag).
  • Key: javascriptLibs
  • Type: array of strings
  • Description: This allows to include the JavaScript libraries that are shipped with the TYPO3 Core.
javascriptLibs {
     # include prototype
   Prototype = 1

     # include Scriptaculous
   Scriptaculous = 1
     # adds modules dragdrop and controls to Scriptaculous
   Scriptaculous.modules = dragdrop,controls

     # include ExtCore
   ExtCore = 1
     # include ExtCore debug file (uncompressed)
   ExtCore.debug = 1

     # includes ExtJS
   ExtJs = 1
     # include ext-all.css
   ExtJs.css = 1
     # include default theme
   ExtJs.theme = 1
    # load specific adapter (jquery|prototype|yui)
   ExtJs.adapter = …
     # initialize QuickTips
   ExtJs.quickTips = 1
     # includes ExtJS debug file (uncompressed)
   ExtJs.debug = 1
}
  • Key: inlineLanguageLabel
  • Type: array of strings
  • Description: ExtJS specific, adds language labels to the page.
  • Example:
page.inlineLanguageLabel {
  label1 = 123
  label2 = 456
}

will produce following source:

TYPO3.lang = {"label1":"123","label2":"456"};
  • Key: inlineSettings
  • Type: array of strings
  • Description: ExtJS specific, adds settings to the page.
  • Example:
page.inlineSettings {
  setting1 = Hello
  setting2 = GoOnTop
}

will produce following source:

TYPO3.settings = {"TS":{"setting1":"Hello","setting2":"GoOnTop"}};
  • Key: extOnReady
  • Type: ->CARRAY
  • Description: add inline javascript, wrapped in Ext.onRTeady.
  • Example:
page.extOnReady {
  10 = TEXT
  10.value = Ext.Msg.alert("Typoscript Message","Hello World!");
}

will produce following source:

Ext.onReady(function() {Ext.Msg.alert("Typoscript Message","Hello World!"); });

Other new properties (TSref, PAGE)

  • Key: footerData
  • Type: ->CARRAY
  • Description: Same as headerData above, except that this block gets included at the bottom of the page (just before the closing body tag).

TSconfig (doc_core_tsconfig)

17299: TYPO3 Core - Enable/integrate conditions in Page TSconfig [Closed; assigned to Oliver Hader]

As of TYPO3 4.3 it is possible to use TypoScript conditions in both User TSconfig and Page TSconfig, just as it is done in TypoScript for templates.

Example:

[treeLevel = 1]
TCEFORM.tt_content.section_frame.disabled = 1
[GLOBAL]

The above TSconfig will hide the “section_frame” field of content elements only on first level of the page tree.

Differences

There are some slight differences between conditions in TSconfig and conditions in template TypoScript, which must be taken into account:

  • Conditions “usergroup” and “loginUser” apply to BE groups and BE users – respectively – and not to FE groups and users, quite obviously.
  • In the “globalString” condition, key “TSFE:” will not work because the TSFE global object only exists in the FE context. The “LIT:” key will not work either as it is used to compare TypoScript constants, which are not available in the BE context.
  • Note that conditions such as “PIDupInRootline” or “treeLevel” will apply correctly to pages that are being created but are not yet saved.

Furthermore the following condition is available only in TSconfig:

adminUser

Syntax:

[adminUser = 0/1]

Comparison

Checks whether the current BE user has admin rights or not. Value is 1 if user is admin, 0 otherwise.

Example:

The following condition will apply only if the BE user is admin.

[adminUser = 1]

References

For a general discussion about TypoScript conditions, please refer to “TypoScript Syntax and In-depth Study”.

For a list of available conditions, please refer to the “TypoScript Reference”.

19204: TYPO3 Core - Options from extra_page_cm_options should be able to be hidden individually [Closed; assigned to Oliver Hader] & 16251: TYPO3 Core - Disable "versioning"-menuitem via contextMenu.[key].disableItems in User TSconfig [Resolved; assigned to Jeff Segars]

doc_core_tsconfig -> userTS -> OPTIONS

Change description of contextMenu.[key].disableItems to:

  • Property: contextMenu.[key].disableItems
  • Description:[...]Items to disable are (for "page" type - that is database records):

view,edit,hide,new,info,copy,cut,paste,delete,move_wizard, history,perms,new_wizard,hide,edit_access,edit_pageheader,db_list,versioning,moreoptions[...]

19061: TYPO3 Core - [feature] Configuration of uploads and create folder in linkbrowser [Resolved; assigned to Steffen Kamper]

Steffen, 2008-10-20

doc_core_tsconfig -> userTS -> OPTIONS

New properties:

  • Property: folderTree.uploadFieldsInLinkBrowser
  • Data type: int
  • Description: This value defines the number of upload fields in the element browser. Default value is 3, if set to 0, no upload form will be shown.
  • Default: 3
  • Property: folderTree.hideCreateFolder
  • Data type: boolean
  • Description: If set, the user can't create new folders.
  • Default: false

17297: TYPO3 Core - Extend TCEFORM_confObj on Page TSconfig by property keepItems [Closed; assigned to Oliver Hader]

Olly, 2008-12-30

Insert in doc_core_tsconfig, Page TSconfig, section TCEFORM_confObj, before property "removeItems":

  • Property: keepItems
  • Data type: list of values
  • Description: (applies to select-types only) This keeps in the list only the items defined here. All others are removed.
  • Example:
TCEFORM.pages.doktype {
    # Show only standard and “Spacer” page types
  keepItems = 1,199
}

New items wizards

19962: TYPO3 Core - Feature: NewRecordWizard with grouping and sorting [Resolved; assigned to Steffen Kamper]

Steffen, 2008-02-17

Documentation of New Record Wizard, pageTS config

  • Description: Define an alternate order for the groups of records in the new records wizard. Pages and content elements will always be on top, but the order of other record groups can be changed.

Records are grouped by extension keys, plus the special key “system” for records provided by the TYPO3 Core.

  • Data type: list of values
  • Example:
mod.wizards.newRecord.order = tt_news

19382: TYPO3 Core - New Element Wizard has no option for hiding Elements via pageTS [Closed; assigned to Steffen Kamper]

Steffen, 2008-02-05

Documentation of New Content Element Wizard

pageTS config, mod.wizards.newContentElement

  • Property: renderMode
  • Data type: string
  • Description: Alternative rendering mode; set to “tabs”, if you want tabs.
  • Default: empty
  • Example:
mod.wizards.newContentElement.renderMode = tabs
  • Property: wizardItems.[group]
  • Data type: array
  • Description: In the new content element wizard, content element types are grouped together by type. Each such group can be configured independently. The four default groups are: “common”, “special”, “forms” and “plugins”. The configuration options below apply to any group.
  • Property: wizardItems.[group].header
  • Data type: string (localized)
  • Description: Name of the group
  • Property: wizardItems.[group].show
  • Data type: string
  • Description: Comma-separated list of items to show in the group. Use “*” to show all.
  • Example:
  # Hide bulletList
mod.wizards.newContentElement.wizardItems.common.show := removeFromList(bullets)

  # Only show text and textpic in common
mod.wizards.newContentElement.wizardItems.common.show = text,textpic
  • Property: wizardItems.[group].elements
  • Data type: array
  • Description: List of items in the group
  • Property: wizardItems.[group].elements.[name]
  • Data type: array
  • Description: Configuration of a single item
  • Property: wizardItems.[group].elements.[name].icon
  • Data type: string
  • Description: Path to the icon
  • Property: wizardItems.[group].elements.[name].title
  • Data type: string
  • Description: Title of the wizard
  • Property: wizardItems.[group].elements.[name].description
  • Data type: string
  • Description: Description of the wizard
  • Property: wizardItems.[group].elements.[name].tt_content_defValues
  • Data type: array
  • Description: Default values for tt_content

Examples

Add a new element (header) to the “common” group:

mod.wizards.newContentElement.wizardItems.common.elements.header {
	icon = gfx/c_wiz/regular_text.gif
	title = Header
	description = Adds a header element only
	tt_content_defValues {
		CType = header
	}
}
mod.wizards.newContentElement.wizardItems.common.show := addToList(header)

Create a new group and add a (prefilled) element to it:

mod.wizards.newContentElement.wizardItems.myGroup {
	header = My Company Special Items
	elements.customText {
		icon = gfx/c_wiz/regular_text.gif
		title = Introtext for national startpage
		description = use this element for all national startpages 
		tt_content_defValues {
			CType = text
			bodytext ( 
<h2>Section Header</h2>
<p class="bodytext">Lorem ipsum dolor sit amet, consectetur, sadipisci velit ...</p>
			)
			header = Section Header
			header_layout = 100
		}
	}
}
mod.wizards.newContentElement.wizardItems.myGroup.show = customText

20014: TYPO3 Core - Page TS option to disable available languages [Closed]

Xavier Perseguers, 23.03.2009

Page TSconfig -> Page (mod.SHARED): Add new property

  • Property: disableLanguages
  • Data type: string
  • Description: Comma-separated list of language UID which will be disabled in the given page tree.

20265: TYPO3 Core - Hide "Save and View"-button when editing a content-element [Closed; assigned to Steffen Kamper]

Steffen, 2009-04-19

->OPTIONS

  • Property: saveDocView, saveDocView.[table]
  • Data type: boolean
  • Description: If set, a button "Save and view" will appear in TCEFORMs. Any value set for a single table will override the default value set to the object "saveDocView".
  • Default: 1

20319: TYPO3 Core - Hide View-icon in listview with doktypes 254 and 255 [Closed; assigned to Steffen Kamper]

Steffen, 2009-04-19

mod.web_list

  • Property: noViewWithDokTypes
  • Data type: string
  • Description: Hide view icon for the defined doktypes (comma-separated)
  • Default: 254,255

20095: TYPO3 Core - Listview: default limits are hardcoded [Resolved; assigned to Steffen Kamper]

Steffen, 2009-04-19

mod.web_list

  • Property: itemsLimitSingleTable
  • Data type: int+
  • Description: Set the default maximum number of items to show in single table view
  • Default: 100
  • Property: itemsLimitPerTable
  • Data type: int+
  • Description: Set the default maximum number of items to show per table
  • Default: 20

20918: TYPO3 Core - Integrate an option to deactivate shortcuts completely [Closed; assigned to Rupert Germann]

Christopher, 3.9.2009

User TSconfig, ->OPTIONS, above "shortcutFrame", new property:

  • Property: enableShortcuts
  • Data type: boolean
  • Description: Enables the usage of shortcuts in the backend.
  • Default: 1

Change the description for "shortcutFrame" (result of the discussion in core-list, #11773):

  • Description: If set, the shortcut frame in the bottom of the window appears. This frame contains the shortcuts, the search field and the workspace selector. Note: Only takes effect, if alt_main.php, the old backend from TYPO3 4.1, is used.

New User TSconfig options

Francois, 09.10.2009, on behalf of Kasper

  • Property: workspaces.allowed_languages.[workspaceId]
  • Data type: list of sys_language uids

Description: This is a list of sys_language uids which will be allowed in a workspace. This list - if set - will override the allowed languages list in the BE usergroup configuration.

  • Property: checkPageLanguageOverlay
  • Data type: boolean (0/1)
  • Description: If set, localized fields in flexforms are shown only for languages which the current page is translated to.

17874: TYPO3 Core - Add suggest-like feature to TCEforms [Closed; assigned to Rupert Germann]

Rupert

section ->TCEFORM:

(add row at the end of the table)


  • Property:

suggest.default

suggest.[queryTable]


[tablename].[field].suggest.default

[tablename].[field].suggest.[queryTable]

  • Data type:

->TCEFORM_suggest

  • Description:

Configuration for the "suggest" wizard. Each level of the configuration overwrites the values of the level below it. "suggest.default" is overwritten by "suggest.[queryTable]". Both are overwriten by "[tablename].[field].suggest.default" which itself is overwritten by "[tablename].[field].suggest.[queryTable]"


suggest.default:

Configuration for all suggest wizards in all tables


suggest.[queryTable]:

Configuration for all suggest wizards from all tables listing records from table [queryTable]


[tablename].[field].suggest.default

Configuration for the suggest wizard for field [field] in table [tablename]


[tablename].[field].suggest.[queryTable]

Configuration for the suggest wizard for field [field] in table [tablename] listing records from [queryTable]


->TCEFORM_suggest

doc_core_tsconfig after section ->TCEFORM_confObj


Properties for the suggest wizard (see introduction above).


(insert table, columns:Property,Data type,Description)

  • Property: pidList
  • Data type: list of values
  • Description: Limit the search to certain pages (and their subpages). When pidList is empty all pages will be included in the search (as long as the be_user is allowed to see them)
  • Example:
TCEFORM.suggest.default {
  # sets the pidList for a suggest fields in all tables
  pidList = 1,2,3,45
}
  • Property: pidDepth
  • Data type: int+
  • Description: Expand pidList by this number of levels. Has only an effect if pidList has a value.
  • Example:
TCEFORM.suggest.default {
  pidList = 6,7
  pidDepth = 4
}
  • Property: minimumCharacters
  • Data type: int+
  • Description: Minimum number of characters needed to start the search. Works only for single fields:
  • Example:
TCEFORM.pages.storage_pid.suggest.default {
  minimumCharacters = 3
}
  • Default: 2
  • Property: maxPathTitleLength
  • Data type: int+
  • Description: Maximum number of characters to display when a path element is too long
  • Example:
TCEFORM.suggest.default {
  maxPathTitleLength = 30
}
  • Property: searchWholePhrase
  • Data type: boolean
  • Description: Whether to do a LIKE=%mystring% (searchWholePhrase = 1) or a LIKE=mystring% (to do a real find as you type)
  • Example:
TCEFORM.pages.storage_pid.suggest.default {
  # configures the sugesst wizard for the field "storage_pid" in table "pages" to search only for whole phrases
  searchWholePhrase = 1
}
  • Default: 0
  • Property: searchCondition
  • Data type: string
  • Description: Additional WHERE clause (no AND needed to prepend)
  • Example:
TCEFORM.pages.storage_pid.suggest.default {
  # configures the sugesst wizard for the field "storage_pid" in table "pages" to search only for pages with doktype=1
  searchCondition = doktype=1
}
  • Property: cssClass
  • Data type: string
  • Description: add a CSS class to every list item of the result list.
  • Example:
TCEFORM.suggest.pages {
  # configures all sugest wizards listing records from table "pages" to add the css-class "pages" to every list item of the result list.
  cssClass = pages
}
  • Property: receiverClass
  • Data type: string
  • Description: PHP class alternative receiver class - the file that holds the class needs to be included manually before calling the suggest feature, should be derived from "t3lib_tceforms_suggest_defaultreceiver"
  • Default: t3lib_tceforms_suggest_defaultreceiver
  • Property: renderFunc
  • Data type: string
  • Description: User function to manipulate the displayed records in the result
  • Property: hide
  • Data type: boolean
  • Description: Hide the suggest field. Works only for single fields.
  • Example:
TCEFORM.pages.storage_pid.suggest.default {
  hide = 1
}

21063: TYPO3 Core - Restrict access to "Clear RTE Cache" option in cache menu [Closed; assigned to Stanislas Rolland]

Stan, 2009-09-16, Restrict access to "Clear RTE Cache" option in cache menu

doc_core_tsconfig -> userTS -> OPTIONS

Add following property after property clearCache.all:

  • Property: clearCache.clearRTECache
  • Data type: boolean
  • Description: If set, the option «Clear RTE Cache» is enabled in the Clear Cache menu. Note that the option is always available to admin users.
  • Default: 0

20146: TYPO3 Core - Integration of mass file uploader [Closed; assigned to Benni Mack]

Chris Müller, 2010-01-18

In User TSconfig, SETUP

  • Property: enableFlashUploader
  • Data type: boolean
  • Description: This option enables the Flash-based uploader in the File module, which allows to select multiple files at once when uploading files. It requires to have the Flash plugin installed (Flash 9 or higher).
  • Default:

21013: TYPO3 Core - Make resizable and flexible textareas configurable, set default maxHeight to 600 [Closed; assigned to Steffen Kamper]

Chris Müller, 2010-01-18

In User TSconfig, SETUP

  • Property: resizeTextareas
  • Data type: boolean
  • Description: This option makes textareas resizable. When moving towards the right or bottom border of the textarea, the mouse cursor changes to a resize cursor. This is active by default.
  • Default: 1
  • Property: resizeTextareas_MaxHeight
  • Data type: int+
  • Description: Defines the maximal height of textarea (in pixels).
  • Default: 600
  • Property: resizeTextareas_Flexible
  • Data type: boolean
  • Description: This option makes textareas flexible, which means that their height grows automatically while typing. Limit is the maximal height set. This is active by default.
  • Default: 1

Core APIs (doc_core_api)

20717: TYPO3 Core - Store separate extlist for the frontend [Closed; assigned to Rupert Germann]

Rupert

doc_core_api: chapter 2.1
section: "Import and install of extensions"

after:

  • Loaded extensions are registered in a global variable, $TYPO3_LOADED_EXT, available in both frontend and backend of TYPO3. The loading and registration process happens in t3lib/config_default.php.

insert:

  • When rendering FE content (TYPO3_MODE = FE) $TYPO3_LOADED_EXT contains only extensions where the $EM_CONF option "doNotLoadInFE" is not set.

section: "ext_emconf.php"
new parameter in table with emconf parameters after "priority"

  • Key: doNotLoadInFE
  • Data Type: Boolean
  • Description: If set, the extension will not be included in the list of extensions to be loaded in the frontend (TYPO3_CONF_VARS['extListFE']). Background: In TYPO3 versions before 4.3 the temp_CACHED* files in folder typo3conf/ did always contain the content of the ext_tables.php and ext_localconf.php files of all installed extensions. Not all installed extensions are needed to render frontend output (e.g. wizard_sortpages, tstemplate_analyzer and others) and so their $EM_CONF array has the flag "doNotLoadInFE" set. This will prevent TYPO3 from adding the extension's ext_localconf.php and ext_tables.php to the temp_CACHED files when rendering frontend content. Since 'extListFE' is shorter than the list of all extensions this will result in 2 new temp_CACHED_FE* files which are smaller than the files containing all extensions settings. This can save some precious milliseconds when delivering content.

19217: TYPO3 Core - Feature: Mark extension as write protected [Closed; assigned to Dmitry Dulepov]

Benni

In the table of the parameters in the ext_emconf.php, add a new state to the state list: "excludeFromUpdates". The descriptions reads: "This state makes it impossible to update the extension through the extension manager (neither by the Update mechanism, nor by uploading a newer version to the installation). This is very useful if you made local changes to an extension for a specific installation and don't want any admin to overwrite them."

19958: TYPO3 Core - Configurable Subcategories for ext_conf_template.txt [Closed; assigned to Francois Suter]

François: Custom subcategories for extension configuration

section: ext_conf_template.txt

The role of this file was explained above, in the list of reserved filenames. The syntax used in this file is similar to the syntax used for the TypoScript constants files. This syntax is described in the "TypoScript Syntax and In-depth Study" manual (doc_core_ts). A typical configuration declaration will look like this:

#cat=basic//; type=integer; label=Number of entries per page: Set the number of log entries to display per page, when viewing all log entries
entriesPerPage = 25

Using custom subcategories is also possible for extension configuration options. Extending the previous example:

#customsubcategory=limits=LLL:EXT:devlog/locallang.xml:limits

#cat=basic/limits/; type=integer; label=Number of entries per page: Set the number of log entries to display per page, when viewing all log entries
entriesPerPage = 25

NOTE: The full syntax description will be available in "TypoScript Syntax and In-depth Study". It doesn't exist yet, but will be based on what's available in doc_doc_tstemplates, which is obsolete and destined to disappear.

21168: TYPO3 Core - Improve the error and exception handling [Closed; assigned to Rupert Germann]

Rupert Germann: Manual for the improved error and exceptionhandling: File:Error and exception handling.odt

20858: TYPO3 Core - Add support for flash messages in the backend [Closed; assigned to Ingo Renner]

Followed by: 21207: TYPO3 Core - Improve flashmessages API [Closed; assigned to Rupert Germann]

Ingo Renner and Rupert Germann: File:Flash messages v2.odt

20689: TYPO3 Core - Add a registry to t3lib [Closed; assigned to Ingo Renner]

Ingo Renner: File:Sys registry.odt


17874: TYPO3 Core - Add suggest-like feature to TCEforms [Closed; assigned to Rupert Germann]

Steffen Kamper


doc_core_api section: Specific wizard configuration options based on type

(add row at the end of the table)


Type: suggest This renders an input field next to a select field of type "group" (internal_type=db) or of type "select" (using foreign_table). After the user has typed at least 2 (minimumCharacters) characters to this field a search will start and show a list of records matching the searchword. The "suggest" wizard's properties can be configured directly in TCA or in page TSconfig (TCEFORM.suggest.default, TCEFORM.suggest.[queryTable]....)



Key: pidList
Type: list of values

Description: Limit the search to certain pages (and their subpages). When pidList is empty all pages will be included in the search (as long as the be_user is allowed to see them)

Example:

$TCA['pages']['columns']['storage_pid']['config']['wizards']['suggest'] = array(
	'type' => 'suggest',
	'default' => array(
		'pidList' => '1,2,3,45',
	),
);

Key: pidDepth
Type: integer
Description: Expand pidList by this number of levels. Has only an effect if pidList has a value.

Example:

$TCA['pages']['columns']['storage_pid']['config']['wizards']['suggest'] = array(
	'type' => 'suggest',
	'default' => array(
		'pidList' => '6,7',
		'pidDepth' => 4
	),
);

Key: minimumCharacters

Type: integer

Description: Minimum number of characters needed to start the search. Works only in "default".


Key: maxPathTitleLength

Type: integer

Description: maximum number of characters to display when a path element is too long


Key: searchWholePhrase

Type: boolean

Description: Whether to do a LIKE=%mystring% (searchWholePhrase = 1) or a LIKE=mystring% (to do a real find as you type), default: 0

Example:

$TCA['pages']['columns']['storage_pid']['config']['wizards']['suggest'] = array(
	'type' => 'suggest',
	'default' => array(
		'searchWholePhrase' => 1,
	),
);

Key: searchCondition
Type: string
Description: Additional WHERE clause (no AND needed to prepend)

Example:

# configures the sugesst wizard for the field "storage_pid" in table "pages" to search only for pages with doktype=1
$TCA['pages']['columns']['storage_pid']['config']['wizards']['suggest'] = array(
	'type' => 'suggest',
	'default' => array(
		'searchCondition' => 'doktype=1',
	),
);

Key: cssClass
Type: string
Description: add a CSS class to every list item of the result list.


Key: receiverClass
Type: string
Description: PHP class alternative receiver class - the file that holds the class needs to be included manually before calling the suggest feature (default: t3lib_tceforms_suggest_defaultreceiver), should be derived from "t3lib_tceforms_suggest_defaultreceiver"


Key: renderFunc
Type: string
Description: Userfunction to manipulate the displayed records in the result





insert after the wizard examples:


Example - add a suggest wizard


IMAGE [suggest_1.png]

suggest wizard


IMAGE [suggest_2.png]

suggest wizard showing results


The suggest-feature is implemented as a wizard to TCEforms.

It can be added like any other wizard, basically by modifying the TCA of a certain field. Here's the configuration which is used for the suggest wizard of the field "storage_pid" in table "pages".

$TCA['pages']['columns']['storage_pid']['config']['wizards']['suggest'] = array(
	'type' => 'suggest',
	'default' => array(
		'searchWholePhrase' => 1,
		'maxPathTitleLength' => 40,
		'maxItemsInResultList' => 5
	),
	'pages' => array(
		'searchCondition' => 'doktype=1',
	),
);

The tables that are queried are the ones used in $TCA['pages']['columns']['storage_pid']['config']['allowed'].

The wizard can be configured differently for each of these tables with the settings in the "queryTable" sections.

The settings in "default" will be taken for all "queryTables". The settings in the "queryTable" section (pages.) will override the default settings.

18858: TYPO3 Core - Integrate possibility to define enabledControls in TCA [Closed; assigned to Oliver Hader]

Olly: IRRE - Integrate possibility to define enabledControls in TCA

In doc_core_api, $TCA array reference, TYPE: "inline" -> new property for ['columns'][fieldname]['config']['appearance']

  • enabledControls (array): Associative array with the keys 'info', 'new', 'dragdrop', 'sort', 'hide', 'delete', 'localize'. If the accordant values are set to a booelan value (true or false), the control is shown or hidden in the header of each record.


Using 3rd Party JS-Libraries in Backend

Steffen Kamper

Now using JS-libs in BE is very easy if you use template.php (as all modules does).

Normally you have an instance of template.php in $this->doc (which will be used in the following examples)

1) Using Prototype library:

use this syntax:

$this->doc->loadPrototype();

that's all, prototype will be added to head of your document, any double inclusion will be prevented.

2) Using Scriptaculous

use this syntax:

 $this->doc->loadScriptaculous();<br> 

You want modules? any of this modules are valid: builder, effects, dragdrop, controls, slider

use one or more like:

$this->doc->loadScriptaculous('slider');
$this->doc->loadScriptaculous('effects,dragdrop');

If modules depend on other modules, it will automatically be added. Don't care order of calling, you can call this as often as you want, it will be included once with the correct modules.

If you want all available modules, just call it with keyword 'all'<br>If you include Scriptaculous, Prototype will be added automatically.

3) Using extJS

use this syntax:

$this->doc->loadExtJS();

There are 2 (optional) Parameters in this call:

$this->doc->loadExtJS($css=true, $theme=true);

first parameter $css (boolean): if set, ext-all.css will be added automatically second parameter $theme (boolean): if set, theme-grey will be added automatically Additionally the function takes care of:

  • adding correct adapter
  • adding localization file of BE-User language
  • adding Ext.BLANK_IMAGE_URL

If you want to debug in extJS-lib, you can force debug-variant by calling

$this->doc->setExtJSdebug();

16323: TYPO3 Core - Implement file_reference for TCA "group" type. Files can be referenced instead of copied to upload folder [Closed; assigned to Christian Kuhn]

Christian, 2009-07-02

Chapter 4.2 $TCA array reference -> ['columns'][fieldname]['config'] / TYPE: "group" -> internal_type

Description: - There are two options for a value: + There are four options for a value:

2. "file_reference" - this will create a field where files can be referenced. In contrast to "file" referenced files (usually from fileadmin/) will not be copied to upload folder. Warning, use this carefully: Your content elements will be broken if you delete referenced files in the filesystem!

20644: TYPO3 Core - Feature: Add Linebreak in Palette of TCEFORMS [Closed; assigned to Steffen Kamper]

Steffen Kamper

doc_core_api, end of this page https://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.2.0/view/4/2/#id4442105

Fields in Palette are rendered in one line. If you add many fields you may want to split them into several lines. Use the seperator "--linebreak--" for a linebreak.

Example:

'palettes' => Array (
   '1' => Array('showitem' => 'salutation, firstname, lastname, --linebreak--, mobile, phone, fax, --linebreak--, email, email_work),
) 

16586: TYPO3 Core - displayCond for flexforms, that affects on row of element [Closed; assigned to Andreas Otto †]

Andreas Otto, on behalf of Tolleiv Nietsch, 2009-08-09
Chapter 4.2 -> ['columns'][fieldname] section

(add after: For FlexForm elements the fields are tags on same level. If <langChildren> is enabled, then the value of other fields on same level is taken from the same language. ) The field-values of the FlexForm-parent record are prefixed with "parentRec.". These fields can be used like every other field (add to the examples part ot the very bottom)

This example would require the header-field of the FlexForm-parent record to be true, otherweise the FlexForm field is not displayed. (Works only within FlexForm datastructure definitions)

<displayCond>FIELD:parentRec.header:REQ:true</displayCond>

20385: TYPO3 Core - User Setup Rewrite #4 [Closed; assigned to Steffen Kamper]

Steffen, 2009-06-02, new chapter 7, after $TCA

User Settings ($GLOBALS['TYPO3_USER_SETTINGS'])

User settings have a configuration array that is quite similar to the $TCA, but has less options.

$GLOBALS['TYPO3_USER_SETTINGS']['ctrl']
property: dividers2tabs
data type: int
description: Render user setup with(out) tabs, settings are as in TCA: 0 = no tabs, 1 = tabs, empty tabs are hidden, 2 = tabs, empty tabs are disabled
default: 1

$GLOBALS['TYPO3_USER_SETTINGS']['columns'][fieldname]
This contains the configuration array for single fields in the user settings. This array allows the following configurations:

property: type
data type: string
description: defines the type of the input field
it type=user you need to define userFunc too. Example:

'installToolEnableFile' => array(
'type' => 'user',
'label' => 'LLL:EXT:setup/mod/locallang.xml:InstallToolEnableFileButton',
'userFunc' => 'SC_mod_user_setup_index->renderInstallToolEnableFileButton',
'access' => 'admin',
)

allowed: text, password, check, select, user


property: label
data type: string
description: label for the input field

property: csh
data type: string
description: CSH key for the input field

property: access
data type: string
description: access control. At the moment only a admin-check is implemented
allowed: admin

property: table
data type: string
description: if the user setting is saved in a DB table, this property sets the table. At the moment only be_users is implemented 
allowed: be_users


property: eval
data type: string
description: eval field to md5 (used for password field)
allowed: md5

property: items
data type: array
description: array of key-value pair for select items 
allowed: only used by type=select


property: itemsProcFunc
data type: string
description: define extern method for render items of select. Other than TCA you have to render the <select> tag too 
allowed: only for type=select, use class->method syntax


$GLOBALS['TYPO3_USER_SETTINGS']['showitem']
This string is used for rendering the FORM in the user setup module. Fields are rendered in the order of this string containing the commalist of fieldnames.
To use a tab insert a "--div--;LABEL" item in the commalist.

Media manual

Manual for the new media CE (should become part of the manual of CSS Styled Content) https://forge.typo3.org/attachments/11257/doc_core_mediace_v2.sxw

The manual has been written for TYPO3 4.3 (not 4.2 as the cover says) by SteffenK and proofread by Jeff; see 20284: TYPO3 Core - [Feature] New Multimedia CE [Closed; assigned to Steffen Kamper].

Jeff wrote in #20284: "Still needs another pass, restructuring, and more content before its officially released but its a step the in the right direction :)"

November 2011: As far as the document above describes the TypoScript properties of the cObjects MEDIA, SWFOBJECT and QTOBJECT, it is now integrated in TSref. -Christopher.