Nashwan D

<h4>Important Notes:</h4>
<ol>
<li>This plugin requires at least PHP 5.3.x .</li>
<li>This plugin is for developers, not general users.</li>
</ol>
<p>Nmwdhj is an API for creating, editing and rendering forms programmatically. This plugin doesn’t have a GUI, It’s only a helper library for the PHP & WP developers.</p>
<p>You can use this plugin to create individual form elements in the meta boxes, front-end, or anything else you might want a form for.</p>
<h4>Basic Examples</h4>
<p>You can use this plugin in many ways depending on your needs, this examples only for learning purposes:</p>
<ul>
<li>
<p>Simple WordPress Search Form:</p>
<p>Nmwdhj\create_element( array(     ‘type’  => ‘form’,     ‘atts’  => array(         ‘method’    => ‘GET’,         ‘role’      => ‘search’,         ‘action’    => home_url( ‘/’ ),     ),     ‘elements’  => array(         ‘search’ => array(             ‘name’  => ‘s’,             ‘type’  => ‘input_search’,             ‘value’ => get_search_query(),             ‘atts’  => array(                 ‘placeholder’   => _x( ‘Search this site…’, ‘placeholder’ ),                 ‘class’         => ‘search-text’,                 ‘required’      => true,             ),         ),         ‘submit’ => array(             ‘type’  => ‘input_submit’,             ‘value’ => __( ‘Search’ ),         ),     ), ) )->output();</p>
</li>
<li>
<p>Simple Login Form:</p>
<p>Nmwdhj\create_element( array(     ‘type’  => ‘form’,     ‘atts’  => array(         ‘method’ => ‘POST’,     ), ) ) ->add( array(     ‘name’  => ‘user_name’,     ‘type’  => ‘input_text’,     ‘label’ => __( ‘User Name’ ), ) ) ->add( array(     ‘name’  => ‘user_pass’,     ‘type’  => ‘input_password’,     ‘label’ => __( ‘Password’ ), ) ) ->add( array(     ‘name’  => ‘user_submit’,     ‘type’  => ‘input_submit’,     ‘value’ => __( ‘Submit’ ), ) ) ->output();</p>
</li>
</ul>
<h4>Contributing</h4>
<p>Developers can contribute to the source code on the <a href="https://github.com/nash-ye/Momtaz-Nmwdhj" rel="nofollow ugc">Nmwdhj GitHub Repository</a>.</p>


Nmwdhj

Nmwdhj is an API for creating forms elements via code.

Jon Christopher

<p>Build any number of options screens based on <a href="https://wordpress.org/plugins/custom-field-suite/" rel="ugc">Custom Field Suite</a>.</p>
<h4>For Example</h4>
<p>Begin by creating Field Group(s) you want to include on your options screen. <strong>Be sure to set NO Placement Rules.</strong> Once it’s created, note the post ID it uses. You can then register any number of options screens like so:</p>
<pre><code>function my_cfs_options_screens( $screens ) {
    $screens[] = array(
        'name'            => 'options',
        'menu_title'      => __( 'Site Options' ),
        'page_title'      => __( 'Customize Site Options' ),
        'menu_position'   => 100,
        'icon'            => 'dashicons-admin-generic', // optional, dashicons-admin-generic is the default
        'field_groups'    => array( 'My Field Group' ), // Field Group name(s) of CFS Field Group to use on this page (can also be post IDs)
    );

    return $screens;
}

add_filter( 'cfs_options_screens', 'my_cfs_options_screens' );
</code></pre>
<h4>Retrieve your options like so:</h4>
<pre><code>$value = cfs_get_option( 'options_screen_name', 'cfs_field_name_from_field_group' );
</code></pre>
<p>You can set up multiple top level and/or children options pages by adding a <code>parent</code> argument when registering your screen:</p>
<pre><code>function my_cfs_options_screens( $screens ) {

    // Parent
    $screens[] = array(
        'name'         => 'options',
        'field_groups' => array( 'My Parent Field Group Name' ),
    );

    // Child
    $screens[] = array(
        'name'         => 'options-nav',
        'parent'       => 'options', // name of the parent
        'field_groups' => array( 'My Child Field Group Name' ),
    );

    return $screens;
 }

 add_filter( 'cfs_options_screens', 'my_cfs_options_screens' );
</code></pre>
<p>You can also use CFS Options Screens to set up Field Group ‘defaults’, allowing a Field Group to appear both on a CFS Options Screen and a post edit screen. The CFS Options Screen will act as the default/fallback and the post edit screen will override those defaults.</p>
<pre><code>function my_cfs_options_screens( $screens ) {
    $screens[] = array(
        'name'            => 'options',
        'menu_title'      => __( 'Site Options' ),
        'page_title'      => __( 'Customize Site Options' ),
        'menu_position'   => 100,
        'icon'            => 'dashicons-admin-generic', // optional, dashicons-admin-generic is the default
        'field_groups'    => array(
            array(
                'title'         => 'My CFS Field Group Name',
                'has_overrides' => true,
            ),
        ),
    );

    return $screens;
}

add_filter( 'cfs_options_screens', 'my_cfs_options_screens' );
</code></pre>
<p>Check out the <code>cfs_options_screens_override_note_default</code> and <code>cfs_options_screens_override_note_override</code> filters to customize the messaging for CFS Options Screens overrides.</p>


CFS Options Screens

Create options screens that utilize Custom Field Suite

Nmwdhj vs CFS Options Screens