{element}
/]]>
` that shall
be rendered.
### Example: Render all child elements of one grid column
`fluidcontent` element with one column of child elements:
/]]>
action1,action3,action4 with LLL values based on "action1"
ControllerName->action2 with LLL values based on "action2"
By default Flux will create one option per action when reading
Controller actions - using "subActions" it becomes possible to add
additional actions to the list of allowed actions that the option
will contain, as opposed to having only one action per option.
And there are a few ways to limit the options that are displayed:
- You can use "excludeActions" to specify an array in the same
syntax used by the "actions" argument, these are then excluded.
- You can specifiy the "controllerName" argument in which case
only actions from that Controller are displayed.
And there are a couple of ways to define/resolve labels for actions:
- You can add an LLL label in your locallang_db file:
lowercasepluginname.lowercasecontrollername.actionfunctionname
example index: myext.articlecontroller.show
- You can do nothing, in which case the very first line of
the PHP doc-comment of each action method is used. This value can
even be an LLL:file reference (in case you don't want to use the
pattern above - but beware this is somewhat expensive processing)
- Or you can do nothing at all, not even add a doc comment, in which
case the Controller->action syntax is used instead.
Marking actions that have required arguments (which cause errors if
rendered on a page that is accessible through a traditional menu) is
possible but is deactivated for LLL labels; if you use LLL labels
and your action requires an argument, be user friendly and note so
in the LLL label or docs as applies.
Lastly, you can set a custom name for the field in which case the
value does not trigger the Extbase SwitchableControllerActions feature
but instead works as any other Flux FlexForm field would.
To use the field just place it in your Flux form (but in almost all
cases leave out the "name" argument which is required on all other
field types at the time of writing this). Where the field is placed
is not important; the order and the sheet location don't matter.
/]]>
1]]>
1 and renderType is SelectSingle]]>
"csv,of,actions" which are allowed. If used, does not require the use of an ExtensionName and PluginName (will use the one specified in your current plugin automatically)]]>
"csv,of,actions" which must be excluded]]>
action syntax]]>
list is selected, ControllerName->update and ControllerName->delete are allowed - but ' .
'cannot be selected).]]>
action values, defaults to "->". Empty values result in default being used.]]>
Then use `` to render the image in the frontend:
`alt` and `title` tags are not loaded from the file's meta data record.
Use `` if you want this feature.
/]]>
1]]>
1 and renderType is SelectSingle]]>
1]]>
1 and renderType is SelectSingle]]>
value pairs that must match in the relation table]]>
v:iterator.first()
-> v:variable.set(name: 'settings.files')}
And now the example how to get the first file reference from a fluidpages template, for the flux field
named "settings.files":
{v:page.resources.fal(field: 'settings.files')
-> v:iterator.first()
-> v:variable.set(name: 'settings.files')}
### Usage warning
Due to [TYPO3 core bug #71239](https://forge.typo3.org/issues/71239), using
FAL references within sections (``) in content elements
or within the page configuration does not work.
When choosing a file in one section element, you will see it in all sections.
When choosing a file in a page configuration, it will be visible in the subpages
configuration, too.
This issue will most likely not be fixed before TYPO3 8, so do not use it.
Alternatively, you could use ``.
### Selecting and rendering an image
#### Selecting a single image
#### Define crop variants
The crop configuration can now be passed to the image viewhelper:
#### Rendering the image
{v:content.resources.fal(field: 'settings.image') -> v:iterator.first() -> v:variable.set(name: 'image')}
#### Rendering multiple images
/]]>
1]]>
1 and renderType is SelectSingle]]>
value pairs that must match in the relation table]]>
### Example: Content element selector with autocomplete
Add a wizard to search for content elements, instead of opening a popup:
/]]>
1]]>
1 and renderType is SelectSingle]]>
value pairs that must match in the relation table]]>
1]]>
1 and renderType is SelectSingle]]>
A list of allowed markers for the `condition` can be found in the documentation at:
https://docs.typo3.org/typo3cms/TCAReference/ColumnsConfig/Type/Select.html#foreign-table-where
/]]>
1]]>
1 and renderType is SelectSingle]]>
value pairs that must match in the relation table]]>
### Items with labels
If you want to display labels that are different than the values itself,
use an object in `items`:
You can translate those labels by putting a LLL reference in the first property:
LLL:EXT:extname/Resources/Private/Language/locallang.xlf:flux.example.fields.items.foo'
### Links
* [TCA Reference: type "select"](https://docs.typo3.org/typo3cms/TCAReference/stable/Reference/Columns/Select/)
/]]>
1]]>
1 and renderType is SelectSingle]]>
1]]>
1 and renderType is SelectSingle]]>
value pairs that must match in the relation table]]>
1]]>
1 and renderType is SelectSingle]]>
value pairs that must match in the relation table]]>
renderField". Ignored on TYPO3 9.5 and above - use renderType instead.]]>
#### Accessing values of grouped elements
Name: {settings.name.firstname} {settings.name.lastname}
/]]>
/]]>
### Example: Check if page is accessible before loading data
Data of disabled and deleted pages cannot be loaded with flux:form.data
and lead to an TYPO3FluidFluidCoreViewHelperException.
To prevent this exception, check if the page is accessible by generating
a link to it:
...
/]]>
`
renders a field that's not user editable which contains
a unique colPos value for each section object.
The colPos field is then associated with the section
object _and will not change even if the section object
is moved up or down in the section_.
This property can then be used in ``
arguments if the grid columns are created by iterating
the section objects and creating a column for each.
Example
-------
Notes
-----
Please be aware that dynamic grid is NOT compatible
with the "static" option for `` - this
option must not be enabled; if it is, the grid will
not be rendered.
/]]>
/]]>
(which is the same as:)
unrestricted
Or:
(which is the same as:)
restricted
/]]>
#### Reading section element values
Number #{id}:
mobile, {obj.landline.number}
landline, {obj.mobile.number}
/]]>
` with nested `` tags
to define a tabular layout.
The grid is then rendered automatically in the preview section
of the content element, or as page columns if used in page templates.
For frontend rendering, use `flux:content.render`.
### Define Page and Content elements
Name is used to identify columns and fetch e.g. translations from XLF files.
#### Rendering
/]]>
` tags.
Use the `colPos` attribute for grids in page and content elements.
See `` for an example.
### Limit allowed elements
It is possible to limit the elements allowed in the column by setting
the `allowedContentTypes` variable:
The value is a comma-separated list of content type IDs; they can be found
in `tt_content.CType` column.
### Limit allowed fluid content elements
It is also possible to limit the allowed fluid content elements:
/]]>
`]]>
` tags.
Usually contains `` tags.
See `` for an example.
/]]>
assign('variable', 'value of my variable');
$view->assign('code', 'My variable: {variable}');
And in the template:
{code -> flux:inline()}
Which outputs:
My variable: value of my variable
You can use this to pass smaller and dynamic pieces of Fluid code
to templates, as an alternative to creating new partial templates.
/]]>