apslo

Apslo Board is a WooCommerce plugin that automatically sends orders from your shop to the <a href="https://apslo.com/landing/board-ecommerce/" rel="nofollow ugc">Apslo Board</a> production management system.
Features:
<ul>
<li>Automatically send orders to Apslo Board on payment success, order processing, or manually</li>
<li>Per-product “Board Template” field (supports simple and variable products)</li>
<li>Order tracking URL stored and displayed on the orders list and single order pages</li>
<li>Tracking link included in WooCommerce customer emails (processing, on-hold, completed, invoice)</li>
<li>Send tracking link email to customers from the order page</li>
<li>Manual “Send order to Board” action from the order actions dropdown</li>
<li>Configurable default lead time for delivery date calculation</li>
<li>Test connection button to verify API key</li>
<li>Compatible with WooCommerce HPOS (High-Performance Order Storage)</li>
</ul>
Requirements:
<ul>
<li>WordPress 5.0 or higher</li>
<li>WooCommerce 6.0 or higher</li>
<li>PHP 8.0 or higher</li>
<li>An Apslo Board account and API key</li>
</ul>
<h3>External Services</h3>
This plugin connects to the Apslo Board external service (<a href="https://board.apslo.com" rel="nofollow ugc">https://board.apslo.com</a>) to send order data and retrieve tracking information. This connection is required for the plugin to function.
<h4>What data is sent and when</h4>
<ul>
<li>Test Connection — When the store administrator clicks “Test Connection” on the plugin settings page, a GET request is sent to <code>https://board.apslo.com/api/test-connection</code> containing only the API key. No customer or order data is transmitted.</li>
<li>Order submission — When an order is placed (or manually triggered by the administrator), the plugin sends a POST request to <code>https://board.apslo.com/api/orders</code> containing: order reference number, customer name, company, email, phone, billing and shipping addresses, order date, delivery date, and line items (product name, SKU, quantity, price, image URL, and board template name). The API key is included as a query parameter.</li>
<li>Tracking URL — The Apslo Board API may return a tracking URL in the response, which is stored as order meta and displayed to the customer in emails and on the order page.</li>
</ul>
No data is sent to any other third-party service.

Apslo Board

Integrate WooCommerce orders with the Apslo Board production management system.

Mark McNeece of 365i

Environment Indicator adds a prominent visual indicator to the WordPress admin bar showing the current site environment. This high-visibility indicator helps prevent accidental changes on production sites by making the environment instantly recognizable to logged-in users.
Perfect for developers, agencies, and teams managing multiple environments (development, staging, production) across different sites.
<h4>Key Features</h4>
Smart Environment Detection 
* Automatically detects environment using WordPress core constants (<code>WP_ENVIRONMENT_TYPE</code>) 
* Supports popular hosting providers: WP Engine, Pantheon, Kinsta, Flywheel 
* Legacy Bedrock constant support (<code>WP_ENV</code>) 
* Subdomain-based heuristics (dev.example.com, staging.example.com) 
* Manual override option for custom setups
Customization Options 
* Custom Colors – Match your branding or personal preferences for each environment 
* Custom Labels – Rename DEV/STAGING/LIVE to LOCAL, UAT, PRODUCTION, or anything you prefer 
* Role-Based Visibility – Control which user roles can see the indicator (great for client sites)
Visual Enhancements 
* Admin bar label (always visible) 
* Full admin bar background coloring (high-visibility option) 
* Browser tab prefix – instantly identify environments across multiple tabs 
* Top border in wp-admin screens 
* Admin footer watermark 
* Dashboard widget showing environment status and system information
Export/Import 
* Export settings as JSON to deploy across multiple sites 
* Import settings from JSON file 
* Perfect for agencies managing client sites with consistent configurations
Multisite Compatible 
* Full support for WordPress multisite installations 
* Network-wide settings when network-activated 
* Per-site settings when activated on individual sites
<h4>How It Works</h4>
Detection runs in this order:
<ol>
<li>WordPress core constant: <code>WP_ENVIRONMENT_TYPE</code></li>
<li>Legacy constant: <code>WP_ENV</code></li>
<li>Hosting provider constants (WP Engine, Pantheon, Kinsta, Flywheel)</li>
<li>Subdomain patterns (dev, staging, test, qa)</li>
<li>Default to LIVE if no detection</li>
</ol>
You can always override automatic detection and manually select the environment.
<h4>Perfect For</h4>
<ul>
<li>Developers – Never accidentally deploy to the wrong environment</li>
<li>Agencies – Manage multiple client sites with consistent environment indicators</li>
<li>Teams – Everyone instantly knows which environment they’re working in</li>
<li>Managed Hosting – Works out-of-the-box with WP Engine, Pantheon, Kinsta, and Flywheel</li>
</ul>
<h4>Zero Impact on Visitors</h4>
The indicator only displays for logged-in users. Public visitors see no performance impact or visual changes.
<h3>Development</h3>
Development of this plugin happens on GitHub: https://github.com/BSolveIT/environment-indicator
Bug reports and feature requests are welcome!

365i Environment Indicator

Displays a color-coded DEV, STAGING, or LIVE indicator in the admin bar to prevent accidental changes on production sites.

Apslo Board vs 365i Environment Indicator