Ivaylo Draganov

<p>Adds a menu to the admin bar to quickly identify different environments for a site (e.g. production and development) and easily switch to the same URL on other environments. Multi-site compatible for both sub-domain and sub-directory installations.</p>
<h3>Configuration</h3>
<p>The plugin has a convenient settings page but can also be configured programatically via a filter hook.</p>
<h4>Setting environments via the WordPress admin interface</h4>
<p>Navigate to “Settings > Set the Stage” in the WordPress admin to review and edit the configuration.</p>
<h4>Setting environments via a WordPress filter hook</h4>
<p>Hook to <code>drgnff_wp_stage_switcher__environments</code> and return an array with environments. Here’s an example filter function:</p>
<pre><code>add_filter( 'drgnff_wp_stage_switcher__environments', function ($envs) {
    return [
        [
            'url' => 'https://example.com', // home url
            'title' => 'LIVE', // display name
            'color' => '#ffffff', // hex color (optional)
            'background_color' => '#ff0000', // hex color (optional)
        ],
        [
            'url' => 'https://example.com',
            'title' => 'DEVELOPMENT',
            'color' => '#ffffff',
            'background_color' => '#228b22',
        ],
    ];
});
</code></pre>
<h4>Controlling visibility of the switcher</h4>
<p>By default the switcher menu is displayed to all logged in users. By hooking to <code>drgnff_wp_stage_switcher__should_display_switcher</code> and returning a boolean you can control whether the switcher should be displayed.</p>
<h4>Overriding the default environment</h4>
<p>The default environment is used for the current site if it’s not in the list of environments. By hooking to <code>drgnff_wp_stage_switcher__default_environment</code> you can control the title and colors for the default environment.</p>
<h4>A few notes on configuration</h4>
<ul>
<li>Filters have a precedence over manual configuration made in the settings page. If filters are used then relevant sections on the settings page are rendered as read-only.</li>
<li>For multi-site installations use the URLs of the main site.</li>
<li>The plugin initiates its logic on the <code>plugins_loaded</code> hook with priority <code>11</code>. Thus filter hooks that affect the plugin must be added before that.</li>
</ul>


Set the Stage

Quickly switch between environments (live, test, dev) from the admin bar.

Jamin Szczesny

<p><strong>PushLive allows you to have a fully functioning staging site or Multisite environment for editing and development that you then with a single click individually push to the live site when you’re ready.</strong></p>
<p><strong>Now works with Multisite!</strong> – Featuring Independent Pushes for Each Site</p>
<p><strong>Coming Soon (Next Major Release): PushLive Replicate</strong> – Easily create a staging site from your current live site</p>
<blockquote>
<h4>With PushLive you ( or your clients ) will make all initial and future edits on the staging site, push them to the live site, and in most cases never actually touch the live site except to enjoy its awesomeness</h4>
<h4> </h4>
<ul>
<li>
Please read the <a href="installation#sections" rel="nofollow ugc">Installation and Setup Instructions</a>
</li>
<li>
Single Site WordPress installations – PushLive is compatable with nearly all available Plugins
</li>
<li>
Special Multisite WordPress installations – PushLive is installed at the Network Admin level and best used when building and testing the site from the ground up because some Plugins are simply not compatable with PushLive in a Multisite environment
</li>
</ul>
</blockquote>
<p><strong>Requires:</strong></p>
<ul>
<li>Linux based server</li>
</ul>
<p><strong>Major features in PushLive include:</strong></p>
<ul>
<li>Fast staging to live pushes that only update the new or changed content as necessary.</li>
<li>Individual and Independent pushes for each site if using Multisite.</li>
<li>Easy 1 page, top to bottom setup and configuration.</li>
<li>A visible log of all previous pushes can be viewed on the main PushLive page.</li>
<li>Require all users to log in to view the staging server </li>
</ul>
<p><strong>Other Features:</strong></p>
<ul>
<li>Creates database backups during every push</li>
</ul>
<p><strong>History:</strong></p>
<ul>
<li>This was originally a simple tried and true Joomla 1.5 component my company developed many years ago</li>
<li>I then updated it for Joomla 2.5 and added some new features</li>
<li>Updated it for Joomla 3.5 and again added some new features</li>
<li>Rewrote it for WordPress for my own use about a year ago</li>
<li>Decided shortly after that I would become a WordPress developer and release it publicly</li>
<li>9 months of using it later I finally released it with some new features and minor bugs fixed</li>
<li>Historically PushLive has always served us/me good use so it should be something you can trust and rely on as well</li>
<li>We have NEVER had a major issue with PushLive we had to recover from, but you should always back up your site</li>
</ul>
<p><strong>Banner Imagery:</strong></p>
<ul>
<li>Photo by: Tom Johnson (https://www.facebook.com/tigger1759)</li>
</ul>


PushLive – Staging Sites to Live in One Click

I might be a bit biased, but PushLive has always worked like a charm for me! After you take a few minutes to set it up, the one button push is all you ever have to think about from then on to make your changes live. I thought about giving PushLive 4 stars, because I know it could be better... But how it could be better has really stumped me, so naturally the only logical thing to do in that case was to 5 star it and see if everyone else agrees!



Works Perfectly Every Time!

Allows you to have a fully functioning development Staging Site or Multisite that you can individually Push to Live when ready.

Set the Stage vs PushLive – Staging Sites to Live in One Click