saas

I don’t like certain things, such as curly “smart” quotes and self-pings. Instead of installing six or seven plugins to handle this, I decided to create one plugin to address the common issues. Disabler allows you to select and deactivate specific settings rather than disabling everything, all through a straightforward UI.
This plugin enables you to disable/remove the following features:
Editor
<ul>
<li>Classic theme styles</li>
<li>Texturization (including Smart/Curly quotes, EM dash, EN dash, and ellipsis)</li>
<li>The automatic capitalization of the P in WordPress (WordPress 3.0+ only)</li>
<li>The <code></code> that is automatically inserted</li>
<li>Autosaving of Posts etc</li>
</ul>
Back-End
<ul>
<li>Self Ping</li>
</ul>
Front-End
<ul>
<li>Disable links to WordPress’ internal ‘shortlink’ URLs for your posts. E.g., </li>
</ul>
Performance
<ul>
<li>Disable emojis</li>
<li>Prevent unauthorized embedding and remove JavaScript requests related to WordPress embeds</li>
<li>Control heartbeat rate: Disable it completely, etc.</li>
<li>Disable dashboard widgets</li>
</ul>
Revisions
<ul>
<li>Disable revisions completely or selectively for each post type.</li>
</ul>
Feeds
WordPress outputs your content in various formats across different URLs, including feeds like RSS and Atom. It’s advisable to disable unused formats for better control over your content distribution.
<ul>
<li>Redirect feeds (if disabled): Redirects feeds to prevent access.</li>
<li>Disable global feed: Removes URLs providing an overview of recent posts.</li>
<li>Disable global comment feeds: Removes URLs providing an overview of recent comments.</li>
<li>Disable post comments feeds: Removes URLs providing recent comments on each post.</li>
<li>Disable post authors feeds: Removes URLs providing recent posts by specific authors.</li>
<li>Disable post type feeds: Removes URLs providing recent posts for each post type.</li>
<li>Disable category feeds: Removes URLs providing recent posts for each category.</li>
<li>Disable tag feeds: Removes URLs providing recent posts for each tag.</li>
<li>Disable custom taxonomy feeds: Removes URLs providing recent posts for each custom taxonomy.</li>
<li>Disable search results feeds: Removes URLs providing search result information.</li>
<li>Disable Atom / RDF feeds: Removes URLs providing alternative formats of the above.</li>
</ul>
Rest API
The REST API in WordPress provides powerful functionality for interacting with your site’s data. However, there may be cases where you want to restrict or disable access to this API for security or privacy reasons.
<ul>
<li>Disable REST API for visitors: Prevents access to the REST API endpoints for non-authenticated visitors.</li>
<li>Disable REST API links: Removes the link tag in the HTML header that points to the REST API endpoint.</li>
<li>Disable REST API RSD link: Removes the RSD (Really Simple Discovery) link tag that specifies the REST API endpoint.</li>
<li>Disable REST API link in HTTP headers: Removes the HTTP header link that specifies the REST API endpoint.</li>
</ul>
Privacy Settings
<ul>
<li>Outputting WordPress version in your blog headers</li>
<li>Sending your blog URL to WordPress when checking for updates on core/theme/plugins</li>
</ul>
XML-RPC
<ul>
<li>XML-RPC Control: Choose between completely disabling XML-RPC or selectively enabling it.</li>
<li>Whitelist IP Addresses: Option to whitelist additional IP addresses.</li>
<li>XML RPC Methods: Control which XML-RPC methods are allowed.</li>
<li>XML-RPC HTTP Headers: Ability to add or remove custom XML-RPC HTTP headers.</li>
<li>Remove RSD, WLW Manifest, Pingback Links: Option to remove these XML-RPC-related links from the website.</li>
</ul>
Updates
<ul>
<li>Plugin Updates: Users can choose between manual or automatic updates, or disable updates entirely.</li>
<li>Theme Updates: Similar options as plugin updates.</li>
<li>Auto and Async Translations Updates: Options to enable auto updates, disable them, or keep the default setting.</li>
<li>WordPress Core Updates: Various options to manage updates, including disabling updates, allowing minor or major auto updates, or enabling updates for development installations.</li>
<li>Enable updates for VCS Installations: Users can choose to enable or disable updates for installations under version control systems.</li>
<li>Updates nags only for Admin: Hides WordPress core update notices for users without update capabilities.</li>
</ul>
Usage Tracking
<ul>
<li>This setting enables anonymous usage data collection for the plugin, including WordPress information, installed plugins/themes, and server details.</li>
</ul>
All options default to off and are cleaned up upon uninstall.
<ul>
<li><a href="https://wordpress.org/plugins/disabler/" rel="ugc">Plugin Site</a></li>
</ul>

Disabler

Instead of installing a million plugins to disable features you don't want, why not use just ONE plugin?

Matt Gibbs

Tim Nolte

Josh Levinson

jmslbam

Elvis Morales

jgleisner

Forum One

mickaelperrin

alfreddatakillen

dsteersf1

gbeezus

WP-CFM lets you copy database configuration to / from the filesystem. Easily deploy configuration changes without needing to copy the entire database. WP-CFM is similar to Drupal’s Features module.
<h4>How will WP-CFM benefit me?</h4>
<ul>
<li>Less need to copy over the entire database.</li>
<li>No more rushing to figure out which settings you forgot to change.</li>
<li>Easily track and version configuration changes via git, subversion, etc.</li>
</ul>
<h4>Which data does WP-CFM support?</h4>
<ul>
<li>WP settings (<code>wp_options</code> table)</li>
<li>Multisite settings (<code>wp_sitemeta</code> table)</li>
<li>Taxonomy terms</li>
<li>Custom Field Suite field groups</li>
</ul>
<h4>Terminology</h4>
<ul>
<li>Bundle – A group of (one or more) settings to track</li>
<li>Push – Export database settings to the filesystem</li>
<li>Pull – Import file-based settings into the database</li>
</ul>
<h4>WP-CLI</h4>
WP-CFM supports [pull / push / diff] of bundles from the command-line using <a href="http://wp-cli.org/" rel="nofollow ugc">WP-CLI</a>:
<pre>
wp config pull [bundle_name]
wp config push [bundle_name]
wp config diff [bundle_name]
wp config bundles
wp config show_bundle [bundle_name]
</pre>
You can optionally set <code>bundle_name</code> to “all” to include all bundles.
Append the <code>--network</code> flag to include multisite bundles.
<h4>Filters</h4>
See the filters reference page at the <a href="https://github.com/forumone/wp-cfm/wiki/Filters-Reference" rel="nofollow ugc">GitHub Wiki</a>.

WP-CFM

Awesome plugin for tracking configuration in version control.
I auto import bundles in my test and live environments when deploying from development which saves me a ton of time from having to make the same configuration updates over and over.



Configure once, deploy multiple times

This is very awesome, old but still serves it purpose, hopefully it would have a version bump so it wont look outdated :)

Very useful to version control the options of your site

Manage and deploy WordPress configuration changes.

Disabler vs WP-CFM