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>


Machine Language

John Huebner

<p><strong><em>Warning: Support for Sub Fields Removed as of Version 4.0.0</em></strong></p>
<p>This is an add on plugin for Advanced Custom Fields (ACF) Version 5.</p>
<p><strong><em>This plugin will not provide any functionality if ACF5 is not installed.</em></strong></p>
<p>This plugin adds a field setting to all field types so that user roles allowed to edit the field can<br />
be selected. Only those roles selected for the field will be able to edit the field.</p>
<h3>Github Repository</h3>
<p>This plugin is also on GitHub<br />
<a href="https://github.com/Hube2/acf-user-role-field-setting" rel="nofollow ugc">https://github.com/Hube2/acf-user-role-field-setting</a></p>
<h3>Excluded Field Types</h3>
<p>Most of the time it would not make sense for a tab field, unless all of the fields in the tab were set the same, in other words, removing a tab should remove all the fields in that tab. That’s not something that I can do at this point.</p>
<p>I’m not sure about the clone field, I haven’t worked with it much. You can test it out if you want.</p>
<p>I have also removed support for repeater, group and flexible content fields because I cannot preserver the values of these fields if they are not editable in the ACF interface. Please note that I do not know what the effect of allowing user role settings on these fields will be.</p>
<p>There is a filter so that you can adjust the types of fields that are excluded. Here is an example</p>
<pre><code><?php 

  add_filter('acf/user_role_setting/exclude_field_types', 'user_role_setting_excluded_field_types');
  function user_role_setting_excluded_field_types($exclude) {
    /* 
      $exclude holds an array of field types to exclude from adding user role settings
      default value:
      $exclude = array('tab' => 'tab', 'clone' => 'clone');
    */

    // remove tab field from exclude
    if (isset($exclude['tab'])) {
      unset($exclude['tab']);
    }

    // add message field to exclude
    $exclude['message'] = 'message';

    return $exclude;
  }

?>
</code></pre>


Machine Language vs ACF User Role Field Setting