GDimitrov

MegaManager Connector allows you to connect your WordPress site to the <a href="https://wpmegamanager.com" rel="nofollow ugc">MegaManager</a> platform for:
<ul>
<li>Real-time Monitoring – Keep track of your site’s health and uptime status</li>
<li>Automated Backups – Schedule and manage full-site cloud backups</li>
<li>Remote Updates – Update plugins, themes, and WordPress core remotely</li>
<li>Cache Management – Clear page, object, and OPcache directly from admin bar or dashboard</li>
<li>Plugin Management – Activate and deactivate plugins from the dashboard</li>
<li>Security – Secure communication with HMAC signatures</li>
<li>Database Optimization – Analyze and optimize database tables remotely</li>
<li>Maintenance Mode – Enable/disable maintenance mode without writing files</li>
</ul>
<h3>External Services</h3>
This plugin connects to the MegaManager platform API to provide remote site management features. The service is hosted at <code>https://wpmegamanager.com/api/fn</code>.
What data is sent and when:
<ul>
<li>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.</li>
<li>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.</li>
<li>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.</li>
<li>Backup operations: During cloud backups, your database and wp-content files are uploaded to MegaManager cloud storage via signed URLs.</li>
</ul>
No data is sent until you explicitly connect the plugin by entering a Connect Token from the MegaManager dashboard.
<ul>
<li>Terms of Service: <a href="https://wpmegamanager.com/terms" rel="nofollow ugc">https://wpmegamanager.com/terms</a></li>
<li>Privacy Policy: <a href="https://wpmegamanager.com/privacy" rel="nofollow ugc">https://wpmegamanager.com/privacy</a></li>
</ul>

MegaManager Connector

Connects your WordPress site to MegaManager for monitoring, backups, cache management, and remote administration.

Juanma Evaristo

