Security Enhancements, Reliability Fixes, and a New AdSanity Integration

Product Updates

These updates are focused on connection security in MainWP Child, a database installer fix for Code Snippets, and a new third-party add-on for teams managing AdSanity across multiple WordPress sites.

MainWP Child 6.1.2

MainWP Child 6.1.2 improves connection verification for passwordless setups.

If Password Authentication is disabled, adding or reconnecting a child site now requires the Unique Security ID. This applies to manual connections, reconnects, the MainWP REST API, and other automations.

For agencies and site care teams using passwordless workflows, this adds a clearer control point around how sites are connected to the Dashboard. Fewer loose ends, better connection handling and more predictable site management.

Code Snippets received a small but important installer fix.

This update corrects the Code Snippets table installer to ensure the auto-increment ID is always defined as the primary key. That helps keep the extension’s database structure cleaner and more reliable during installs and upgrades.

AdSanity for MainWP – New 3rd-party Integration

A new third-party MainWP add-on, AdSanity for MainWP, is now available on WordPress.org.

For teams running AdSanity across multiple client sites, this add-on brings ad reporting into the MainWP Dashboard. It shows fleet-wide ad performance, including impressions, clicks, and CTR, with 7, 30, and 90-day date ranges. It also adds per-site reporting, trend charts, expiring ad alerts, connector health checks, and an overview widget for published ads and ads expiring soon.

That means fewer site-by-site logins when checking campaign performance or spotting ads that are close to expiring. This is particularly useful if you manage publisher sites, advertiser campaigns, or client sites where ad inventory needs regular oversight.

A practical note: this is a MainWP Dashboard extension. Each managed site still needs AdSanity core and the free AdSanity MainWP Connector installed for reporting to work. The add-on is focused on reporting and monitoring, not creating or deploying ads from the MainWP Dashboard.

Documentation Updates

MainWP Child connection docs now clarify that each site must use an Administrator Password, Unique Security ID, or both, with updated setup guidance in Get Started with MainWP, Manage Child Sites, and Connection Security.

Bulk site workflows now better explain which connection credentials to include when importing, exporting, or moving sites between Dashboards, helping avoid CSV import failures and credential mismatches. See Manage Child Sites, Move Child Sites, and Export Child Sites.

API and command-line users now get clearer guidance for adding sites with the required connection credentials through the REST API Sites, REST API Batch, Abilities API Sites, and MainWP WP-CLI Commands documentation.

The Boilerplate Add-on guide was refreshed with current MainWP Dashboard navigation, clearer token setup steps, and updated workflows for creating, editing, publishing, and removing Boilerplate posts and pages.

Extension licensing troubleshooting now includes clearer recovery steps for failed add-on updates, including resetting the plugin activation and license connection before retrying the update.

These updates reflect an ongoing focus on the fundamentals of WordPress site management. Whether it’s strengthening site connections, improving extension reliability, or making documentation easier to follow, each change is intended to help you work more efficiently across your site portfolio.