Dan-Lucian Stefancu

<p>This plugin will help you quickly set up a standard WordPress settings page for your project, be it a theme or a plugin. That’s it!</p>
<p>Below is a “Hello World” piece of code to quickly get you an idea. It will generate a standard settings page with a checkbox, complete markup, save logic.</p>
<pre><code><?php 
 add_action( 'init', 'my_options_create_page', 11 );  function my_options_create_page() {   $options_page = new Aff();    // Add a checkbox   $options_page->add_field(     array(       'name'        => 'simple_checkbox',       'label'       => __( 'Is this plugin awesome?', 'textdomain' ),       'type'        => 'checkbox',       'description' => __( 'Help your users with a nice description.', 'textdomain' ),       'section'     => 'general', // Optional. Default section. You can add new ones as easily as adding a field.     )   );    // Render the page - this is mandatory   $options_page->init();  ?> </code></pre>
<h4>There are a zillion options plugins out there. Why this?</h4>
<p>All plugins will inevitably have their limitations, but Admin Form Framework is written in form of an object that can be easily extended to suit your needs. This is what we use internally at <a href="http://dreamproduction.com" rel="nofollow ugc">Dream Production</a>.</p>
<h4>Get started</h4>
<p>For a complete example / settings page template, open up the included my_options.php file from <code>examples</code> folder.</p>


Admin Form Framework

This plugin provides a wrapper for the WordPress Settings API that is a much easier, faster and extensible way of building your settings forms.

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>


Admin Form Framework vs Machine Language