Project

General

Profile

Actions

Bug #93263

open

Creating a new page via pagetree context menu 'New' does not apply TCAdefaults

Added by Jigal van Hemert almost 4 years ago. Updated over 3 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2021-01-11
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

TSconfig has:

    TCAdefaults {
        pages {
            hidden = 1
        }
    }

If you use the context menu in the page tree to create a new page with the option 'New' it will open a new page record form which has the field hidden set to 0. The patch in #89211 applies the TSconfig before using the incoming fields, but this won't help as the value was already submitted.

Use case: no matter how you create a new page (drag'n'drop, context menu, wizard, ...) the default values for that site should be applied at first. With the 'New' context menu option the editor can change those defaults if they like


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #93793: Page cannot be hidden by default if it is not created by drag'n'dropClosed2021-03-22

Actions
Actions #1

Updated by Benni Mack over 3 years ago

  • Related to Bug #93793: Page cannot be hidden by default if it is not created by drag'n'drop added
Actions #2

Updated by Benni Mack over 3 years ago

Hey Jigal,

just a side-note as I stumbled over this problem as well recently. this is connected to this "useColumnsForDefaultValues" TCA option which takes the "neighbouring row" to use this as preset (which I find very confusing).

Actions #3

Updated by Jan Delius over 3 years ago

Benni Mack wrote in #note-2:

Hey Jigal,

just a side-note as I stumbled over this problem as well recently. this is connected to this "useColumnsForDefaultValues" TCA option which takes the "neighbouring row" to use this as preset (which I find very confusing).

This is very confusing, especially when it reacts differently via drag'n'drop.

Actions #4

Updated by Benni Mack over 3 years ago

Jan Delius wrote in #note-3:

Benni Mack wrote in #note-2:

Hey Jigal,

just a side-note as I stumbled over this problem as well recently. this is connected to this "useColumnsForDefaultValues" TCA option which takes the "neighbouring row" to use this as preset (which I find very confusing).

This is very confusing, especially when it reacts differently via drag'n'drop.

I agree, but as you can imagine this wasn't my idea either ;) This side-effect / feature goes back to TYPO3 4.2 (introduction with IRRE). Very tiresome to find these things and then takes a lot of time to fix it properly.

Actions

Also available in: Atom PDF