Issue Feature New Stale

#110411Hide in default - for content elements

Andreas Kießling 08/10/26, 16:01 updated 08/10/26, 16:01

Description

There are various issues with copying content from a page / language in connected mode to a page / language in free mode, e.g. #109624 #90610
One translation loophole was closed in v14 with invoking the translation dialogue when translating an element, but copy/pasting is still a problematic action.

In one of my projects we accidentally ended up with quite some pages in mixed mode and they are very hard to debug and clean up.
Maybe the technical aspects were not clear to the users and initially the frontend looked right, thus the errors only showed up later as work on the content started again and content was moved around.

My proposal is: we should provide a way to make Free Mode for content an exception or an explicit choice when a page/translation is set up as you can not easily revert your decision later. Converting a connected / mixed language to free may work, but the other way around is a nightmare when container elements etc. are involved.

Pages can already be configured to be hidden in default, only translations show up. Thus it would be great to have a similar feature also for content.
—> All content can / must be created in default and localized / translated as needed, so the usage of Free Mode can hopefully be limited to a very few exceptions, e.g. pages that have totally different content or only have content in sys_language_uid > 0

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

Fix this issue

Start the commit message of your patch with this. Add what the patch does, and the versions it goes to in "Releases:". How to create a patch

Commit message
[FEATURE] Hide in default - for content elements Resolves: #110411 Releases: main