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

Felipe Elia

<p>CFS Auto Loop Label is a <a href="https://wordpress.org/plugins/custom-field-suite/" rel="ugc">Custom Field Suite</a> addon that takes the first textfield value of each loop and rename it’s row. It’s very useful when you don’t want to have just a list of “Row name” labels in the post edit screen. If no textfield is find, it takes the first textarea value.</p>
<p>You can contribute to the source code in the <a href="https://github.com/felipeelia/cfs-auto-loop-label" rel="nofollow ugc">GitHub page</a>.</p>


CFS Auto Loop Label

Custom Field Suite addon that auto label loops with the first textfield value

CFS Options Screens vs CFS Auto Loop Label