#87117FormEngine: disable/hide not used/necessary form elements fields automatically based on site configuration
Description
Problem/Description
Would it make sense
- to hide all language/localization/translation specific formEngine fields
- in the backend
- if only one language is defined within the site configuration for the actual pagetree
?
—-
Benefits
From a UX perspective, this could be a real benefit. The TYPO3 integrator override this functionality for example via TsConfig or a siteConfiguration setting. Actually it was not really possible to hide those specific fields, as these are necessary even if you have only 1 language.
—-
What to do with records which don’t have a correct language
We can show them in the page module in a different area for example: “These records have a language set whicih is not configured in this page tree”
Same goes for the list view module.
Reviews 0
No change resolves or names this issue in its commit message, and no comment links one.
History 9
-
Josef Glatz changed tracker
FeatureTask TYPO3 Version 9 <span data-processor="relativetime" data-value="2018-12-10T12:20:34+00:00" > 12/10/18, 12:20 </span> -
Josef Glatz changed priority
Should haveCould have <span data-processor="relativetime" data-value="2018-12-10T12:20:41+00:00" > 12/10/18, 12:20 </span> -
Josef Glatz changed description <span data-processor="relativetime" data-value="2018-12-11T08:21:41+00:00" > 12/11/18, 08:21 </span>
-
Josef Glatz changed subject
FormEngine: disable/hide localization/translation/language specific form elements automatically if only one language is set in the site configuration of the actual site configurationFormEngine: disable/hide not used/necessary form elements fields automatically based on site configuration <span data-processor="relativetime" data-value="2018-12-11T08:27:00+00:00" > 12/11/18, 08:27 </span> -
Josef Glatz commented <span data-processor="relativetime" data-value="2018-12-12T23:08:31+00:00" > 12/12/18, 23:08 </span>
Georg Ringer wrote:
> the only drawback I see is that it will also remove the “all language” selection. a possible use case could be that someone wants to create content for a site which will get more languages in the future.Therefore such feature should be possible to deactivate via TSConfig or any equivalent stuff
-
Josef Glatz changed tracker
TaskFeature <span data-processor="relativetime" data-value="2018-12-12T23:08:45+00:00" > 12/12/18, 23:08 </span> -
Georg Ringer changed status
NewAccepted <span data-processor="relativetime" data-value="2020-03-02T16:40:26+00:00" > 03/02/20, 16:40 </span> -
Georg Ringer commented and changed status
AcceptedClosed <span data-processor="relativetime" data-value="2026-11-14T20:12:37+00:00" > 11/14/26, 20:12 </span>This has been implemented in v14.2 with #109366 “Hide form fields with no selectable items”: fields of
type=languageare no longer rendered in FormEngine if only a single language is configured for the site. The special “All languages” item (-1) is not counted as a choice, so the field is hidden for sites with only one real language and shows up again as soon as a further language is added.For regular backend users the field is removed completely. With backend debug mode enabled, it is kept as read-only with an info badge so that administrators can still see it. Integrators can opt out per field with the TCA option
showIfEmpty.The proposal to list records with a no longer configured language in a dedicated area of the page and list module is not part of this change. Please open a separate issue if you want to follow up on it.
Closing this one as resolved. Thanks again!
the only drawback I see is that it will also remove the “all language” selection. a possible use case could be that someone wants to create content for a site which will get more languages in the future.