Andrés Villarreal

<p><strong>VERY IMPORTANT:</strong> This plugin is deprecated and will not be mantained anymore. Please consider using <a href="https://wordpress.org/plugins/stage-wp-plugin-manager/" rel="ugc">Stage WP Plugin Manager</a> instead.</p>
<p>If you develop locally, at some point you’ll have some plugins active in your local environment that you don’t need anymore when you deploy your code and database to staging or production. Sure, you can deactivate them before or after deploying, but you’re gonna need them again to be active if you want to perform changes to your code, or update your local database from your remote one. The whole process of activate and deactivate plugins for testing purposes could be really frustrating, and sometimes a complete waste of time.</p>
<p>Is in that kind of situations when the <strong>Environmental Plugin Manager</strong> can be a really helpful friend. Sadly, due to the sentitive work that this plugin performs, it doesn’t work right out of the box, so besides from installing this plugin, you need to do some additional work.</p>
<p><strong>Please read the following instructions very carefully.</strong></p>
<h4>What do I need to make it work?</h4>
<p><strong>The Environmental Plugin Manager works on some assumptions about your workflow:</strong></p>
<ol>
<li>You have a constant named <code>WP_ENV_PLUGINS</code> defined in your WordPress configuration file (often <code>wp-config.php</code>).</li>
<li>The <code>WP_ENV_PLUGINS</code> value is one of the following: <code>development</code>, <code>staging</code>, <code>production</code>.</li>
<li>
<p>The value of <code>WP_ENV_PLUGINS</code> is different in each of your stages. Some developers prefer to keep different configuration files for each one of their environments, or change the values of their constants based on some evaluation. For example, you could have something like this in your <code>wp-config.php</code> file:</p>
<p>if ( file_exists( dirname( <strong>FILE</strong> ) . ‘/development-config.php’ ) ) {     define(‘WP_ENV_PLUGINS’, ‘development’); } elseif ( file_exists( dirname( <strong>FILE</strong> ) . ‘/staging-config.php’ ) ) {     define(‘WP_ENV_PLUGINS’, ‘staging’); } else {     define(‘WP_ENV_PLUGINS’, ‘production’); }</p>
</li>
</ol>
<p>If you follow this example, note that <code>development-config.php</code> should not be included in your deployments to staging and production, and both <code>development-config.php</code> and <code>staging-config.php</code> should not exist in your production environment.</p>
<p><strong>These assumptions are not going to change</strong>, so you need to follow this practice in order to use this plugin correctly.</p>
<h4>How do I set up my environment?</h4>
<p>Once you have installed this plugin (my recommendation is to do it first in development), you will notice that a new link appears under each active plugin of the list, which reads “Use for development only” (note that “development” could also be “staging” or “production”, depending on your <code>WP_ENV_PLUGINS</code> constant). Keep that in mind and follow these steps:</p>
<ol>
<li>Activate all the plugins that you need to use for your environment.</li>
<li>Click the “Use for development only” link for all the plugins you want to mark as development-only.</li>
</ol>
<p>Once you click a link, that plugin will be added to the list of plugins that need to be active only in the current environment. You can click the “No more development only” link if you want to remove the plugin from the list.</p>
<h4>How do I reset my environment after a deploy?</h4>
<p>Once you performed a complete deploy (files and database) to a different environment, let’s say from development to staging, you will see that those plugins you selected in development to be active only in that environment are still active. Fear not! This is an intended behavior, as it would be insecure to change the status of the plugins without your knowledge, so you need to do it manually by just clicking the “Reset Plugins Environment (staging)” button that you see in your admin bar. After that, you should see your development-only plugins as not active.</p>
<p>That’s pretty much it. You can test it yourself before deploying by just changing the values of <code>WP_ENV_PLUGINS</code>.</p>
<h4>Auto-reset mode</h4>
<p>If you prefer your environments to be reset automatically, without clicking any button, you can add a second constant to your configuration file, called <code>WP_ENV_PLUGINS_AUTO_RESET</code>, which should be set to <code>true</code>. If you use this method, you won’t see the reset button in the admin bar anymore (instead, it will be replaced by an environment indicator), but keep in mind that the reset process will run every time a page of your site is loaded. It shouldn’t take a lot of resources, though.</p>
<p>If you use the auto-reset process, using this plugin as a <a href="https://codex.wordpress.org/Must_Use_Plugins" rel="nofollow ugc">must-use</a> will be a lot more effective.</p>
<h4>Will this plugin work on MultiSite installations?</h4>
<p>If you’re using MultiSite, please note that you can activate and deactivate this plugin globally, but you cannot manage plugin environments for the whole network, just for individual sites. Also, this plugin cannot manage network activated plugins. This is in the to-do list, though.</p>
<h4>Contribute</h4>
<p>You can make suggestions and submit your own modifications to this plugin on <a href="https://github.com/andrezrv/environmental-plugin-manager" rel="nofollow ugc">Github</a>.</p>


