MegaManager Connector

Description

MegaManager Connector allows you to connect your WordPress site to the MegaManager platform for:

  • Real-time Monitoring – Keep track of your site’s health and uptime status
  • Automated Backups – Schedule and manage full-site cloud backups
  • Remote Updates – Update plugins, themes, and WordPress core remotely
  • Cache Management – Clear page, object, and OPcache directly from admin bar or dashboard
  • Plugin Management – Activate and deactivate plugins from the dashboard
  • Security – Secure communication with HMAC signatures
  • Database Optimization – Analyze and optimize database tables remotely
  • Maintenance Mode – Enable/disable maintenance mode without writing files

External Services

This plugin connects to the MegaManager platform API to provide remote site management features. The service is hosted at https://wpmegamanager.com/api/fn.

What data is sent and when:

  • Site Registration (on connect): Your site URL, WordPress version, PHP version, and a generated site secret are sent once when you connect the plugin to MegaManager.
  • Heartbeat (every 5 minutes while connected): Site ID, WordPress version, PHP version, and site URL are sent to confirm your site is online and reachable. The heartbeat is essential for the connection status feature and runs automatically while the plugin is connected. It does NOT send any content, user data, or analytics — only basic environment identifiers.
  • Metrics (hourly, opt-in only): When you enable telemetry in the plugin settings, performance data (TTFB, page size, plugin list, theme, PHP/WP versions, disk/database size, activity logs) is sent hourly. This is disabled by default and requires explicit opt-in via the Settings > MegaManager page. You can disable it at any time; the setting takes effect immediately.
  • Backup operations: During cloud backups, your database and wp-content files are uploaded to MegaManager cloud storage via signed URLs.

No data is sent until you explicitly connect the plugin by entering a Connect Token from the MegaManager dashboard.

Screenshots

  • Dashboard – connected site overview
  • Cache management panel
  • Connect token input

Installation

  1. Upload the megamanager-connector folder to the /wp-content/plugins/ directory
  2. Activate the plugin through the ‘Plugins’ menu in WordPress
  3. Go to Settings > MegaManager in your WordPress admin
  4. Enter your Connect Token from the MegaManager dashboard
  5. Click “Connect to MegaManager”

FAQ

How do I connect my site?

After installing the plugin, go to Settings > MegaManager in WordPress admin, enter your Connect Token from the MegaManager dashboard, and click Connect.

Is my data secure?

Yes. All communication between your site and MegaManager uses HMAC-signed requests. Your site secret is stored locally and never shared.

What caching plugins are supported?

MegaManager Connector supports WP Super Cache, W3 Total Cache, WP Fastest Cache, LiteSpeed Cache, WP Rocket, Autoptimize, SG Optimizer, Hummingbird, WP-Optimize, and Breeze.

Does this plugin send data without my consent?

No. The plugin only sends data after you explicitly connect it. The heartbeat (connection check) runs only while connected. Performance metrics require an additional opt-in via the telemetry toggle in the plugin settings. You can disable telemetry or disconnect entirely at any time.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“MegaManager Connector” is open source software. The following people have contributed to this plugin.

Contributors

Changelog

1.2.8

  • FIX: Remote plugin, theme, and WordPress core updates no longer return success when the upgrader returns false or when the installed version is unchanged after the upgrade attempt
  • FIX: REST API: debug-log-trim route registers permission_callback correctly; added POST /wpmm/v1/debug-log-clear to empty debug.log without full parse (for large logs, use clear instead of trim)
  • IMPROVE: Debug log trim safety limit increased from 8 MB to 16 MB; clearer guidance when the file is too large to trim
  • IMPROVE: Broader debug.log line classification (PHP Error, memory limit, max execution time, uncaught Throwable) for remote monitoring

1.2.7

  • FEATURE: Auto updates default on for plugins/themes; configurable check interval (15 min / 1 h / 12 h / daily) replaces maintenance window field in connector settings
  • RELEASE: Aligned with MegaManager app (cookie consent, add-site connection gate, UI fixes)

1.2.6

  • FIX: Cache clear reporting — success only when something is actually cleared; OPcache unavailable or failed reset no longer reported as success
  • IMPROVE: wp-content/cache cleanup reports deleted file count; expired transients report row counts; skipped layers listed separately

1.2.5

  • FIX: Improved debug log handling and PHP error log processing (parsing, structured PHP error blocks)
  • FEATURE: REST API endpoints for remote diagnostics: PHP error log (/wpmm/v1/php-errors) and debug log trim (/wpmm/v1/debug-log-trim)
  • FIX: MegaManager API base URL aligned to https://wpmegamanager.com/api/fn with optional WPMM_API_BASE override; External Services readme updated accordingly (replaces legacy Supabase URL in documentation)
  • FIX: Admin AJAX URL fallback when ajaxurl is undefined (admin bar / cache UI reliability)
  • FIX: Additional bug fixes and stability improvements across connector operations

1.2.4

  • FIX: Bug fixes and stability improvements for the connector
  • COMPLIANCE: readme Contributors list updated
  • FIX: 1.2.3 changelog clarified (edge function auth headers use X-Site-Secret)

1.2.3

  • FEATURE: Switch User one-time login token support
  • FIX: Auto-login now uses REST API switch-user endpoint instead of removed legacy wpmm_autologin
  • FIX: Edge function auth headers corrected to use X-Site-Secret

1.2.1

  • COMPLIANCE: Added wpsupporting to Contributors in readme.txt
  • COMPLIANCE: Removed define(‘FS_METHOD’, ‘direct’) — no longer sets global constant; guides user to wp-config.php instead
  • COMPLIANCE: Backup manager inline / replaced with wp_register_style/wp_register_script + wp_add_inline_style/wp_add_inline_script via admin_enqueue_scripts hook
  • COMPLIANCE: Temp backup directory now uses wp_upload_dir() basedir with plugin-slug subfolder (megamanager-connector/) instead of hardcoded WP_CONTENT_DIR path

1.2.0

  • SECURITY: Removed all sslverify=false from outbound requests; default SSL verification is now used
  • STABILITY: Fixed is_plugin_active() fatal errors in cron/frontend contexts by adding safe include guard
  • STABILITY: Bounded disk usage scan (max 50,000 files) and media inventory (max 500 images) to prevent cron timeouts
  • STABILITY: Wrapped RecursiveIteratorIterator in try/catch for permission-denied safety
  • CRON: Moved cron_schedules filter into class constructor for reliable early registration
  • CRON: Ensured five_minutes schedule is always available before wp_schedule_event calls
  • COMPLIANCE: Fully removed residual handle_autologin() method from plugin code
  • COMPLIANCE: Updated readme External Services section with heartbeat data details

1.1.0

  • SECURITY: Removed insecure URL-based auto-login mechanism
  • SECURITY: Hardened REST API permission callbacks for PHP 8+ null safety (returns WP_Error instead of fatal)
  • COMPLIANCE: Added explicit telemetry opt-in toggle; metrics are disabled by default
  • COMPLIANCE: Added External Services section to readme.txt with Terms/Privacy links
  • COMPLIANCE: Removed all direct wp-content file writes for maintenance mode
  • COMPLIANCE: Refactored inline CSS/JS to use wp_enqueue_script/wp_enqueue_style and wp_add_inline_script/wp_add_inline_style
  • COMPLIANCE: Consistent plugin headers and author metadata referencing https://wpmegamanager.com
  • FIX: Replaced direct emoji characters in PHP with HTML entities for shared-hosting compatibility

1.0.1

  • Added backward-compatible remote backup support and command routing fixes

1.0.0

  • Initial release