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 renderMode is default]]>
"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.]]>
1]]>
1 and renderMode is default]]>
1]]>
1 and renderMode is default]]>
1]]>
1 and renderMode is default]]>
1]]>
1 and renderMode is default]]>
function notation of UserFunc to be called, example "Tx_Myext_Configuration_FlexForms_MyField->renderField" - Extbase classes need autoload registry for this]]>
... section of
the output FlexForm.]]>
]]>