Environmental Plugin Manager

Gives you the option to define which plugins must be active for a particular environment only.

akkmarketingservices

marqs

<p>Process & Queue Manager (PQM) is a production queue and workflow management plugin for WordPress and WooCommerce.</p>
<p>PQM Free is designed for businesses that use WooCommerce as the source of customer orders and need a structured way to organize production work around those orders.</p>
<p>Instead of managing production only through order notes, spreadsheets, messages, or disconnected task lists, PQM adds a dedicated production layer inside the WordPress admin area. It helps your team follow production tasks, departments, statuses, workflow stages, planning dates, reports, and customer communication from one central place.</p>
<p>PQM Free is especially useful for print shops, workshops, production teams, manufacturing-related businesses, service companies, agencies, and order-based operations that need better internal production control.</p>
<p><strong>Important:</strong> PQM Free is built for WooCommerce order-based production workflows. In this Free version, practical production task creation is connected with WooCommerce orders. If you need to create production tasks manually without WooCommerce orders, that workflow is available in PQM Pro with the Offline Orders module.</p>
<h4>What PQM Free helps you manage</h4>
<ul>
<li>WooCommerce order-based production queue</li>
<li>Production tasks connected with customer orders</li>
<li>Departments and workflow stages</li>
<li>Custom production statuses</li>
<li>Task list with filtering and operational overview</li>
<li>Production dashboard for daily control</li>
<li>Calendar and Gantt-style production planning</li>
<li>Basic production reports and KPI visibility</li>
<li>Email communication tools for production workflows</li>
<li>Client-facing status and communication tools, where configured</li>
<li>Admin settings for departments, statuses, workflows, and access</li>
<li>Local data storage on the site owner’s own WordPress installation</li>
</ul>
<h4>WooCommerce-based production workflow</h4>
<p>PQM Free is built around WooCommerce orders. WooCommerce provides the order source, while PQM helps organize what happens after an order enters production.</p>
<p>A typical workflow looks like this:</p>
<ol>
<li>A customer order exists in WooCommerce.</li>
<li>The production team creates or manages a production task connected with that order.</li>
<li>The task moves through departments, statuses, and workflow stages.</li>
<li>The team can monitor deadlines, production progress, internal notes, and customer communication.</li>
<li>The business gains a clearer operational view of active production.</li>
</ol>
<p>This makes PQM Free a practical tool for companies that already use WooCommerce and want to turn order handling into a more controlled production process.</p>
<h4>Departments, statuses, and workflow control</h4>
<p>PQM lets you structure your production process around departments and status changes. You can define how work moves through your organization, track where a task currently is, and give your team a shared operational view.</p>
<p>This is useful for multi-step workflows such as print production, fulfillment, finishing, packaging, service delivery, internal approvals, or other order-based production processes.</p>
<h4>Calendar and Gantt-style planning</h4>
<p>PQM includes planning views that help teams understand current workload, planned production dates, and active tasks.</p>
<p>The calendar and Gantt-style screens are designed to make production easier to follow visually, especially when several tasks, departments, or deadlines are active at the same time.</p>
<h4>Email communication and client visibility</h4>
<p>PQM includes email communication tools and client-facing workflow features to support order-based production communication.</p>
<p>Depending on configuration, the plugin can help organize production-related messages, task status communication, and client-facing visibility around assigned work.</p>
<h4>Reports and operational visibility</h4>
<p>PQM Free includes basic reporting and dashboard views for production management. These screens help teams see workload, production activity, task status, and key operational indicators.</p>
<p>Reports are intended to support daily operational control, not just historical order review.</p>
<h4>Data ownership</h4>
<p>All plugin data remains on the site owner’s own WordPress installation. PQM Free does not require an external SaaS account to store production data.</p>
<h4>Pro modules and extensions</h4>
<p>Separate commercial add-ons and services may be available from the product website for businesses that need advanced production management features.</p>
<p>Examples of possible extensions include:</p>
<ul>
<li>Offline Orders for creating production tasks without WooCommerce orders</li>
<li>Warehouse and stock workflows</li>
<li>Documents Hub</li>
<li>Client Portal Pro</li>
<li>Purchasing and suppliers</li>
<li>Advanced Gantt planning</li>
<li>Sticky Notes and team productivity tools</li>
</ul>
<p>PQM Free remains usable as a WooCommerce-based production queue system. Pro modules are optional extensions for businesses that need a wider production operating system.</p>
<h4>Documentation</h4>
<p><a href="https://rewolucjaai.pl/?page_id=1006" rel="nofollow ugc">Read the PQM documentation</a></p>
<h4>Product website</h4>
<p><a href="https://rewolucjaai.pl/" rel="nofollow ugc">Visit the PQM product website</a></p>


Process & Queue Manager

WooCommerce-based production queue and workflow management for tasks, departments, planning, reports, email communication, and client status visibilit …

Environmental Plugin Manager vs Process & Queue Manager