Scott Reilly

This plugin prevents WordPress from allowing and handling any search requests from the front-end of the site. Specifically, this plugin:
<ul>
<li>Prevents the search form from appearing if the theme uses the standard <code>get_search_form()</code> function to display the search form.</li>
<li>Prevents the search form from appearing if the theme uses a <code>searchform.php</code> template</li>
<li>Prevents the search item from appearing in the admin tool bar when shown on the front-end.</li>
<li>Disables the search widget.
<ul>
<li>Removes the Search widget from the list of available widgets</li>
<li>Deactivates any search widgets currently in use in any sidebars (they are hidden, not deleted; they’ll reappear in their original locations if this plugin gets deactivated)</li>
</ul>
</li>
<li>Disables the search block.
<ul>
<li>Removes the Search block from the list of available blocks</li>
<li>Deactivates any search blocks currently in use, such as in posts or as a widget (they are disabled, not deleted; they’ll reappear if this plugin gets deactivated and the associated placeholder block doesn’t get deleted)</li>
</ul>
</li>
<li>With or without a search form, the plugin prevents any direct or manual requests by visitors, via either GET or POST requests, from actually returning any search results.</li>
<li>Submitted attempts at a search will be given a 404 File Not Found response, rendered by your site’s 404.php template, if present.</li>
<li>Disables output of <code>SearchAction</code> in SEO schema by the <a href="https://wordpress.org/plugins/wordpress-seo/" rel="ugc">Yoast SEO</a> plugin.</li>
</ul>
The plugin only affects search on the front-end of the site. It does not disable searching in the admin section of the site.
Links: <a href="https://coffee2code.com/wp-plugins/disable-search/" rel="nofollow ugc">Plugin Homepage</a> | <a href="https://wordpress.org/plugins/disable-search/" rel="ugc">Plugin Directory Page</a> | <a href="https://github.com/coffee2code/disable-search/" rel="nofollow ugc">GitHub</a> | <a href="https://coffee2code.com" rel="nofollow ugc">Author Homepage</a>

Disable Search


In 2024, numerous bots are crawling sites, generating significant search spam. Generally, site search incurs high costs, primarily because we end up paying for CPU resources consumed by spam.



If site search is not crucial for your website, I recommend activating this plugin.



Thank you, Scott, for maintaining this simple yet effective plugin!


The most effective way to avoid search spam

Disable the built-in front-end search capabilities of WordPress.

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.

Disable Search vs Force Admin Color Scheme