Consider using the administration theme when editing or creating content by default

Created on 9 March 2023, almost 2 years ago
Updated 17 March 2023, almost 2 years ago

Problem/Motivation

Unless you're using the Standard profile, the default value of the Use the administration theme when editing or creating content option on the Appearance page is false, which means that node forms are rendered using the frontend theme. I feel like since the progress in the Admin UI and JavaScript Modernisation Initiative, the Claro theme set as default admin theme and the rise in popularity of Gin theme โ†’ this is no longer a sensible default. Maybe I'm biased since I have never had to integrate admin forms with custom frontend themes, but is this still a thing nowadays?

Steps to reproduce

Set up a fresh Drupal installation with the Minimal install profile and visit the Appearance admin page. The option is turned off.

Proposed resolution

Turn on the Use the administration theme when editing or creating content by default for new installations.

Remaining tasks

Do it.

User interface changes

Node forms will be rendered in the admin theme by default.

๐Ÿ“Œ Task
Status

Needs work

Version

10.1 โœจ

Component
Node systemย  โ†’

Last updated 4 days ago

No maintainer
Created by

๐Ÿ‡ง๐Ÿ‡ชBelgium dieterholvoet Brussels

Live updates comments and jobs are added and updated live.
  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Comments & Activities

  • Issue created by @dieterholvoet
  • @dieterholvoet opened merge request.
  • Status changed to Needs review almost 2 years ago
  • ๐Ÿ‡ง๐Ÿ‡ชBelgium dieterholvoet Brussels
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

    Tagging for framework manager for their thoughts.

    Personally I would not like to see this happen as I think this goes against the work done for claro.

  • ๐Ÿ‡ง๐Ÿ‡ชBelgium dieterholvoet Brussels

    Personally I would not like to see this happen as I think this goes against the work done for claro.

    How so? Changing this would make it so Claro is used in even more situations, right?

  • Status changed to RTBC almost 2 years ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

    Having a terrible case of the Mondays and no coffee. You are correct, some reason I read it as using the front end theme by default.

    That's my mistake. Will mark it and see what the committer says.

  • ๐Ÿ‡ญ๐Ÿ‡บHungary Gรกbor Hojtsy Hungary

    I think Drupal may have been a system where using the frontend theme was the sensible default, but its used for more ambitious projects now and using the admin theme by default fits with that better. (Content types are more complex and usually other admin tasks are involved in creating the content, such as category management or media management).

  • Status changed to Needs review almost 2 years ago
  • ๐Ÿ‡ซ๐Ÿ‡ฎFinland lauriii Finland

    I don't think this actually needs a framework manager review so removing the tag.

    Something we still need to do is to go through tests where $this->config('node.settings')->set('use_admin_theme', '1') is being called to make sure that we are not changing any tests to not test what they are supposed to test.

  • ๐Ÿ‡ฌ๐Ÿ‡งUnited Kingdom alexpott ๐Ÿ‡ช๐Ÿ‡บ๐ŸŒ

    Yeah it'd be good to know if we have explicit test coverage around this setting. Plus we'll need a CR to announce the change to people.

    +1 for the change.

  • Status changed to Needs work almost 2 years ago
  • ๐Ÿ‡บ๐Ÿ‡ธUnited States smustgrave

    Searching for

    ->config('node.settings')->set('use_admin_theme',

    There are 4 instances and 3 I believe can be removed.

    ConfigurableLanguageManagerTest
    AddedStylesheetsTest
    ShortcutLinksTest

    As far as a dedicated test where would that go?

Production build 0.71.5 2024