This page belongs to the Core Team (category Core Team)

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!

1 TSRef (doc_core_tsref)
- 1.1 Changes for TYPO3 4.5
- 1.2 Changes for TYPO3 4.4
2 TSConfig (doc_core_tsconfig)
- 2.1 Changes for TYPO3 4.5
- 2.2 Changes for TYPO3 4.4
  - 2.2.1 22701: Core - Remove old_backend [Closed to Steffen Kamper]
  - 2.2.2 notificationEmail_subject and notificationEmail_body
3 TCA reference (doc_core_tca)
- 3.1 Changes for TYPO3 4.4
- 3.2 Changes for TYPO3 4.5
  - 3.2.1 23922: Core - [Feature] TCA tree [Closed to Steffen Kamper] -- 2011-04-18 (olly): Updated the documentation
4 Core APIs (doc_core_api)

TSRef (doc_core_tsref)

Changes for TYPO3 4.5

23677: Core - [Feature] Add SVG support for all browsers [Closed to Steffen Kamper]

Steffen,

TSref: SVG (new cObj)

Property: width
Data type: int /stdWrap
Description: width of SVG
default: 600

Property: height
Data type: int /stdWrap
Description: height of SVG
default: 400

Property: src
Data type: file resource /stdWrap
Description: SVG file resource
default:

Property: value
Data type: XML /stdWrap
Description: SVG raw XML. When src is defined the file will be loaded and value is ignored.
default:

Property: noscript
Data type: text /stdWrap
Description: Output if SVG output is not possible
default:

Property: stdWrap
Data type: ->stdWrap

Example:

10 = SVG
10 {
 width = 600
 height = 600
 value (
      <rect x="100" y="100" width="500" height="200" fill="white" stroke="black" stroke-width="5px"/>
      <line x1="0" y1="200" x2="700" y2="200" stroke="red" stroke-width="20px"/>
      <polygon points="185 0 125 25 185 100" transform="rotate(135 125 25)" />
      <circle cx="190" cy="150" r="40" stroke="black" stroke-width="2" fill="yellow"/>
 )
 noscript.cObject = TEXT
 noscript.cObject.value = no svg rendering possible, use a browser
}

TSref: CONFIG, add in javascriptLibs:

 #load SVG library
SVG = 1
 #add SVG debug
SVG.debug = 1
 #force render with flash
SVG.forceFlash = 1

The above already includes "stdWrap everywhere" 24065: Core - Optimize stdWrap usage for TypoScript content element SVG [Closed to Steffen Kamper]

23744: Core - A new TypoScript cObject: FLUIDTEMPLATE [Closed to Benjamin Mack]

Benni,

Documentation for feature #23744 - FLUID-Template To be insterted as new cObject in TSref / FLUIDTEMPLATE:

The TypoScript object FLUIDTEMPLATE works in a similar way as the regular "marker"-based TEMPLATE object. However, it does not use marker or subparts, but allows Fluid-style variables with curly braces.

Note: The extensions "Fluid" and "Extbase" need to be installed for this.

FLUIDTEMPLATE

Property: file
Data type: string+stdWrap
Description: the FLUID template file

Property: layoutRootPath
Data type: filepath+stdWrap

Property: partialRootPath
Data type: filepath+stdWrap

Property: format
Data type: keyword+stdWrap
Description: Sets the format of the current request
Default: html

Property: extbase.pluginName
Data type: string+stdWrap

Property: extbase.controllerExtensionName
Data type: string+stdWrap

Property: extbase.controllerName
Data type: string+stdWrap

Property: extbase.controllerActionName
Data type: string+stdWrap

Property: variables
Data type: array of cObjects
Description: the keys are the variable names in Fluid, reserved variables are "data" and "current", which are filled automatically with the current dataset.

Proerty: stdWrap
Data type: ->stdWrap

an example would be:

10 = FLUIDTEMPLATE
10 {
  file = fileadmin/templates/MyTemplate.html
  partialRootPath = fileadmin/templates/partial/
  variables {
     mylabel = TEXT
     mylabel.value = Label from TypoScript coming
  }
}

the fluid template (fileadmin/templates/MyTemplate.html) could then look like this:

{mylabel}

<f:format.html>{data.bodytext}</f:format.html>

