kunzemarketing

<p>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<br />
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<br />
pulled again. The big advantage: In order to get all websites updated, you only have to edit the snippet on the remote server.</p>
<h3>Example:</h3>
<p>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<br />
content will be pulled from the remote server. No need to do this manually on every website.</p>
<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 <strong>facebook.html</strong>, 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>
<p>Shortcode within WordPress: <code>[kunze_filename]</code><br />
HTML Snippet on remote Server: <strong>filename.html</strong></p>
<p>Example of a HTML snippet:</p>
<pre><code>`<div class="myClass"><strong>lorem ipsum</strong></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.

Phill Healey

<p>This is a WordPress object cache backend that supports the MemCachier caching service. It requires <a href="http://pecl.php.net/package/memcached" rel="nofollow ugc">Memcached ver. 2.2.0 PECL package</a> or greater for SASL support.</p>
<p>This is a fork of <a href="https://github.com/tollmanz/wordpress-pecl-memcached-object-cache" rel="nofollow ugc">tollmanz</a> object cache, adding SASL and binary protocol support for cloud based caches.</p>
<h3>Credits</h3>
<ul>
<li><a href="https://github.com/tollmanz/wordpress-memcached-backend" rel="nofollow ugc">wordpress-memcached-backend</a></li>
<li><a href="https://github.com/RedisLabs/wordpress-memcached-backend" rel="nofollow ugc">RedisLabs SASL support</a></li>
</ul>


Clinical Memcachier

This is the best plugin for caching your data objects with the remote memcached service provided by Memcachier, of all the ones I've tried.

Best Data Cache

This is a WordPress object cache backend that supports the MemCachier caching service. It requires Memcached ver. 2.2.0 PECL package or greater for SA …

Kunze Law vs Clinical Memcachier