ryanshoover

<p><a href="https://circleci.com/gh/ryanshoover/safe-staging/tree/master" rel="nofollow ugc"></a></p>
<p>Simply define your production url in settings and copy your site to your staging instance without fear. The staging site won’t send any emails and won’t process any payments.</p>
<h4>Why should I use the plugin</h4>
<p>If you host your site on a managed host that provides a staging instance (WP Engine, Siteground, and others), or if you run a staging instance for a self-hosted website, you may have found that WordPress and WooCommerce will automatically send emails and process payments from the staging site. Whenever you clone your production site to your staging site, you would normally need to complete a number of steps to make your site “safe for staging.”</p>
<p>Instead, install this plugin in production, set the production URL, and safely copy your site to and from staging. No other steps needed!</p>
<h4>Features on Staging</h4>
<ol>
<li>A “noindex” tag is added to all pages. Your staging site won’t show up in Google.</li>
<li>WordPress emails are stopped. The site won’t send any emails except for the password reset email. Please note, this feature may not be compatible with plugins that offload email to a 3rd party service.</li>
<li>The WooCommerce checkout page has a warning message notifying the visitor they are viewing the staging site.</li>
<li>WooCommerce payment gateways are suspended. Bank account transfer, Cash on Delivery and Check are left enabled. Stripe is automatically put into test mode.</li>
<li>WooCommerce Subscriptions is put into staging mode.</li>
</ol>


Safe Staging

My client did something that suddenly started sending emails from the staging server for their membership site. This plugin allowed me to kill the emails from sending and backtrack the issues caused before it got out of hand. 

This saved my client

Safely copy your WordPress, WooCommerce, and membership site between production and staging.

Scott Reilly

<p>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:</p>
<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>
<p>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.</p>
<p>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></p>
<h3>Hooks</h3>
<p>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).</p>
<p><strong>c2c_force_admin_color_scheme (filter)</strong></p>
<p>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.</p>
<p>Arguments:</p>
<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>
<p>Example:</p>
<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.

Safe Staging vs Force Admin Color Scheme