Flux Providers Available page layouts/templates (empty selection means allow-all) Available content types (empty selection means allow-all) 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. 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! 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. 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. 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. 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. Page Integration: If enabled, Flux will integrate with pages to make templates you place in the "Pages" template folder selectable in page properties (the features previously provided by the "Fluidpages" extension). You must flush system caches after changing this option! EXPERIMENTAL - FlexForm-to-IRRE: FlexForm XML to IRRE storage. WARNING - destroys existing FlexForm data in DB when saving records! Enabling this option makes Flux capable of storing FlexForm XML data structures as normalized IRRE records. By using the DataAccessTrait, classes such as controllers can read out the data in an array structure compatible with vanilla FlexForm data. Flux-based Content Type 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. Icon file or icon name (if custom icon name you must manually register the icon in TYPO3) 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_". Content type configuration options Grid configuration options 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. Template source Content type validation Flux template source (copy-paste to template file rendered by Flux) Sheet name (a-z, 0-9 and _) Sheet label (any characters you need) 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. Context Form Fields Grid Fluid Template Export Template Field name (a-z, 0-9, _ and .) Label, can be LLL:EXT: reference or LLL:keyname which resolves the label in the content type's extension context, file locallang.xlf Data type transformation, enter for example "array" to cast CSV values to array. See Flux documentation about possible values. Field can be cleared (add "clear" checkbox wizard beside field) Default value Default state Input Text Checkbox Radio DateTime Select Items (CSV) Relation Size of fields (number of possible entries) Minimum number of items that can be selected Maximum number of items that can be selected Allow multiple selections of the same value/record Add an empty option before as first option 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. MultiRelation Inline File Function User function reference, e.g. MyClass->myFunction. Class must be registered with autoloader to be usable. Columns in parent Flux content Options Content-type options Clear value Reference to content on page '%s' - click to jump to original No fields found in form No form selected/configured (enabling Flux debug will produce more information) 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: flux.this_table_does_not_exist.fields.input flux.this_table_does_not_exist Insert new content element in this position Paste in this position Paste as reference in this position Show or hide the grid Columns from selected "Page Layout" Page Layout - this page Parent decides Page Layout - subpages Page Configuration Page Configuration - subpages Package Page Layouts Page Configuration Raw Fluid template Template file reference EXT:... or site-relative path Layout to use for rendering Fluid Content Area Columns from selected "Page Layout"