axiomattik

<p>PocketGecko Email provides a settings page <code>(Settings -> Email)</code> to connect WordPress to an email server using basic authentication (username/password). This allows any other plugin that uses <code>wp_mail</code> to function correctly.</p>
<p>PocketGecko Email also provides the shortcode <code>[pocketgecko-email]</code> which renders a simple HTML form for sending email. This form supports custom recipients, carbon copies, blind carbon copies, and sending emails with one or more attachments. Any attachments sent using PocketGecko Email are automatically uploaded to the Media Library.</p>
<p>Full functionality is restricted to users who possess the ‘publish_posts’ capability. Users, including guests, who do not have this capability cannot send carbon copies or blind carbon copies, and are restricted to sending emails back to the account used to send them.</p>
<p>By default, PocketGecko Email attempts to ‘ajaxify’ the HTML form to provide an interactive user experience. If, however, JavaScript is not available, then the form will fallback to using POST instead.</p>
<p>Two <code>send_email</code> endpoints are created at <code>/wp-admin/admin-post.php</code> and <code>/wp-admin/admin-ajax.php</code>. These can be used by other plugins or in your own custom functions.php, JavaScript or HTML to send emails. For security reasons, use of the endpoints must be authenticated with a nonce.</p>
<p>There are plans to make the email form available as a Gutenberg block.</p>
<h4>Privacy Notices</h4>
<p>No information about emails sent using PocketGecko Emails is stored by the plugin, except for email attachments which are uploaded to the Media Library.</p>
<h4>Docs and Support</h4>
<p>Documentation is currently in progress and will be made available <a href="https://pocketgecko.co.uk/wp-plugins/email/docs" rel="nofollow ugc">here</a>.</p>
<p>Support is available on the <a href="https://wordpress.org/plugins/search/pocketgecko-email/" rel="ugc">forums</a>.</p>
<h3>Copyright</h3>
<p>Icons provided by fontawesome.com – <a href="https://fontawesome.com/license" rel="nofollow ugc">license</a></p>


PocketGecko Email

Makes it easy to configure and send emails using POST/AJAX.

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

PocketGecko Email vs CFS Options Screens