MainWP Built For The Details That Matter

Product Updates

Last week’s MainWP updates focused on more reliable monitoring, more accurate reporting data, and better control over maintenance tasks across larger groups of sites.

Domain Monitor and Advanced Uptime Monitor received substantial reliability improvements, while Cache Control adds new options for managing how bulk cache purges are processed. Google Analytics also picked up fixes to keep reporting periods and refresh operations working as expected.

MainWP Add-ons

Domain Monitor 5.4

Domain Monitor 5.4 improves both the accuracy and reliability of domain monitoring.

Expiration messages now better distinguish between expired domains, domains expiring today, and cases where expiration data is unavailable. WHOIS handling has also been corrected for manual domain profiles and .hr domains.

Behind the scenes, scheduled checks, retries, alerts, and monitored-site reconciliation have all been improved. REST API, WP-CLI, and reconciliation operations now reduce repeated database queries, which is particularly useful on larger MainWP Dashboards. The release also includes additional validation, permissions, data-handling, and code-quality improvements.

Google Analytics 6.1.1

Google Analytics 6.1.1 improves reporting accuracy by making sure cached statistics and session, page/screen, and country data consistently use the reporting period you selected.

The update also fixes an issue where a foreground analytics refresh could block unrelated MainWP admin pages, reducing unnecessary interruption while working elsewhere in the Dashboard.

Google Search Console 6.2.1

Google Search Console 6.2.1 includes an internal update to its activation handling, improving file handling and removing transient retry logic.

Advanced Uptime Monitor 5.4

Advanced Uptime Monitor 5.4 updates the UptimeRobot integration to use the latest UptimeRobot REST API and improves how monitor operations are handled.

Creating, editing, and deleting monitors now has better duplicate and rollback handling, while API errors, rate limits, missing data, and unavailable uptime ratios are handled more consistently. The release also adds Abilities API support for uptime monitor providers.

Cache Control 5.2

Cache Control 5.2 gives you more control over bulk cache purges across your managed sites. You can now configure between 1 and 10 concurrent purge requests and add a delay of up to 10 seconds between batches.

That makes it easier to tune bulk cache clearing to suit your Dashboard and hosting environment rather than sending every request at once. Completion and success reporting have also been improved, along with handling for sites where no supported caching solution is detected.

Documentation Updates

Export Sites now provides safer migration guidance, clarifies exported credentials and connection data, and explains what must be supplied before importing sites into another MainWP Dashboard.

MainWP Dashboard Settings now covers automatic URL correction, WP-Cron behavior, monitoring options, child-site log retention, backup-provider overrides, and connection-management tools in greater detail.

Domain Monitor now explains expiration status indicators, Overview widgets, and per-site overrides for notifications and automated checks.

Advanced Uptime Monitor now documents Uptime Robot API v3 permissions, read-only access, uptime-ratio synchronization, and automatic rate-limit retries. The direct cron guide also includes an hourly Uptime Robot refresh worker.

Virusdie now clarifies paid-plan requirements for on-demand, WP-CLI, and REST API scans, including how scan availability works for accounts with mixed free and paid sites.

Cache Control now explains how to tune concurrent requests and delays for faster, more reliable bulk cache purges across large networks.

Patchstack now clearly distinguishes MainWP access requirements from the separate Patchstack Developer plan required for API integration.

Google Analytics and Google Search Console now include safe, step-by-step recovery instructions when their encryption keys cannot be added to wp-config.php automatically.