Issue Bug Closed

#108608"Create an additional TypoScript record" button missing

Christian Weiske 01/09/26, 12:45 updated 01/15/26, 09:30

Description

I’m on “Site Management” > “TypoScript” > Edit TypoScript Record pages with TypoScript generated from site set includes, the “Additional TypoScript record” area with the “Create an additional TypoScript record” is missing (Screenshot 1).

Pages without a site set typoscript still have the buttons to create a root or extension typoscript record (Screenshot 2).

This makes it hard to create a root-level extension typoscript record.

Happens with TYPO3 13.4.22

Reviews 0

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

Files 2

History 5

  1. Georg Ringer commented and changed status New Needs Feedback <span data-processor="relativetime" data-value="2026-01-09T13:34:31+00:00" > 01/09/26, 13:34 </span>

    thanks for creating the issue! IMHO it is a bit different.
    the button to create a new TS record is only shown if the current page does not have any sys_template record and it is not related to using site sets or not.

    My test setup:
    2 root pages, one with a set, one with a root sys_template record. None shows the the button but as soon as I am on a subpage of either of those, the button is shown.

    => IMHO this fine as it is as on the root page it should not be promoted to generate an sys_template record.

    what do you think?

  2. Christian Weiske commented <span data-processor="relativetime" data-value="2026-01-09T13:49:34+00:00" > 01/09/26, 13:49 </span>

    When not using site sets, I had to define a root TS record in database. This record could easily be edited when needed, e.g. to quickly add google search console site verification.

    Now with site sets, there is no root TS record anymore that I can modify. To quickly try something, I have to create a TS extension template in the root page, making the button necessary.

  3. Garvin Hicking commented <span data-processor="relativetime" data-value="2026-01-15T06:16:22+00:00" > 01/15/26, 06:16 </span>

    I would tend to closing the issue with Georgs feedback plus: It is intentional that we do not want to mix site sets and DB records. The reason is that site sets are built to be the source of truth, and binding. Thats why it has strong defaults ans validation. It does not fit into a concept of having another kind of storage. If you need that, you can create nested site sets and dependencies to your base site set, this would be the current concept.

    Is it ok with you to close the issue because of this?

  4. Garvin Hicking commented and changed status Needs Feedback Closed <span data-processor="relativetime" data-value="2026-01-15T09:30:48+00:00" > 01/15/26, 09:30 </span>

    Thanks! :)