The above already includes "stdWrap everywhere" 23897: Core - Optimize stdWrap usage for TypoScript content element FLUIDTEMPLATE [Closed to -]

14894: Core - stdWrap.age should differenciate between singular/plural [Closed to Susanne Moog]

Susanne,

Change description of stdWrap->age: From: If you set this property with a non-integer, it's used to format the four units. This is the default value: " min| hrs| days| yrs"

To: If you set this property with a non-integer, it is used to format the eight units. The first four values are the plural values and the last four are singular. This is the default string: " min| hrs| days| yrs| min| hour| day| year"

Set another string if you want to change the units. You may include the "-signs. They are removed anyway, but they make sure that a space which you might want between the number and the unit stays.

Example:

libdate = TEXT
libdate.data = page:tstamp
libdate.age = " Minuten | Stunden | Tage | Jahre | Minute | Stunde | Tag | Jahr"

15288: Core - Ellipse Gifbuilder Function [Closed to Susanne Moog]

Susanne,

TSref: GIFBUILDER, new section ELLIPSE

Property: dimensions
Data type: x,y,w,h +calc
Description: Dimensions of a filled ellipse.

x,y is the offset. w,h is the dimensions. Dimensions of 1 will result in 1-pixel wide lines!

Property: color
Data type: GraphicColor
Description: fill-color

Example:

 file = GIFBUILDER
 file {
   XY = 200,200
   format = jpg
   quality = 100
   10 = ELLIPSE
   10.dimensions = 100,100,50,50
   10.color = red
 }

[tsref:->GIFBUILDER.(GBObj).ELLIPSE]

16209: Core - additional wrap for mailform.radio [Closed to Susanne Moog]

Susanne,

TSref Section "FORM":

radioInputWrap ->stdWrap Wraps the input element and label of a radio button.

20497: Core - New options noRescale and resoultionFactor for getImgResource() [Closed to Benjamin Mack]

Added by Benni, text by Stefan Geith

To be insterted to Properties-Table in TSref / Functions / imgResource:

Property: noScale
Data type: boolean
Description: If set, the image itself will never be scaled. Only width and height are calculated according to the other properties, so that image is _displayed_ resizedly, but original file is used. Can be used for creating PDFs or printing of pages, where the original file could provide much better quality than a rescaled one.

Example:
 // Could e.g. have 1600 x 1200 pixels
 file = test.jpg 
 file.width = 240m
 file.height = 240m
 file.noScale = 1
This example results in an image tag like the following. Note that src="test.jpg" is the _original_ file:
 <img src="test.jpg" width="240" height="180" />

Default: 0

22279: Core - Add .numberFormat function to stdWrap [Closed to Steffen Kamper]

Sebastian Michaelsen

TSref: 1.5 Function / stdWrap (before date), new function numberFormat

Data type: ->numberFormat
Description: Format a float value to any number format you need (e.g. useful for prices).

TSref: 1.5 Functions, new section numberFormat

With this property you can format a float value and display it as you want, for example as a price. It is a wrapper for the number_format() function of PHP. You can define how many decimals you want and which separators you want for decimals and thousands.

Table of properties:

Property: decimals
Data type: integer
Description: Number of decimals the formatted number will have. Defaults to 0, so that your input will in that case be rounded up or down to the next integer.

Property: dec_point
Data type: string
Description: Character that divides the decimals from the rest of the number. Defaults to "."

Property: thousands_sep
Data type: string
Description: Character that divides the thousands of the number. Defaults to ",", set an empty value to have no thousands separator.

Examples:

lib.myPrice = TEXT
lib.myPrice {
  value = 0.8
  numberFormat {
    decimals = 2
    dec_point = ,
  }
  noTrimWrap = || €|
}
# Will result in "0,80 €"

lib.carViews = CONTENT
lib.carViews {
  table = tx_mycarext_car
  select.pidInList = 42
  renderObj = TEXT
  renderObj {
    field = views
    numberFormat.thousands_sep = .
    numberFormat.decimals = 3
  }
}
# Will result in something like "2.055"

23528: Core - Allow easy use of lightbox style image enlargement in the frontend [Closed to Susanne Moog]

Susanne,

Functions -> imageLinkWrap:

Change datatype of JSwindow to "boolean /stdWrap"

