Gregory Karpinsky (@tivnet)

<p><strong>NOTE:</strong> The current version of the TIVWP-DM plugin was released mostly for educational purposes.</p>
<p>I appreciate your comments and ideas. Please see the <a href="https://github.com/TIVWP/tivwp-dm" rel="nofollow ugc">TIVWP-DM Development Manager’s GitHub repo</a> for <strong>additional files showing how to setup Travis-CI/PHPUnit for automatic testing</strong>.</p>
<p><strong>TIVWP-DM Development Manager</strong> is a plugin for WordPress developers. Its main features are:</p>
<ul>
<li>Prompts to automatically install and activate popular development plugins from the WordPress repository</li>
<li>Allows to activate / deactivate those plugins in bulk – with a single admin menu click or automatically, according to the wp-config settings</li>
</ul>
<h4>3rd Party Software Used</h4>
<p><a href="https://github.com/thomasgriffin/TGM-Plugin-Activation" rel="nofollow ugc">TGM-Plugin-Activation</a> by</p>
<ul>
<li>Thomas Griffin <a href="mailto:thomas@thomasgriffinmedia.com" rel="nofollow ugc">thomas@thomasgriffinmedia.com</a> and</li>
<li>Gary Jones <a href="mailto:gamajo@gamajo.com" rel="nofollow ugc">gamajo@gamajo.com</a></li>
</ul>


TIVWP-DM Development Manager

Viktor Szépe

<p>Toggles human and machine language (aka ID-s) on admin pages.</p>
<h4>Only for development!</h4>
<p>This plugin shows you the ID-s of almost all form fields including selects, checkboxes and radio buttons like in <code>wp-admin/options.php</code>.</p>
<p>It works only on WordPress Settings API-like formatted — not necessarily API generated — admin pages. E.g. <code><input></code> elements cannot be wrapped in <code><span></code>.</p>
<h4>Activation</h4>
<p>You can find the plugin’s checkbox in standard Screen Options (upper right corner). This checkbox could be overwritten — thus hidden — by poorly written plugins. To restrict Machine Language to a certain admin page, copy this to your <code>wp-config.php</code>:</p>
<pre><code>define( 'MACHINE_LANGUAGE_HOOK', 'load-options-reading.php' ); </code></pre>
<p>For example this line causes to run only on Settings / Reading.</p>
<h4>Features</h4>
<ul>
<li>Basically all input ID-s are displayed in place of labels, actually <code>for</code> attributes of labels</li>
<li><code>select</code>-s get a title showing all option values comma separated (hover over <code>select</code>-s with your mouse)</li>
<li><code>option</code>-s get values appended in the form of “original option text|value”</li>
<li>Radio button labels will show: “name|value”</li>
<li>Descriptions (<code>p</code>-s and <code>span</code>-s with “description” class) will be hidden, this way Machine Language will clean up all admin pages, descriptions are hidden by CSS, so there’s no <a href="http://en.wikipedia.org/wiki/Flash_of_unstyled_content" rel="nofollow ugc">FOUC</a></li>
</ul>
<h4>Other notes</h4>
<ul>
<li>Radio buttons or checkboxes with empty value are displayed with the “Empty Set” Unicode character: “? ” (U+2205) ( e.g. Settings / Permalinks / Default )</li>
<li><code>select</code>-s with empty values are not</li>
<li>The plugin’s checkbox in Screen Options is effective immediately</li>
<li>The code is designed as a must use plugin, so there is no separated Javascript or CSS file</li>
<li>State of Machine Language is saved as a user option so it is a per user setting</li>
</ul>
<h4>Links</h4>
<p>Development goes on on <a href="https://github.com/szepeviktor/machine-language" rel="nofollow ugc">GitHub</a>.</p>


TIVWP-DM Development Manager vs Machine Language