Scott Reilly

Though it is typically an individually configurable aspect of WordPress, there are times when forcing a single admin color scheme upon all users of a site can be warranted, such as to:
<ul>
<li>Provide a unique backend color scheme for multiple sites used by the same set of users to reinforce the difference between the sites.</li>
<li>Clearly denote backend differences between a production and staging/test instance of a site. Especially given that in this situation with the same plugins active and often the same data present, it can be easy to get mixed up about what site you’re actually on.</li>
<li>Force a site brand-appropriate color scheme.</li>
<li>Crush the expression of individuality under your iron fist.</li>
</ul>
Additionally, the plugin removes the “Admin Color Scheme” profile setting from users who don’t have the capability to set the admin color scheme globally since being able to set its value gives them the false impression that it may actually apply.
Links: <a href="https://coffee2code.com/wp-plugins/force-admin-color-scheme/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/force-admin-color-scheme/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/force-admin-color-scheme/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>
<h3>Hooks</h3>
The plugin is further customizable via one filter. Typically, code making use of filters should ideally be put into a mu-plugin or site-specific plugin (which is beyond the scope of this readme to explain).
c2c_force_admin_color_scheme (filter)
The ‘c2c_force_admin_color_scheme’ filter allows you to set or override the forced admin color scheme. Use of the constant (“) takes priority over the filtered value, but the filtered value takes priority over the value set via the admin.
Arguments:
<ul>
<li>$color (string): The name of the admin color scheme. If an empty string is returned, then the plugin will behave as if no forced admin color scheme has been defined.</li>
</ul>
Example:
<pre><code>/**
 * Sets a forced admin color scheme based on user. Admins get one color scheme, whereas everyone else gets another.
 *
 * @param string $color The current forced admin color scheme. Empty string indicates no forced admin color scheme.
 * @return string
 */
function my_c2c_force_admin_color_scheme( $color ) {
 return current_user_can( 'manage_options' ) ? 'sunrise' : 'coffee';
}
add_filter( 'c2c_force_admin_color_scheme', 'my_c2c_force_admin_color_scheme' );
</code></pre>

Force Admin Color Scheme

Force a single admin color scheme for all users of the site.

Goal Prevail

WordPress 7.0 changed the default admin color scheme to “Modern”, renaming the long-standing classic palette to “Fresh” and migrated existing users over to the new default. This plugin quietly restores the classic Fresh scheme for every user, exactly once, without taking away anyone’s freedom to switch back later.
<ul>
<li>Sets the color scheme to Fresh for newly registered users.</li>
<li>Migrates each existing user from “Modern” (or no preference) back to “Fresh” the next time they visit the dashboard, exactly once.</li>
<li>Leaves users who already chose another scheme (Light, Blue, Midnight, Ocean, Coffee, Ectoplasm, Sunrise, etc.) completely alone.</li>
<li>Restores the classic “Fresh” look on the login screen too, the blue WordPress logo, the classic blue submit button, and the classic blue input focus ring.</li>
<li>Cleans up after itself when deactivated, reverting every migrated user back to “Modern” and removing its own user metadata.</li>
<li>No settings page, no public front-end assets, no scheduled jobs, no mass updates on activation. The login styles are printed only while the plugin is active and disappear the moment it is deactivated or deleted.</li>
</ul>

Restore Old Admin Colors

Restore the classic pre-7.0 "Fresh" WordPress admin color scheme as the default, without overriding custom user choices.

Force Admin Color Scheme vs Restore Old Admin Colors