Add property:

Property: directImageLink
Data type: boolean
Description: If true, a link to the generated image file will be returned directly (showpic.php is not used)

Add property:

Property: linkParams
Data type: typolink
Description: Allows the manipulation of the generated typolink if JSwindow is not used.

Example:

linkParams.ATagParams.dataWrap =  class="{$styles.content.imgtext.linkWrap.lightboxCssClass}" rel="{$styles.content.imgtext.linkWrap.lightboxRelAttribute}"

23533: Core - TSConfig needs conditions for current page (backend) [Closed to Susanne Moog]

Susanne,

Add to "Condition reference", new condition "page":

page

Syntax:

[page|[field] = value]

This condition checks values of the current page record. While you can achieve the same with TSFE:[field] conditions in the frontend, this condition is usable in both backend and frontend.

Example:

With this condition you can do things depending on the layout field:

[page|layout = 1]

23760: Core - Let typolink honour secure filelink configuration [Closed to Ernesto Baschny]

Stan,

In function "typolink", add the following new property (after "addQueryString"):

Property: jumpurl
Data type: boolean
Description: Decides if the link should call the script with the jumpurl parameter in order to register any clicks in the stat. This works the same as "filelink.jumpurl", see more details there.

Example:

typolink.jumpurl = 1
typolink.jumpurl.secure = 1
typolink.jumpurl.secure.mimeTypes = list of mimetypes, syntax [ext] = [mimetype]

23844: Core - No possibility to completely disable the preview info box -> introduce new config setting [Closed to Jeff Segars]

Jeff,

TSRef - section "CONFIG"

Property: disablePreviewNotification
Data type: boolean
Description: Disables the "preview" notification box completely.
default: 0

24059: Core - Add basic support for RDFa in core (semantic web) [Closed to Jochen Rau]

Jochen Rau:

Add the line

"xhtml+rdfa_10" for XHTML+RDFa 1.0 doctype.

to the description of TLO CONFIG->doctype

Resulting list of doctypes:

"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.

"xhtml+rdfa_10" for XHTML+RDFa 1.0 doctype.

"xhtml_2" for XHTML 2 doctype.

"html5" for HTML5 doctype.

"none" for NO doctype at all.

---

Add the following property to the description of TLO CONFIG

Property: namespaces

Data type: array of strings
Description: This property enables you to add xml namespaces (xmlns) to the html tag. This is especially useful if you want to add RDFa or microformats to your html.

Example:

config.namespaces.dc = http://purl.org/dc/elements/1.1/
config.namespaces.foaf = http://xmlns.com/foaf/0.1/

The configuration will result in a html tag like

<html xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:foaf="http://xmlns.com/foaf/0.1/">

24443: Core - getBrowserInfo should recognize iOS and android for easier mobile optimization [Closed to Ernesto Baschny]

Andy,

Add the following browsers to the "Values and comparison" table of browsers (browser | identification):

Mozilla Firefox | firefox
Apple Safari | safari
Google Chrome | chrome

Add the following systems to the "Values and comparison" table of systems (system | identification):

Android | android
Chrome OS | chrome
OpenBSD/NetBSD/FreeBSD | unix_bsd
iOS | iOS
Windows 2000 | win2k
Windows XP | winXP
Windows Vista | winVista
Windows 7 | win7

Add the following text and corresponding table (system | identification), e.g. after the Example of matching systems:

Note that for backwards compatibility, some systems are also matched by more generic strings. It is recommended to use the new identifiers documented above, but those are valid, too:

System | Generic but valid identification
Android | linux
Chrome OS | linux
iOS | mac
Windows 2000 | winNT
Windows XP | winNT
Windows Vista | winNT
Windows 7 | winNT

24545: Core - Rename config.doctype value "html_5" to "html5" [Closed to Steffen Gebert]

Sebastian M.

Apply the following changes to 1.6 Setup -> "CONFIG" -> doctype: Replace "html_5" with "html5" and add the Note "In TYPO3 4.4 the keyword for HTML5 is "html_5". This spelling is deprecated since TYPO3 4.5."

25317: Core - Typolink fails to link between two non-default page types [Closed to -]

Ernesto Baschny,

