Problem/Motivation

This is found when working on deprecating Claro. Adding to the Admin theme component so the maintainers are aware of this.

Steps to reproduce

Proposed resolution

Change \Drupal\system\Theme\DbUpdateNegotiator::determineActiveTheme to return 'default admin'

Remaining tasks

User interface changes

After

Introduced terminology

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#3 Two.png41.86 KBquietone
#3 One.png119.05 KBquietone

Issue fork drupal-3622756

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

quietone created an issue. See original summary.

quietone opened merge request !17104

quietone’s picture

quietone commented
Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new One.png119.05 KB
new Two.png41.86 KB

Clearly no testing is dependent on the theme.

catch’s picture

catch
he/him
Primary language English
commented
Status: Needs review » Reviewed & tested by the community

This looks good to me, let's do it.

xjm’s picture

xjm
she/her
Primary language English
commented

If we do this for the Installer it does make sense to do it for our other nonstandard front controller for the same reason.

  • xjm committed 22a4c02f on main 
    task: #3622756 Use Admin theme for the update page

By: quietone

  • xjm committed 2fe2cc2a on 11.x 
    task: #3622756 Use Admin theme for the update page

By: quietone
xjm’s picture

xjm
she/her
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed to main and 11.x. Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.