#109743Field visible
Description
A wonderful new feature is the toggler to hide fields temporary by using the Field visible-toggler. The toggler shows up in be-editor for static Text and Content Elements but does not work on summary-Page and emails – form-elements are always visible. At least in the yaml-definition and in the partials I could not find something that points to the cause of the problem.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 9
-
Garvin Hicking changed status
NewNeeds Feedback <span data-processor="relativetime" data-value="2026-05-04T08:32:49+00:00" > 05/04/26, 08:32 </span> -
wini2 no-lastname-given commented <span data-processor="relativetime" data-value="2026-05-04T12:26:57+00:00" > 05/04/26, 12:26 </span>
Hi,
sorry, I forgot to share my config.yaml part.StaticText: formEditor: editors: 580: identifier: customContainerClass templateName: Inspector-TextEditor label: 'Klasse[n] um äußeres div' propertyPath: renderingOptions.customContainerClass ... # ausgabe in summary und e-mail variants: - identifier: hide-1 renderingOptions: enabled: true condition: 'stepType == "SummaryPage" || finisherIdentifier in ["EmailToSender", "EmailToReceiver"]'similar for ContentElement.
On the regular form the elements are hidden if ‘Field visible’-toggler is unchecked (as wanted) but show up on summary and in emails.
In summary and email I only made some conditions with
<f:if condition="{0: formValue.element.type} {0: 'StaticText'}"> ... and <br><f:if condition="{formValue.element.type} 'ContentElement'"><br>…<br><f:cobject typoscriptobjectpath="lib.tx_form.contentElementRendering">{formValue.element.properties.contentElementUid}</f:cobject>…<br>for ce</f:if></f:if>in order to style them a little bit. Works fine and is surely not the cause why the ‘Field visible’-toggler does not work.
-
Josua Vogel commented <span data-processor="relativetime" data-value="2026-05-05T07:44:23+00:00" > 05/05/26, 07:44 </span>
Hi @wini2 ,
thanks for sharing this.
In my opinion there is no bug.You have explicitly defined a variant that ensures the element is enabled on the summary page and in the finishers. This overrides the behavior set in the UI (the Form Editor). Variants cannot currently be managed via the UI.
Looking at your code snippets, everything works as expected.
Fields are hidden in the form and always displayed in the defined cases due to the variant. -
wini2 no-lastname-given commented <span data-processor="relativetime" data-value="2026-05-05T11:56:36+00:00" > 05/05/26, 11:56 </span>
Thanks for your explanation. If it’s not a bug, do you have any suggestions on how to query the state of the “Field visible toggle” in a condition or in the YAML file to align the behavior in the summary and email with that of the form?
Thanks in advance
-
Josua Vogel commented <span data-processor="relativetime" data-value="2026-05-05T16:09:30+00:00" > 05/05/26, 16:09 </span>
I didn´t tried it, but maybe you can change the condition and use “&& renderable.isEnabled()” (https://docs.typo3.org/permalink/typo3-cms-form:concepts-variants-conditions-renderable)
-
wini2 no-lastname-given commented <span data-processor="relativetime" data-value="2026-05-05T21:02:27+00:00" > 05/05/26, 21:02 </span>
@josuavogel I could not make it with traverse (maybe caused by my inability) but I found out that
<f:if condition="{0: formValue.element.type} == {0: 'StaticText'} && <strong>{element.renderingOptions.enabled}</strong> "> <br>does the trick. No need for changing the code</f:if>variants: - identifier: hide-1 renderingOptions: enabled: true condition: 'stepType == "SummaryPage" || finisherIdentifier in ["EmailToSender", "EmailToReceiver"]'Perhaps equally helpful if it should be simpler is to show up in the form editor as a memory aid or as a hint for editors and to avoid irritation from inconsistent behavior towards other field type.
StaticText: formEditor: editors: 240: identifier: enabled fieldExplanationText: 'Does not work on emails and summary'It’s regrettable that this useful feature has not yet been consistently implemented.
-
Josua Vogel commented <span data-processor="relativetime" data-value="2026-05-06T06:34:36+00:00" > 05/06/26, 06:34 </span>
Okay, great that you found a solution. :)
yeah, I know that the current state is not the best one. You can enable / disable many fields but with variants it’s tricky.
We are missing the UI for variants, but this is a huge task. It‘s on my todo list, but will take a lot of (free)time. :)We can close this ticket.
-
Garvin Hicking changed status
Needs FeedbackClosed <span data-processor="relativetime" data-value="2026-05-06T06:40:30+00:00" > 05/06/26, 06:40 </span>
Hi @wini2 ,
Am I correct in understanding that your expectation is this: StaticText and ContentElement will be displayed on the summary page if the elements are set to visible?
Currently, they are never displayed on the summary page (or in finishers).