Document on "CONFIG"->linkVars that one should *not* include "type" parameter in the linkVars list (e.g. "config.linkVars = type"), as this can result in unexpected behaviour. See above mentioned bug report.

stdWrap everywhere

Following is a list of the properties, to which stdWrap has been added. It is ordered by their appearance in TSref.

The patches were made by Joey.

23921: Core - Optimize stdWrap usage for TypoScript content element HTML [Closed to Steffen Kamper]

diff

TSref: HTML

Property: stdWrap
Data type: ->stdWrap

(The property "value" already had stdWrap before.)

So now it's possible to use 2 times stdWrap, one with "value" and one with "stdWrap".

24063: Core - Optimize stdWrap usage for TypoScript content element TEXT [Closed to Steffen Kamper]

TSref: TEXT

Only optimizsation of when to call stdWrap; no new stdWrap anywhere.

23891: Core - Optimize stdWrap usage for TypoScript content element COA [Closed to Steffen Kamper], 23892: Core - Optimize stdWrap usage for TypoScript content element COA_INT [Closed to Steffen Kamper]

TSref: COA, COA_INT

Property: wrap
Data type: wrap /stdWrap

Property: includeLibs
Data type: list of resources /stdWrap
Description: (This property is used only if the object is COA_INT!, See introduction.)

This is a comma-separated list of resources that are included as PHP-scripts (with include_once() function) if this script is included. This is possible to do because any include-files will be known before the scripts are included. That's not the case with the regular PHP_SCRIPT cObject.

23896: Core - Optimize stdWrap usage for TypoScript content element FILE [Closed to Steffen Kamper]

diff

TSref: FILE

Property: file
Data type: resource/stdWrap
Desription: If the resource is jpg,gif,jpeg,png the image is inserted as an image-tag. Al other formats is read and inserted into the HTML-code.

The maximum filesize of documents to be read is set to 1024 kb internally!

Property: linkWrap
Data type: linkWrap/stdWrap
Description: (before ".wrap")

Property: wrap
Data type: wrap/stdWrap

Property: stdWrap
Data type: ->stdWrap

23969: Core - Optimize stdWrap usage for TypoScript content element IMAGE [Closed to Susanne Moog]

TSref: IMAGE

No new stdWrap. But other missing stdWrap parameters will be added by another RFC changing the behaviour of cObj->cImage.

23970: Core - Optimize stdWrap usage for TypoScript content element IMG_RESOURCE [Closed to Ernesto Baschny]

TSref: IMG_RESOURCE

No new stdWrap anywhere, but same as above: Other missing stdWrap parameters will be added by another RFC changing the behaviour of cObj->cImage.

23888: Core - Optimize stdWrap usage for TypoScript content element CLEARGIF [Closed to Steffen Kamper]

diff

TSref: CLEARGIF

Property: wrap
Data type: wrap/stdWrap

Property: stdWrap
Data type: ->stdWrap

23890: Core - Optimize stdWrap usage for TypoScript content element CONTENT [Closed to Steffen Kamper]

diff

TSref: CONTENT

Property: slide
Data type: integer /stdWrap
Description: If set and no content element is found by the select command, then the rootLine will be traversed back until some content is found.

Possible values are “-1” (slide back up to the siteroot), “1” (only the current level) and “2” (up from one level back). Use -1 in combination with collect.

- .collect (int/stdWrap): If set, all content elements found on current and parent pages will be collected. Otherwise, the sliding would stop after the first hit. Set this value to the amount of levels to collect on, or use “-1” to collect up to the siteroot.
- .collectFuzzy (boolean/stdWrap): Only useful in collect mode. If no content elements have been found for the specified depth in collect mode, traverse further until at least one match has occurred.
- .collectReverse (boolean/stdWrap): Change order of elements in collect mode. If set, elements of the current page will be at the bottom.

Property: wrap
Data type: wrap/stdWrap
Description: Wrap the whole content story ...

23972: Core - Optimize stdWrap usage for TypoScript content element RECORDS [Closed to Susanne Moog]

TSref: RECORDS

nonsense example

Property: tables
Data type: list of tables /stdWrap

Property: dontCheckPid
Data type: boolean /stdWrap

Property: wrap
Data type: wrap /stdWrap

23898: Core - Optimize stdWrap usage for TypoScript content element HMENU [Closed to Steffen Kamper]

