Issue Bug Closed

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

Jigal van Hemert 01/11/21, 14:47 updated 10/02/26, 19:53

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

Reviews 0

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

History 5

  1. Benni Mack changed Related to #93793 04/24/21, 19:32

  2. Benni Mack commented 04/29/21, 18:23

    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).

  3. Jan Delius commented 05/19/21, 11:47

    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.

  4. Benni Mack commented 05/19/21, 11:49

    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.

  5. Georg Ringer commented and changed status New Closed 10/02/26, 19:53

    just tested this on main

    TCAdefaults {
    pages {
        subtitle = test
          }
    }

    and that works fine. therefore closing issue