->SETUPΒΆ

Default values and overriding values for the "User tools > User settings" module.

Note

The "User tools > User settings" module only represents a subset of the options from the table below.

Default values and overriding values for the "User tools > User settings" module

Default values are set by 'setup.default' while overriding values are set by 'setup.override'. Overriding values will be impossible for the user to change himself and no matter what the current value is, the overriding value will overrule it. The default values are used for new users or if the setup is re-initialized.

Note

If you have first set a value (by override e.g.) and then remove that value from being set, the value is not restored to the original default but is kept at the current value! Therefore setting a value and later removing that value would require the users preferences to be reset (you can do that from the Install Tool > Database Analyser > Reset user preferences) OR better, don't remove the value, just change the value of it! (e.g. to a blank string if you wish to "reset" the value).

This table shows the keys for both defaults and override values:

Property

thumbnailsByDefault

Data type

boolean

Description

Show Thumbnails by default

Property

emailMeAtLogin

Data type

boolean

Description

Notify me by email, when somebody logs in from my account

Property

startInTaskCenter

Data type

boolean

Description

If set, then the backend will start up in the task center (task center should be enabled for the user).

This is an old property. Rather look at startModule below instead, as it provides more flexibility.

Property

helpText

Data type

boolean

Description

Show help text when applicable

Property

titleLen

Data type

positive integer

Description

Max. Title Length

Property

edit_wideDocument

Data type

boolean

Description

Wide document background

Property

edit_RTE

Data type

boolean

Description

Enable Rich Text Editor

Property

edit_docModuleUpload

Data type

boolean

Description

File upload directly in Doc. module

Property

edit_showFieldHelp

Data type

string

Description

Keywords: "" (empty string), "icon" or "text"

Determines the type of help text mode for TCA form fields.

Property

lang

Data type

language-key

Description

One of the language-keys. For current options see typo3/sysext/core/Classes/Localization/Locales.php. E.g. "dk", "de", "es" etc.

Property

copyLevels

Data type

positive integer

Description

Recursive Copy: Enter the number of page sub-levels to include, when a page is copied

Property

recursiveDelete

Data type

boolean

Description

Recursive Delete(!): Allow ALL subpages to be deleted when deleting a page

Property

allSaveFunctions

Data type

boolean

Description

Display all save functions in Doc-module menu

Property

neverHideAtCopy

Data type

boolean

Description

If set, then the hideAtCopy feature for records in TCE will not be used.

Property

startModule

Data type

string

Description

Name of the module that is called when the user logs into the Backend

Property

noMenuMode

Data type

boolean / string

Description

If set, the backend will not load the left menu frame but rather put a selector-box menu in the top frame. This saves a lot of space on small screens. Also icons will not be displayed in the clickmenu panel in the top.

Value "icons":

Setting noMenuMode to "icons" will still remove the menu, but instead of the selector box menu you will have the whole clickmenu panel as a menu with the icons only as the hidden state of the clickmenu panel. This is extremely nice (in my opinion) for experienced users who know the icons of the modules.

Property

hideSubmoduleIcons

Data type

boolean

Description

If set then submodule icons will not be shown in the left menu of the backend.

Property

dontShowPalettesOnFocusInAB

Data type

boolean

Description

If set, palettes are not activated in the TCEFORMs when focus is moved to a field.

Property

disableCMlayers

Data type

boolean

Description

Disable the context menu layers in the backend.

Property

disableTabInTextarea

Data type

boolean

Description

If you are using IE or Mozilla, TYPO3 will load a little JavaScript file that makes it possible to use the <tab> key in textareas. If you don't like the feature for some reason, you can disable it here.

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

positive integer

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

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

Property

default.tx_form.showWizardByDefault

Data type

boolean

Description

Enables the forms wizard of EXT:form. If set to 0 only predefined forms will be selectable by the editor.

Default

1

[beuser:setup.default/setup.override]

Do not use any other properties than the ones listed in the table above.

On top of being able to set default values or override them as described above, it is also possible to hide fields in the module "User tools > User Settings".

The table below describes the related option:

Property

<field name>.disabled

Data type

boolean

Description

This setting hides the option with the name <field name> 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.<field name>.disabled and setup.override.<field name>.

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

0

[beuser:setup.fields]