TSref: HMENU

Property: wrap
Data type: wrap/stdWrap

And present since TYPO3 4.5.4:

26483: Core - stdWrap for excludeUidList (HMENU) does not work [Resolved to -]

Roland Waldner:

Property: excludeUidList
Data type: list of integers /stdWrap

23895: Core - Optimize stdWrap usage for TypoScript content element CTABLE [Closed to Steffen Kamper]

TSref: CTABLE

Property: offset
Data type: x,y /stdWrap
Description: Offset from upper left corner
Default: 0,0

Property: tm
Data type: ->CARRAY + TDParams /stdWrap
Description: top menu

Property: lm
Data type: ->CARRAY + TDParams /stdWrap
Description: left menu

Property: rm
Data type: ->CARRAY + TDParams /stdWrap
Description: right menu

Property: bm
Data type: ->CARRAY + TDParams /stdWrap
Description: bottom menu

Property: c
Data type: ->CARRAY + TDParams /stdWrap
Description: content cell

Property: cMargins
Data type: margins /stdWrap
Description: Distance around the content cell "c"
Default: 0,0,0,0

Property: cWidth
Data type: pixels /stdWrap
Description: Width of the content cell "c"

Property: tableParams
Data type: <TABLE>-params /stdWrap
Description:
Default: border="0" cellspacing="0" cellpadding="0"

Property: stdWrap
Data type: ->stdWrap

24050: Core - Optimize stdWrap usage for TypoScript content element OTABLE [Closed to Steffen Kamper]

diff

TSref: OTABLE

Property: offset
Data type: x,y /stdWrap

Property: tableParams
Data type: <TABLE>-params /stdWrap

Property: stdWrap
Data type: ->stdWrap

23889: Core - Optimize stdWrap usage for TypoScript content element COLUMNS [Closed to Steffen Kamper]

TSref: COLUMNS

Property: tableParams
Data type: <TABLE>-params/stdWrap
Description:
default: border="0" cellspacing="0" cellpadding="0"

Property: TDParams
Data type: <TD>-params/stdWrap
Description:
default: valign="top"

Property: rows
Data type: int(range:2-20)/stdWrap
Description: The number of rows in the columns.
default: 2

Property: totalWidth
Data type: int/stdWrap
Description: The total width of the columns + gaps.

23920: Core - Optimize stdWrap usage for TypoScript content element HRULER [Closed to Steffen Kamper]

TSref: HRULER

Property: lineColor
Data type: HTML-color /stdWrap

Property: spaceLeft
Data type: pixels /stdWrap

Property: spaceRight
Data type: pixels /stdWrap

Property: tableWidth
Data type: string /stdWrap

(Senseless) example:

page.15 = HRULER
page.15.lineColor.field = uid
page.15.lineColor.wrap = #00|00
page.15.lineThickness = 2

==== 23974: Core - Optimize stdWrap usage for TypoScript content element IMGTEXT [Closed to Steffen Kamper] TSref: IMGTEXT

Property: noStretchAndMarginCells
Data type: boolean /stdWrap

==== 23886: Core - Optimize stdWrap usage for TypoScript content element CASE [Closed to Steffen Kamper] TSref: CASE

There where no missing stdWrap parameters so nothing to add.

23971: Core - Optimize stdWrap usage for TypoScript content element LOAD_REGISTER [Closed to Susanne Moog]

TSref: LOAD_REGISTER

Bug descriptiopn only speaks of optimization, not of new stdWrap anywhere.

RESTORE_REGISTER

TSref: RESTORE_REGISTER

Not needed. No issue, no discussion, no entry in ChangeLog

23981: Core - Optimize stdWrap usage for TypoScript content element FORM [Closed to Steffen Kamper]

TSref: FORM

Property: dataArray
Data type: (unchanged, but stdWrap for the subproperties:)
- dataArray.XXX.required
- dataArray.XXX.type
- dataArray.XXX.valueArray.YYY.selected
- dataArray.XXX.valueArray.YYY.value

Property: radioWrap.accessibilityWrap
Data type: wrap /stdWrap

Property: target
Data type: target /stdWrap

Property: method
Data type: form-method /stdWrap

Property: no_cache
Data type: string /stdWrap

Property: noValueInsert
Data type: boolean /stdWrap

