开发者 | coffee2code |
---|---|
更新时间 | 2021年10月15日 13:47 |
捐献地址: | 去捐款 |
PHP版本: | 4.1 及以上 |
WordPress版本: | 5.8 |
版权: | GPLv2 or later |
版权网址: | 版权信息 |
/wp-content/plugins/
).c2c_force_admin_color_scheme
filter in custom code to programmatically set the forced admin color scheme with greater control.C2C_FORCE_ADMIN_COLOR_SCHEME
constant somewhere (such as wp-config.php
) if you'd prefer to configure the color that way. Configuring the color in this manner takes precedence over the color as configured via an admin's profile. Also, if the constant is used, the plugin prevents the setting of admin color schemes entirely from within user profiles, including by admins.Have you followed all of the installation instructions? You must configure the forced admin color scheme by setting the color scheme for yourself while also checking the "Force this admin color scheme?" checkbox.
Uncheck the "Force this admin color scheme?" when updating an administrative profile (assuming the plugin's provided constant and/or filter aren't being used), or simply deactivate the plugin.
Yes, but only via custom coding by making use of the c2c_force_admin_color_scheme
filter. See the documentation for the filter for an example.
The plugin will recognize that the chosen admin color scheme is no longer valid and will act as if one isn't set. In such a case, users would then see their individually chosen admin color schemes. If the custom admin color scheme becomes available again (before a new existing color scheme is selected as the new scheme to be forced), then the plugin will reinstate it as the forced admin color scheme.
Just to be clear, if an admin color scheme is being forced, then non-admininistrative users won't see the admin color scheme picker at all. The plugin does not disable the admin color scheme picker for administrative users even if a value is directly configured in code (via the constant or the filter) so that the admin color schemes can still be seen and previewed in case an admin user wants to evaluate alternatives.
Yes.
phpunit/
into tests/
phpunit/bin
into tests/
phpunit/
to house all files related to unit testingbin/
to phpunit/bin/
tests/bootstrap.php
to phpunit/
tests/
to phpunit/tests/
phpunit.xml
to phpunit.xml.dist
per best practices