Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[DOCS] Add note on accessing defaults in FlexForm attributs #3612

Merged
merged 3 commits into from
Oct 26, 2023
Merged

[DOCS] Add note on accessing defaults in FlexForm attributs #3612

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6495dd8
[DOCS] Add note on accessing defaults in FlexForm attributs
garvinhicking Oct 26, 2023
9c58e02
[DOCS] Add proper link, head section, wording
garvinhicking Oct 26, 2023
4a30581
[DOCS] Proper pairing, TypoScript -> TSconfig
garvinhicking Oct 26, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions Documentation/ApiOverview/FlexForms/Index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -475,6 +475,25 @@ The key `flexform` is followed by the field which holds the FlexForm data
* :ref:`TypoScript: flexform <t3tsref:data-type-gettext-flexform>`


.. index:: pair: FlexForms; Default value
.. _default-flexforms-attribute:

Providing default values for FlexForms attributes
-------------------------------------------------

When a new content element with an attached FlexForm is created, the
default values for each FlexForm attribute is fetched from the
:xml:`<default>` XML attribute within the specification of each
FlexForm attribute. If that is missing, an empty value will be
shown in the backend (:ref:`FormEngine <FormEngine>`)
fields.

While you can use page TSconfig's :ref:`t3tsref:pageTsTcaDefaults` to
modify defaults of usual TCA-based attributes, this is not
possible on FlexForms. This is because the values are calculated
at an earlier step in the Core workflow, where FlexForm values
have not yet been extracted.

.. index:: pair: FlexForms; Fluid
.. _read-flexforms-fluid:

Expand Down
Loading