Lock My Site is a lightweight plugin that enables remote management of your WordPress site through a secure REST API. Perfect for agencies, freelancers, and anyone managing multiple WordPress sites.
<h4>Features</h4>
<ul>
<li>Complete Health Check – Monitor site status, PHP version, memory usage, and more</li>
<li>Update Management – Manage plugins, themes, core, and translations updates remotely</li>
<li>Plugin Management – Activate, deactivate, and get detailed plugin information</li>
<li>Theme Management – Switch themes and manage theme updates</li>
<li>Database Optimization – Clean up and optimize database tables</li>
<li>Security Audit – Basic security checks and recommendations</li>
<li>Error Logs – Access PHP error logs remotely</li>
<li>User Management – List users and roles</li>
</ul>
<h4>Security</h4>
<ul>
<li>API Key authentication</li>
<li>Optional HMAC signature verification</li>
<li>Optional IP whitelist</li>
<li>Rate limiting protection</li>
<li>Automatic lockout after failed attempts</li>
<li>API key expiration (90 days)</li>
<li>Email alerts for suspicious activity</li>
<li>Activity logging</li>
</ul>
<h4>Available Endpoints</h4>
Status & Health 
* <code>GET /ping</code> – Connection check 
* <code>GET /health</code> – Complete site health status
Updates 
* <code>GET /updates</code> – Available updates (plugins, themes, core, translations) 
* <code>POST /update/plugin</code> – Update a specific plugin 
* <code>POST /update/theme</code> – Update a specific theme 
* <code>POST /update/core</code> – Update WordPress core 
* <code>POST /update/all-plugins</code> – Update all plugins 
* <code>POST /update/all-themes</code> – Update all themes 
* <code>POST /update/translations</code> – Update all translations
Plugins 
* <code>GET /plugins</code> – List all plugins 
* <code>GET /plugins/{plugin}</code> – Get plugin details 
* <code>POST /plugins/activate</code> – Activate a plugin 
* <code>POST /plugins/deactivate</code> – Deactivate a plugin 
* <code>GET /plugins/ignored</code> – List ignored plugins 
* <code>POST /plugins/ignore</code> – Ignore a plugin from bulk updates 
* <code>POST /plugins/unignore</code> – Remove plugin from ignored list
Themes 
* <code>GET /themes</code> – List all themes 
* <code>POST /themes/activate</code> – Activate a theme
Database 
* <code>GET /database/stats</code> – Database statistics 
* <code>POST /database/cleanup</code> – Clean database (revisions, drafts, spam, etc.) 
* <code>POST /database/optimize</code> – Optimize database tables
Logs 
* <code>GET /logs/php</code> – PHP error log 
* <code>GET /logs/activity</code> – Plugin activity log
Users 
* <code>GET /users</code> – List WordPress users
<h3>External services</h3>
This plugin connects to the following external services:
<h4>1. WordPress.org Checksums API</h4>
<ul>
<li>Service URL: <code>https://api.wordpress.org/core/checksums/1.0/</code></li>
<li>What it does: Retrieves the official MD5 checksums for all WordPress core files so the plugin can verify that no core file has been modified or tampered with.</li>
<li>When data is sent: Only when a core integrity check is explicitly triggered by the site administrator via the authenticated REST API endpoint <code>/security/core-integrity</code>.</li>
<li>What data is sent: The installed WordPress version number and the site locale (e.g. <code>en_US</code>). No personal data is sent.</li>
<li>Service provider: WordPress.org (Automattic Inc.)</li>
<li>Terms of use: <a href="https://wordpress.org/about/domains/" rel="ugc">WordPress.org Terms of Service</a></li>
<li>Privacy policy: <a href="https://wordpress.org/about/privacy/" rel="ugc">WordPress.org Privacy Policy</a></li>
</ul>
<h4>2. WordPress.org Translations API</h4>
<ul>
<li>Service URL: <code>https://api.wordpress.org/translations/plugins/1.0/</code>, <code>https://api.wordpress.org/translations/themes/1.0/</code>, and <code>https://api.wordpress.org/translations/core/1.0/</code></li>
<li>What it does: Returns the latest available translation package versions for plugins, themes, and WordPress core in the site’s locale, so the plugin can determine which translations need updating.</li>
<li>When data is sent: When translation updates are checked, either on demand or as part of a full updates check, explicitly triggered by the site administrator via the authenticated REST API.</li>
<li>What data is sent: Plugin/theme slugs, their version numbers, and the site locale. No personal data is sent.</li>
<li>Service provider: WordPress.org (Automattic Inc.)</li>
<li>Terms of use: <a href="https://wordpress.org/about/domains/" rel="ugc">WordPress.org Terms of Service</a></li>
<li>Privacy policy: <a href="https://wordpress.org/about/privacy/" rel="ugc">WordPress.org Privacy Policy</a></li>
</ul>
These are the only two external services this plugin connects to. No other HTTP requests are made to any third-party service.
<h4>Important note about domain name references in the source code</h4>
The plugin’s security scanner contains a hardcoded list of well-known, legitimate third-party domain names used as a local string-matching whitelist only. This list includes domains such as:
<ul>
<li>google-analytics.com, googletagmanager.com, googleapis.com</li>
<li>maps.google.com, maps.googleapis.com</li>
<li>tawk.to, crisp.chat, intercom.io, zendesk.com</li>
<li>cdn.jsdelivr.net, cdnjs.cloudflare.com, code.jquery.com, unpkg.com</li>
<li>recaptcha.net, gstatic.com</li>
</ul>
These domains are NOT contacted, called, or connected to in any way by this plugin. No HTTP requests, API calls, or any form of network communication is made to any of these domains.
The domain names appear as plain string constants in a PHP array. When the security scanner analyzes post and page content for potentially malicious script injections (e.g. <code><script src="..."></code> tags), it compares the <code>src</code> attribute against this whitelist using local string matching. Scripts referencing whitelisted domains are recognized as legitimate and excluded from the scan results, reducing false positives. The entire comparison happens locally in PHP memory — no data leaves the server.

Lock My Site

Lightweight worker plugin for remote WordPress maintenance and management via secure REST API.

MegaManager Connector vs Lock My Site