en	Flux Providers

en	Available page layouts/templates (empty selection means allow-all)

en	Available content types (empty selection means allow-all)

en	Debug Mode: Display debug information about every Flux template being rendered and every ConfigurationProvider being used. Value "0" (production) means debug messages are disabled and Exceptions may be suppressed. Value "1" (development) means every debug message is displayed. Value "2" (staging, testing) means only severe errors' messages are displayed.

en	Error handling: If enabled, all Flux controllers are permitted to handle their own errors in ways that are far more flexible than traditional error catching. Enable with care - if your plugin, content or page template collection does not contain an Error.html template, your site may risk breaking with an extremely basic and not very informative error á la "Template not found for action foobar" but when enabled and combined with proper error templates you can customise pretty much any error which might happen anywhere when a Flux controller subclass is in play. Best turned off on development sites unless you are developing exactly error templates as it greatly limits debug output!

en	Automatic initialisation: If enabled, Flux will automatically create the TypoScript setup that is required to render Flux templates in the frontend, and will use it on every page. Unchecking this option instead registers a static TypoScript file which can be loaded as needed.

en	Plug-and-play templates: If enabled, Flux will automatically create a template directory structure under your project folder (public folder) into which you can place Content and Page templates which are then automatically integrated as page- and content types.

en	Plug-and-play templates directory: The directory name of plug-and-play templates, automatically created under the project folder ("public" directory). You can change this value to use a different directory name, but it will still be created under the "public" directory. Only relative paths are allowed - note that attempting to use "../" will not work as it causes the path to be sanitised and removed by TYPO3 itself.

en	Doktypes: CSV list of doktypes to add the page layout selectors to in addition to the default standard pages and shortcuts (0,1,4). Possible use cases are sysfolders (254) or custom page types.

en	Translation: Enable translation of Page Configuration through the Pages Language Overlays.

en	Flux-based Content Type

en	Extension identity (Vendor.ExtensionName format, should be your own extension). Determines where a partial and layout template files are resolved, and where a controller class may potentially be found.

en	Icon file or icon name (if custom icon name you must manually register the icon in TYPO3)

en	Content type name, must be a value using only a-z and 0-9, but never starting with a number, and must use signature of extension you put in "extension identity" as prefix, e.g. extension "MyVendor.MySpecialExt" means prefix must be "myspecialext_".

en	Content type configuration options

en	Grid configuration options

en	Template file - if you use this, it overrides "template source" below. If you also enter a source it is available as {contentType.templateSource} in your own template. Use EXT:... file reference format.

en	Template source

en	Content type validation

en	Flux template source (copy-paste to template file rendered by Flux)

en	Sheet name (a-z, 0-9 and _)

en	Sheet label (any characters you need)

en	Add fields or modify fields that appear in this sheet when editors edit the content type. The properties of fields follow TCA standards with a few exceptions. If you need it, there is documentation about this API on https://viewhelpers.fluidtypo3.org/fluidtypo3/flux/ - which although it is for the ViewHelper API of Flux also documents the attributes used here.

en	Context

en	Form Fields

en	Grid

en	Fluid Template

en	Export Template

en	Field name (a-z, 0-9, _ and .)

en	Label, can be LLL:EXT: reference or LLL:keyname which resolves the label in the content type's extension context, file locallang.xlf

en	Data type transformation, enter for example "array" to cast CSV values to array. See Flux documentation about possible values.

en	Field can be cleared (add "clear" checkbox wizard beside field)

en	Default value

en	Default state

en	Input

en	Text

en	Checkbox

en	Radio

en	DateTime

en	Select

en	Items (CSV)

en	Relation

en	Size of fields (number of possible entries)

en	Minimum number of items that can be selected

en	Maximum number of items that can be selected

en	Allow multiple selections of the same value/record

en	Add an empty option before as first option

en	Field name on foreign table that contains UID of origin record. Empty means only one item can be related and UID is stored in origin record.

en	MultiRelation

en	Inline

en	File

en	Function

en	User function reference, e.g. MyClass->myFunction. Class must be registered with autoloader to be usable.

en	Columns in parent

en	Flux content
de	Flux-Inhalt

en	Options
de	Option(en)

en	Content-type options

en	Clear value
de	Wert leeren

en	Standard pipe (no action)
de	Standard-Pipe (keine Aktion)

en	Controller action pipe
de	Controller-Action-Pipe

en	Email sending pipe
de	E-Mail-Versand-Pipe

en	FlashMessage dispatch pipe
de	FlashMessage-Weiterleitungs-Pipe

en	Extbase TypeConverter pipe
de	Extbase-TypeConverter-Pipe

en	Reference to content on page '%s' - click to jump to original
de	Referenz auf den Inhalt von Seite '%s' - Anklicken um zum Original zu springen.

en	No fields found in form
de	Keine Felder im Formular gefunden

en	No form selected/configured (enabling Flux debug will produce more information)
de	Kein Formular ausgewählt/konfiguriert (Mehr Informationen mit aktiviertem Flux-Debug)

en	No FlexForm source selected. This is usually caused by incorrect template paths being returned by a ConfigurationProvider - in the case of FED/FluidContent/FluidPages this can also be caused by not having selected a page template or Fluid content element type, which can be considered a safe "error" that is only reported because debug mode is enabled in Flux. The parameters which lead to this error were:
de	Keine FlexForm-Quelle ausgewählt. Grund sind üblicherweise nicht-korrekte Template-Pfade aus einem ConfigurationProvider. Im Fall von FED/FluidContent/FluidPages kann dies auch hervorgerufen werden wenn kein Seitenmplate oder Fluid-Content Elementen-Typ ausgewählt wurde. Die kann sicher als sicherer "Fehler" betrachtet werden, da er nur bei aktiviertem Debug-Mode in Flux ausgegeben wird. Folgender Parameter führte zu diesem Fehler:

en	flux.this_table_does_not_exist.fields.input

en	flux.this_table_does_not_exist

en	Insert new content element in this position
de	Neues Inhaltselement an dieser Stelle einfügen

en	Paste in this position
de	An dieser Stelle einfügen

en	Paste as reference in this position
de	An dieser Stelle als Referenz einfügen

en	Show or hide the grid

en	Columns from selected "Page Layout"

en	Page Layout - this page

en	Parent decides

en	Page Layout - subpages

en	Page Configuration

en	Page Configuration - subpages

en	Package

en	Page Layouts

en	Page Configuration

en	Raw Fluid template

en	Template file reference

en	EXT:... or site-relative path

en	Layout to use for rendering

en	Fluid Content Area

en	Columns from selected "Page Layout"