kunzemarketing

Use the Kunze Law Plug-In to import content (HTML snippets) from a central remote Address into a post or page using a shortcode. This is very beneficial in case you deliver content for several 
WordPress installations which needs a periodical update. The Plug-In will cache the remote content locally. After a predefined time, which can be set within the Plug-In, the snippet will be 
pulled again. The big advantage: In order to get all websites updated, you only have to edit the snippet on the remote server.
<h3>Example:</h3>
Imagine you are using the Plugin and a HTML snippet in hundreds of your websites. In case of content changes you only have to edit the snippet on the remote server. After expiry of the set cache time the new 
content will be pulled from the remote server. No need to do this manually on every website.
<h3>How to start:</h3>
<ol>
<li>Set up the remote server. Choose the url of your remote server.</li>
<li>If you would like to receive an E-Mail in case of remote access problems, please activate the “Get E-Mail Error Message checkbox”. Please provide a valid “E-Mail Error From Address” value.</li>
<li>Create HTML snippets. A snippet is a html file. The content of the snippet will be delivered. Always use filename.html as the file name. “filename” can be replaced to your need.</li>
<li>Upload the snippets onto the remote server.</li>
<li>Install the Plugin and fill in the following information:
<ul>
<li>Remote Server. e.g. http://yourserver.com/content</li>
<li>Cache time in seconds. This is the time in seconds after the plugin will look for updated content on the remote server.</li>
</ul>
</li>
<li>In order to get the content of a snippet named facebook.html, you have to use <code>[kunze_facebook]</code> as the shortcode.</li>
<li>Embed the shortcode within WordPress. This works in pages, posts and widgets.</li>
</ol>
<h3>Naming convention:</h3>
Shortcode within WordPress: <code>[kunze_filename]</code> 
HTML Snippet on remote Server: filename.html
Example of a HTML snippet:
<pre><code>`<div class="myClass">lorem ipsum</div>```
</code></pre>
<h3>The Kunze Law..</h3>
<ul>
<li>in case of problems with the remote server, a message can be send to the WordPress administration email address. (Settings > General > E-Mail Address). The email is send only once.</li>
<li>will cache locally your HTML snippets. If the remote server does not work any longer – the local saved snippets will be served.</li>
<li>works within a WordPress Multisite installation</li>
<li>is based on regular expressions</li>
</ul>

Kunze Law

The Kunze Law Plug-In import remote content into a post, page or widget using a shortcode.

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.

Kunze Law vs Lock My Site