Force Admin Color Scheme vs Hide Broken Shortcodes

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: Provide a unique backend color scheme for multiple sites used by the same set of users to reinforce the difference between the sites. 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. Force a site brand-appropriate color scheme. Crush the expression of individuality under your iron fist. 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: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage Hooks 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: $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. Example: /** * 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' );

By default in WordPress, if the plugin that provides the functionality to handle any given shortcode is disabled, or if a shortcode is improperly defined in the content (such as with a typo), then the shortcode in question will appear on the site in its entirety, unprocessed by WordPress. At best this reveals unsightly code-like text to visitors and at worst can potentially expose information not intended to be seen by visitors. This plugin prevents unhandled shortcodes from appearing in the content of a post or page. If the shortcode is of the self-closing variety, then the shortcode tag and its attributes are not displayed and nothing is shown in their place. If the shortcode is of the enclosing variety (an opening and closing tag bookend some text or markup), then the text that is being enclosed will be shown, but the shortcode tag and attributes that surround the text will not be displayed. See the Filters section for more customization tips. Links: Plugin Homepage | Plugin Directory Page | GitHub | Author Homepage Developer Documentation Developer documentation can be found in DEVELOPER-DOCS.md. That documentation covers the hooks provided by the plugin. As an overview, these are the hooks provided by the plugin: hide_broken_shortcode : Customizes what, if anything, gets displayed when a broken shortcode is encountered. hide_broken_shortcodes_filters : Customizes what filters to hook to find text with potential broken shortcodes.