Feature #87117

open

FormEngine: disable/hide not used/necessary form elements fields automatically based on site configuration

Added by Josef Glatz almost 6 years ago. Updated over 4 years ago.

Status:

Accepted

Priority:

Could have

Assignee:

Category:

Site Handling, Site Sets & Routing

Target version:

Start date:

2018-12-10

Due date:

% Done:

Estimated time:

PHP Version:

Tags:

Complexity:

Sprint Focus:

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.

Actions

Copy link

Updated by Josef Glatz almost 6 years ago

Tracker changed from Feature to Task
TYPO3 Version set to 9

Actions

Copy link

Updated by Josef Glatz almost 6 years ago

Priority changed from Should have to Could have

Actions

Copy link

Updated by Josef Glatz almost 6 years ago

Description updated (diff)

Actions

Copy link

Updated by Josef Glatz almost 6 years ago

Subject changed from FormEngine: disable/hide localization/translation/language specific form elements automatically if only one language is set in the site configuration of the actual site configuration to FormEngine: disable/hide not used/necessary form elements fields automatically based on site configuration

Actions

Copy link

Updated by Georg Ringer almost 6 years ago

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.

Actions

Copy link

Updated by Josef Glatz almost 6 years ago

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

Actions

Copy link