Property: compensateFieldWidth
Data type: double /stdWrap

Property: locationData
Data type: boolean / string /stdWrap

Property: redirect
Data type: string /stdWrap

Property: goodMess
Data type: string /stdWrap

Property: badMess
Data type: string /stdWrap

Property: emailMess
Data type: string /stdWrap

Property: REQ
Data type: boolean /stdWrap

Property: REQ.layout
Data type: string /stdWrap

Property: COMMENT.layout
Data type: string /stdWrap

Property: CHECK.layout
Data type: string /stdWrap

Property: RADIO.layout
Data type: string /stdWrap

Property: LABEL.layout
Data type: string /stdWrap

Property: hiddenFields.stdWrap
Data type: ->stdWrap

Property: params
Data type: form-element tag parameters /stdWrap

Property: params.tagname
Data type: ->stdWrap

Property: wrapFieldName
Data type: wrap /stdWrap

Property: noWrapAttr
Data type: boolean /stdWrap

Property: arrayReturnMode
Data type: boolean /stdWrap

Property: accessibility
Data type: boolean /stdWrap

Property: formName
Data type: string /stdWrap

Property: fieldPrefix
Data type: string /stdWrap

Property: dontMd5FieldNames
Data type: boolean /stdWrap

24069: Core - Optimize stdWrap usage for TypoScript content element SEARCHRESULT [Closed to Steffen Kamper]

TSref: SEARCHRESULT

Property: target
Data type: target /stdWrap

Property: range
Data type: integer /stdWrap

Property: renderWrap
Data type: wrap /stdWrap

Property: noOrderBy
Data type: boolean /stdWrap

Property: wrap
Data type: wrap /stdWrap

24062: Core - Optimize stdWrap usage for TypoScript content element USER_INT [Closed to Steffen Kamper]

TSref: USER_INT

Property: includeLibs
Data type: list of resource /stdWrap

The rest of the element the USER element won't get any additional stdWrap functionality to avoid conflicts with existing setups, that handle the stdWrap functions within a plugin.

24051: Core - Optimize stdWrap usage for TypoScript content element PHP_SCRIPT [Closed to Steffen Kamper]

TSref: PHP_SCRIPT

Property: file
Data type: resource /stdWrap

Property: stdWrap
Data type: ->stdWrap

24052: Core - Optimize stdWrap usage for TypoScript content elements PHP_SCRIPT_INT and PHP_SCRIPT_EXT [Closed to Steffen Kamper]

TSref: PHP_SCRIPT_INT, PHP_SCRIPT_EXT

Property: file
Data type: resource /stdWrap

Property: stdWrap
Data type: ->stdWrap

24064: Core - Optimize stdWrap usage for TypoScript content element TEMPLATE [Closed to Steffen Kamper]

TSref: TEMPLATE

Property: workOnSubpart
Data type: string /stdWrap

Property: markerWrap
Data type: wrap /stdWrap

Property: substMarksSeparately
Data type: boolean /stdWrap

Property: nonCachedSubst
Data type: boolean /stdWrap

Property: stdWrap
Data type: ->stdWrap

24048: Core - Optimize stdWrap usage for TypoScript content element MULTIMEDIA [Closed to Steffen Kamper]

TSref: MULTIMEDIA

Property: width
Data type: integer /stdWrap

Property: height
Data type: integer /stdWrap

24032: Core - The content object type EDITPANEL is missing, causing pi_getEditPanel to break. []

TSref: EDITPANEL

A hidden issue. This issue "added" the cObject EDITPANEL again, which somehow got lost while refactoring tslib_content. Jeff Segars also integrated stdWrap.

Property: stdWrap
Data type: ->stdWrap

Some other properties have stdWrap (coming from typo3/sysext/feedit/view/class.tx_feedit_editpanel.php). This is at least the case since TYPO3 4.3 and was not documented. Here is a list:

Property: label
Data type: string /stdWrap

Property: innerWrap
Data type: wrap /stdWrap

Property: outerWrap
Data type: wrap /stdWrap

24090: Core - Optimize stdWrap usage for GIFBUILDER [Closed to Susanne Moog]

TSref: GIFBUILDER

Property: transparentBackground
Data type: boolean /stdWrap

Property: reduceColors
Data type: posint (1-255) /stdWrap

