dawsony

<p><strong>DawsonyWeb – Admin Utilities</strong> is a developer-friendly WordPress plugin that packages the small admin improvements you actually need into one clean, modular plugin. No bloat, no nag banners, no upsells.</p>
<p>Each tool (module) can be independently enabled or disabled. Only enabled modules load their hooks and assets, keeping your admin fast.</p>
<h4>Modules Included</h4>
<p><strong>Copy Buttons Everywhere</strong><br />
Adds copy buttons for IDs, permalinks, edit links, and slugs across:</p>
<ul>
<li>Post/Page/CPT list tables (row actions)</li>
<li>Single post edit screens (meta box)</li>
<li>Users list table</li>
<li>Taxonomy term list tables</li>
</ul>
<p><strong>Environment Badge</strong><br />
Shows a color-coded environment indicator (LOCAL / DEV / STAGING / LIVE) in the admin bar. Uses <code>wp_get_environment_type()</code> with a <code>DAWSONY_ENV</code> constant fallback. Configurable per role.</p>
<p><strong>Debug Snapshot</strong><br />
A read-only support snapshot page showing WordPress version, PHP version, server info, memory limits, active theme, active plugins, and more. Includes a one-click “Copy as Text” button for easy sharing with support teams.</p>
<p><strong>Global Admin Notice Board</strong><br />
Set a message that appears in wp-admin for selected roles. Supports basic HTML, notice type (info/success/warning/error), optional expiry date, and per-user dismissal with admin reset.</p>
<p><strong>Dashboard Widget Manager</strong><br />
Hide or show dashboard widgets per user role. Automatically discovers all registered widgets (core + plugin) and lets you control visibility from a simple settings UI.</p>
<h4>Philosophy</h4>
<ul>
<li>No front-end output or performance impact</li>
<li>No external tracking, telemetry, or “phone home” behavior</li>
<li>All inputs sanitized, all outputs escaped</li>
<li>Nonces for all actions, capability checks for all settings</li>
<li>Clean uninstall removes all data</li>
</ul>
<h3>Privacy</h3>
<p>DawsonyWeb – Admin Utilities does not collect, store, or transmit any data externally. All data is stored locally in your WordPress database (wp_options and wp_usermeta). No cookies are set. No external requests are made.</p>


DawsonyWeb – Admin Utilities

A lightweight, modular admin suite that bundles small, high-value quality-of-life tools for developers, site admins, and editors.

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.

DawsonyWeb – Admin Utilities vs Environmental Plugin Manager