Viktor Szépe

<h4>This plugin needs more documentation!</h4>
<p>You can edit your robots.txt and add remote content to it.<br />
E.g. you have several sites and want to use a centralized robots.txt.</p>
<h4>Features</h4>
<ul>
<li>Include or exclude WordPress’ own robots.txt (core function)</li>
<li>Include or exclude plugins – e.g. sitemap plugins – output to robots.txt (filter output)</li>
<li>Include or exclude a remote text file (the common part)</li>
<li>Include or exclude custom records from the settings page (the site specific part)</li>
</ul>
<h4>Where is robot.txt?</h4>
<p>WordPress handles robots.txt as a virtual URL – just the same way as posts and pages.</p>
<p>So when you browse to <code>https://example.com/robots.txt</code> WordPress generates robots.txt on the fly.</p>
<h4>TODO</h4>
<ul>
<li>add more description here</li>
<li>add a video too</li>
<li>add an admin notice for subdir installs (robots.txt is useless in a subdir)</li>
<li>‘At least one “Disallow” field must be present in the robots.txt file.’ – check for that</li>
</ul>
<h4>Links</h4>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/multipart-robotstxt-editor" rel="nofollow ugc">GitHub</a>.</p>


Multipart robots.txt editor

Customize your site's robots.txt and include remote content to it

Matthew Batchelder

<p>Have you ever wanted to get debug output sent to you from WordPress without interrupting the flow of the page?<br />
Do you ever wish you could get debug output from <em>other users’</em> sessions so you don’t have to:</p>
<ul>
<li>Log in as them</li>
<li>Asking them to look at debug output themselves (bleh)</li>
<li>Or try in vain to re-create their issue</li>
</ul>
<p>This plugin allows you to send debug messages via UDP to a <a href="https://github.com/borkweb/jabberbot" rel="nofollow ugc">Jabber Bot</a> that can then route<br />
the debug information to your IM client.</p>
<p><em>Note: This plugin sends the messages via UDP.  The receiving end doesn’t necessarily need to be a Jabber bot…it could be anything you want<br />
(e.g. email bot, logger, whatever).  My implementation is a Jabber Bot on my local dev environment 🙂</em></p>
<h4>Usage</h4>
<p>To send debug messages, simply call:</p>
<pre><code>do_action( 'debug_robot', $message [, $target ]);
</code></pre>
<ul>
<li><strong>$message</strong>: Message to send to your jabber bot.</li>
<li><strong>$target</strong>: <em>(optional)</em> Email address that your jabber bot will route the message to.</li>
</ul>
<p>To receive debug messages, you will need to have:</p>
<ul>
<li>Your <a href="https://github.com/borkweb/jabberbot" rel="nofollow ugc">Jabber Bot</a> installed and configured.</li>
<li>The Jabber Bot must be running.</li>
<li>You must have friended your robot’s jabber account with another jabber account (e.g. your Google account).</li>
<li>You must be signed into Google Talk in some way shape or form so that your jabber bot can IM you.</li>
</ul>
<p><em>Note: If your Jabber Bot isn’t running, no worries.  UDP doesn’t wait for a response so it won’t impact your WordPress instance…you just won’t get the messages that<br />
are sent until your bot is running 🙂</em></p>
<h3>Credits</h3>
<p>This code was largely written by <a href="https://github.com/abackstrom" rel="nofollow ugc">@abackstrom</a> with some additions by me while we worked at <a href="https://github.com/PlymouthState" rel="nofollow ugc">@PlymouthState</a>. I then ported it into a WordPress plugin.</p>


WP Debug Robot

An unobtrusive debugging tool for WordPress

Multipart robots.txt editor vs WP Debug Robot