Property: XY
Data type: x,y +calc /stdWrap

Property: offset
Data type: x,y +calc /stdWrap

Property: workArea
Data type: x,y,w,h + calc /stdWrap

Property: maxWidth
Data type: pixels /stdWrap

Property: maxHeight
Data type: pixels /stdWrap

TEXT:
- Property: maxWidth
- Data type: pixels /stdWrap

- Property: offset
- Data type: x,y +calc /stdWrap

- Property: breakWidth
- Data type: integer /stdWrap

IMAGE:
- Property: offset
- Data type: x,y +calc /stdWrap

BOX:
- Property: dimensions
- Data type: x,y,w,h +calc /stdWrap

ELLIPSE:
- Property: dimensions
- Data type: x,y,w,h +calc /stdWrap

WORKAREA:
- Property: set
- Data type: x,y,w,h + calc /stdWrap

CROP:
- Property: crop
- Data type: x,y,w,h + calc /stdWrap

SCALE:
- Property: width
- Data type: pixels + calc /stdWrap

- Property: height
- Data type: pixels + calc /stdWrap

24089: Core - Optimize stdWrap usage for tslib_content [Closed to Susanne Moog]

TSREF, changes to tslib_content affecting different cObjects

This is the patch which was referenced in the issues of IMAGE and IMG_RESOURCE: There no new stdWrap were added with the two according RFCs (#23969 and #23970).

But: "other missing stdWrap parameters will be added by another RFC changing the behaviour of cObj->cImage."

I went through the diff and added stdWrap where it has been added.

IMAGE

Property: linkWrap
Data type: linkWrap /stdWrap

IMAGE

Property: wrap
Data type: wrap /stdWrap

imageLinkWrap

Property: sample
Data type: boolean /stdWrap

imageLinkWrap

Property: width
Data type: int (1-1000) /stdWrap

imageLinkWrap

Property: height
Data type: int (1-1000) /stdWrap

imageLinkWrap

Property: effects
Data type: see GIFBUILDER / effects. (from stdgraphics-library)

/stdWrap

imageLinkWrap

Property: alternativeTempPath
Data type: path /stdWrap

imageLinkWrap

Property: title
Data type: string /stdWrap

imageLinkWrap

Property: bodyTag
Data type: <tag> /stdWrap

imageLinkWrap

Property: wrap
Data type: wrap /stdWrap

imageLinkWrap

Property: directImageLink
Data type: boolean /stdWrap

imageLinkWrap

Property: <A>-data:target /stdWrap
Data type: target

imageLinkWrap

Property: JSwindow.newWindow
Data type: boolean /stdWrap

imageLinkWrap

Property: JSwindow.altUrl
Data type: string /stdWrap

IMAGE

Property: emptyTitleHandling
Data type: string /stdWrap

FILE

Property: emptyTitleHandling
Data type: string /stdWrap

filelink

Property: emptyTitleHandling
Data type: string /stdWrap

IMGTEXT

Property: emptyTitleHandling
Data type: string /stdWrap

filelink

Property: icon_image_ext_list
Data type: list of image extensions /stdWrap

filelink

Property: wrap
Data type: wrap /stdWrap

split

Property: cObjNum
Data type: cObjNum +optionSplit /stdWrap

split

Property: wrap
Data type: wrap +optionSplit /stdWrap

makelinks

Property: http.wrap
Data type: wrap /stdWrap

makelinks

Property: mailto.wrap
Data type: wrap /stdWrap

imgResource

Property: noScale
Data type: boolean /stdWrap

typolink

Property: wrap
Data type: wrap /stdWrap

select

Property: groupBy
Data type: SQL-groupBy /stdWrap

select

Proerty: orderBy
Data type: SQL-orderBy /stdWrap

Changes for TYPO3 4.4

20736: Core - HTML5 doctype implementation [Closed to Steffen Kamper]

Andy:

Add in config / doctype

html_5 for the HTML5 doctype.

21053: Core - Support for SSL and absolute Links [Closed to Oliver Hader]

Olly, 2010-02-22

TSref: functions/typolink, new property after "parameter"

Property: forceAbsoluteUrl
Data type: boolean
Description: Forces links to internal pages to be absolute, thus having a proper URL scheme and domain prepended.

Additional property: .scheme: Defines the URL scheme to be used (https or http, which is the default value)

Example:
typolink {
  parameter = 13
  forceAbsoluteUrl = 1
  forceAbsoluteUrl.scheme = https
}

22300: Core - Possibility to configure another link paramter for jumpurl filelinks [Closed to Benjamin Mack]

Add the following to chapter 1.5 Functions in section filelink inside the explanation of the jumpurl property inside "Extra properties":

.parameter = [string/stdWrap]

By default the jumpurl link will use the current pid and typeNum. If you need alternative values (e.g. for logging) you can specify them here. For options see typolink.parameter

22338: Core - Added marker in CONTENT object [Closed to Steffen Kamper]

Jigal

New property for CONTENT.select:

Property: markers
Data type: array of markers
Description: The markers defined in this section can be used, wrapped in the usual ###markername### way, in any other property of select.

Each value is properly escaped and quoted to prevent SQL injection problems. This provides a way to safely use external data (e.g. database fields, GET/POST parameters) in a query.

<markername>.value (value) sets the value directly.

<markername>.commaSeparatedList (bool) If set the value is interpreted as a comma separated list of values. Each value in the list is individually escaped and quoted.

(stdWrap properties ...) All stdWrap properties can be used for each markername

Example:
page.60 = CONTENT
page.60 {
  table = tt_content
  select {
    pidInList = 73
    where = header != ###whatever###
    orderBy = ###sortfield###
    markers {
      whatever.data = GP:first
      sortfield.value = sor
      sortfield.wrap = |ting
    }
  }
}

22511: Core - getBrowserInfo delivers wrong info [Closed to Steffen Kamper]

SteffenK:

Modify "Condition reference", browser:

The browser condition now delivers reliable information about the client browser. So now it's possible to make a condition for usage of Firefox, or even a webkit based browser. This is the list of known browsers:

msie, firefox, webkit, opera, netscape, konqueror, gecko, chrome, safari, seamonkey, navigator, mosaic, lynx, 
amaya, omniweb, avant, camino, flock, aol

22603: Core - Condition misses check for no logged in user [Closed to Steffen Kamper]

SteffenK:

Add to the "Condition reference", loginUser:

Additionally it is possible to match for no FE user being logged in.

Example:
This matches when no user is logged in:
[loginUser = ]

TSConfig (doc_core_tsconfig)

Changes for TYPO3 4.5

Description of setup.fields.<fieldname>.disabled

Søren Malling:

This can be used in TYPO3 4.3 and newer, but is missing in doc_core_tsconfig: You can not only set default values or override them as described above, but beginning with TYPO3 4.3 it is also possible to hide fields in the module "User tools > User Settings". Also see this Buzz Post.

New section Setup-->fields.

Property: setup.fields.<fieldname>.disabled

Data type: boolean

Description: This setting hides the option with the name <fieldname> in the module User Settings.

You can find the names of the fields in the Module "Configuration". Just browse through the "User Settings" array.

Example:

setup.fields.emailMeAtLogin.disabled = 1

With this example, we hide the "E-mail me when I login" checkbox.

You can also combine setup.fields.<fieldname>.disabled and setup.override.<fieldname>.

Example:

setup.fields.emailMeAtLogin.disabled = 1 setup.override.emailMeAtLogin = 1

Now the "Email me when i login" field is removed, but the user will still receive an email when he logs in.

Default value: 0

23433: Core - Rename "Shortcuts" to "Bookmarks" [Closed to Steffen Gebert], 23943: Core - Apply "bookmarks" naming to UserTS options [Closed to Steffen Gebert]

SteffenG:

In the descriptions the word "Shortcuts" was replaced with "Bookmarks".

In doc_core_tsconfig Section: User TSconfig Table: ->OPTIONS

Add enableBookmarks with text of enableShortcuts
Add bookmarkGroups with text of shortcutGroups
Add bookmark_onEditId_dontSetPageTree with text of shortcut_onEditId_dontSetPageTree
Add bookmark_onEditId_keepExistingExpanded with text of shortcut_onEditId_keepExistingExpanded
Add mayNotCreateEditBookmarks with text of mayNotCreateEditShortcuts
The old options with "shortcut" are depecated. They still are included with an according hint.