WP Superstar

Managing WooCommerce With The YITH Frontend Manager For WooCommerce Plugin

If managing your WooCommerce Store isn’t time consuming enough, imagine having to train new personnel on what they can do or should do when they access your Website’s back-end. YITH saw there was a need to allow collaborators and even store managers to be able to add and edit products without ever having access to the back-end. Say hello to the “YITH Frontend Manager For WooCommerce” plugin.

YITH Frontend Manager For WooCommerce Plugin

The YITH Frontend Manager For WooCommerce plugin allows you to:

Enable Front-End Shop Management for Your Site
It will provide a Shop manager with an interactive, feature-rich dashboard allowing to update many aspects of your WooCommerce Store.
Restrict Shop Manager’s Back-End Access
Prevent All Shop Managers From Having Access To The Site Back-end. Your WooCommerce Store will be completely managed from the Front-End of your Website.
Choose Shop Sections To Enable In The Front-End
That’s right, you can easily enable or disable which WooCommerce Modules are displayed to Shop Managers. Modules include Coupons, Dashboard, Logout, Orders, Products and Reports.
Manage Unauthorized Access
Keep those without access out of your Website. Show them you mean business by displaying a customizable error message.
Enable WordPress Admin Bar
Enable the WordPress Admin Bar for Shop Managers so they can quickly get to the Front-End Dashboard.
Edit The Endpoints Of Each SectionChange the Endpoints/Urls to specific sections. For example, the default endpoint to manage Coupons is /coupon/. This option would allow you to change it to something like /coupon-management/.
Choose The Skin To Be Used For The Dashboard

The YITH Frontend Manager For WooCommerce Plugin In Combination With YITH Multi Vendor Can

Enable All Vendors To Access The Front-End Dashboard
Choose Which Sections To Enable For Vendors
Prevent All Vendors From Accessing WordPress Dashboard

YITH Frontend Manager For WooCommerce Is Developer Friendly

The YITH Frontend Manager For WooCommerce plugin is developer friendly. It contains a significant number of actions and filters that you can use to make it your own and customize it to your needs. A quick example of this can be seen below, where we are changing the capability required to view the Front-End manager to those who have upload_files permissions. In a real world application, this could be a capability registered by your own plugin.

// Set new Capability required to access the Front-End Manager
add_filter( 'yith_wcfm_access_capability', 'enable_custom_frontend_manager_access', 10, 1 );
function enable_custom_frontend_manager_access( $plugin_capability ) {
	// Set new capability
	return 'upload_files';
}

// Set new Capability required to access the Front-End Manager

add_filter( 'yith_wcfm_access_capability', 'enable_custom_frontend_manager_access', 10, 1 );

function enable_custom_frontend_manager_access( $plugin_capability ) {

// Set new capability

return 'upload_files';

}

Speed Up Large WordPress & WooCommerce Website Back-End

Last week while trying to find ways to improve KelbyOne’s Website speed, I came across a particular query being ran on the back-end that was responsible for slowing it down. Every time you tried loading an Order, Course, Lesson, Subscription or anything else, that query was responsible for almost 80% of the time it took to load.

The query was discovered using the latest version of Query Monitor. What did the query do, it goes through the whole postmeta table and tries to find every different meta_key found for a particular post_type. Needless to say if you have a large postmeta table with millions of records, this query will take a long time to run.

Results from the query populate the Custom Fields metabox select menu so that you can easily add new custom fields with a few clicks. Keep in mind that if you add this code to your Website, the select menu will not be populated anymore. Also, any custom fields added to the post will still show in Custom Fields metabox and you’ll have the “Add New Custom Field” interface to add any fields if you need to.

I was able to reduce page load times from around 27 seconds down to 4-5 seconds. How is this beneficial? Simple. The less time the server is busy running the query the more resources available to your visitors. Also, if you have a lot of people going in the back-end for things like Customer Service, they’ll thank you, too.

Enough rambling, here is the code.

add_filter( 'postmeta_form_limit', 'limit_postmeta_keys_to_zero', 10, 1 );
function limit_postmeta_keys_to_zero( $limit ) {
	global $post;
	// Only for these post types
	$valid_post_types = array(
		// WooCommerce Subscriptions
		'shop_subscription',
		// WooCommerce
		'shop_order',
		'shop_coupon',
		// Sensei
		'course',
		'lesson',
		// WordPress
		'page',
		'post'
	);

	if( is_admin() ):
		if( in_array( $post->post_type, $valid_post_types ) ) {
			return 0;
		}
	endif;

	return $limit;
}

add_filter( 'postmeta_form_limit', 'limit_postmeta_keys_to_zero', 10, 1 );

function limit_postmeta_keys_to_zero( $limit ) {

global $post;

// Only for these post types

$valid_post_types = array(

// WooCommerce Subscriptions

'shop_subscription',

// WooCommerce

'shop_order',

'shop_coupon',

// Sensei

'course',

'lesson',

// WordPress

'page',

'post'

);

if( is_admin() ):

if( in_array( $post->post_type, $valid_post_types ) ) {

return 0;

}

endif;

return $limit;

}

LearnDash Zapier Integration: Sending Additional User Information

I was recently hired at Codeable to write a plugin which would allow the LearnDash Zapier Integration plugin to pass additional user information with every call made to Zapier. This information needed to happen whenever global user even happened, like completing a quiz, for example. Upon reviewing the plugin, I noticed there was no filter that would allow me to pass in this additional data or an action to alter it’s default behavior.

Luckily the plugin was using WordPress’ HTTP API and I knew if I could listen to every request being made to an external site, then I could check whether or not the call was being made to Zapier and add my data there. This is exactly what I ended up doing. I’m posting this hoping that it will help someone else who needs to do this and you should get in touch with LearnDash like I did in order to ask for a filter to be added to the already existing plugin. It wouldn’t take more than 5 minutes to add a filter and open the request so that you can pass your own data.

Below is the plugin I wrote to pass a single field the User object being sent to Zapier. You can use the same technique and add as many as you’d like.

<?php
/*
Plugin Name: LearnDash Zapier Integration: Additional User Fields
Plugin URI: https://www.wpsuperstar.com/
Description: Extends LearnDash Zapier Integration by including custom data from a specific user with every request sent to Zapier
Version: 1.0
Author: Yojance Rabelo
Author URI: https://www.wpsuperstar.com/
*/

class LearnDash_Zapier_Additional_User_Fields {

    /**
     * @var null
     */
    protected static $instance = null;
    /**
     * This is what we are looking for in the Zapier hook URL
     *
     * @var string
     */
    public $needle = 'zapier.com';

    /**
     * LearnDash_Zapier_Additional_User_Fields constructor.
     */
    public function __construct() {
        $this->hooks();
    }

    /**
     * Make sure this is a singleton class
     *
     * @return LearnDash_Zapier_Additional_User_Fields|null
     */
    public static function instance() {
        if ( is_null( self::$instance ) ) {
            self::$instance = new self();
        }
        return self::$instance;
    }

    /**
     * WordPress Hooks
     */
    public function hooks() {
        // Low level function listening to all calls and making
        // sure it appends whatever data we need whenever a request
        // is sent to Zapier
        add_filter( 'http_request_args', array( $this, 'append_custom_user_data' ), 100, 2 );
    }

    /**
     * Low level function listening to all calls and making sure it appends
     * necessary custom data whenever a request is sent to Zapier
     *
     * @param $arguments
     * @param $url
     * @return mixed
     */
    public function append_custom_user_data( $arguments, $url ) {
        // Make sure these exists to prevent errors
        if( function_exists( 'ld_zapier_send_trigger' ) && function_exists( 'ld_zapier_post' ) ) {
            // Is it a LearnDash ---> Zapier Request?
            $is_learndash_zapier_request = strpos( $url, $this->needle );

            // Is it now?
            if( $is_learndash_zapier_request !== false ) {

                // Get the user ID
                $user_id = $arguments['body']['user']->ID;

                // Get the custom field from this customer's meta
                $custom_field = get_user_meta( $user_id, 'custom-field-key', true );

                // Append the new field
                $arguments['body']['user']->custom_field = $custom_field;

                // Return the newly modified user object
                return $arguments;
            }
        }

        // Return the default arguments or newly modified set of arguments
        return $arguments;
    }
}

function ld_zapier_additional_user_fields() {
    return LearnDash_Zapier_Additional_User_Fields::instance();
}
add_action( 'plugins_loaded', 'ld_zapier_additional_user_fields' );

<?php

Plugin Name: LearnDash Zapier Integration: Additional User Fields

Plugin URI: https://www.wpsuperstar.com/

Description: Extends LearnDash Zapier Integration by including custom data from a specific user with every request sent to Zapier

Version: 1.0

Author: Yojance Rabelo

Author URI: https://www.wpsuperstar.com/

class LearnDash_Zapier_Additional_User_Fields {

/**

* @var null

protected static $instance = null;

/**

* This is what we are looking for in the Zapier hook URL

* @var string

public $needle = 'zapier.com';

/**

* LearnDash_Zapier_Additional_User_Fields constructor.

public function __construct() {

$this->hooks();

}

/**

* Make sure this is a singleton class

* @return LearnDash_Zapier_Additional_User_Fields|null

public static function instance() {

if ( is_null( self::$instance ) ) {

self::$instance = new self();

}

return self::$instance;

}

/**

* WordPress Hooks

public function hooks() {

// Low level function listening to all calls and making

// sure it appends whatever data we need whenever a request

// is sent to Zapier

add_filter( 'http_request_args', array( $this, 'append_custom_user_data' ), 100, 2 );

}

/**

* Low level function listening to all calls and making sure it appends

* necessary custom data whenever a request is sent to Zapier

* @param $arguments

* @param $url

* @return mixed

public function append_custom_user_data( $arguments, $url ) {

// Make sure these exists to prevent errors

if( function_exists( 'ld_zapier_send_trigger' ) && function_exists( 'ld_zapier_post' ) ) {

// Is it a LearnDash ---> Zapier Request?

$is_learndash_zapier_request = strpos( $url, $this->needle );

// Is it now?

if( $is_learndash_zapier_request !== false ) {

// Get the user ID

$user_id = $arguments['body']['user']->ID;

// Get the custom field from this customer's meta

$custom_field = get_user_meta( $user_id, 'custom-field-key', true );

// Append the new field

$arguments['body']['user']->custom_field = $custom_field;

// Return the newly modified user object

return $arguments;

}

// Return the default arguments or newly modified set of arguments

return $arguments;

}

function ld_zapier_additional_user_fields() {

return LearnDash_Zapier_Additional_User_Fields::instance();

}

add_action( 'plugins_loaded', 'ld_zapier_additional_user_fields' );

There you have it, nice and simple.

Faster AJax Calls In WordPress By Using The AjaxFlow Plugin

Is it possible to achieve faster Ajax Calls in WordPress? You bet it is possible and you can start doing it right now with very little edits to the code you already have in place. We are going to be using a little plugin called AjaxFlow to speed it up, but first let’s go over the regular, slow way of doing Ajax Calls in WordPress.

Meet Ajaxflow

By installing this plugin in your Website, your Ajax calls will be so fast you’ll think it’s sorcery, but it is not, I think it’s not. All kidding aside, the plugin basically tells WordPress to load the bare minimum instead of loading the whole WordPress environment, thus speeding everything up and resulting in much faster Ajax calls. I’m talking calls that would normally would take 3-5 seconds on a good server down to 100-300 milliseconds.

How To Use Use AjaxFlow

Using AjaxFlow is super easy, and if you are already using regular Ajax calls within WordPress using wp_ajax_nopriv_$action and wp_ajax_$action, converting to AjaxFlow can be done in minutes.

What Are The Differences?

Ajax calls need to be made to /ajaxflow/$action, meaning that /wp-admin/admin-ajax.php is no longer used.
Passing the action parameter in your Ajax request is no longer necessary since we include the action in the call endpoint as explained above
ajaxflow_nopriv_$action and ajaxflow_$action must be used in your PHP code instead of using wp_ajax_nopriv_$action and wp_ajax_$action

AjaxFlow Example

jQuery.ajax({
    type: 'POST',
    url: '/ajaxflow/get_subcategories',
    data: { parent_id: top_category },
    success: function( data, textStatus, jqXHR  ) {
        // Do Some stuff with data
    },
    error: function( jqXHR, textStatus, errorThrown ) {
    }
});

jQuery.ajax({

type: 'POST',

url: '/ajaxflow/get_subcategories',

data: { parent_id: top_category },

success: function( data, textStatus, jqXHR ) {

// Do Some stuff with data

error: function( jqXHR, textStatus, errorThrown ) {

}

});

// Add actions in your class constructor
add_action( 'ajaxflow_get_subcategories',               array( $this, 'get_subcategories' ) );
add_action( 'ajaxflow_nopriv_get_subcategories',        array( $this, 'get_subcategories' ) );

// Function to handle the Ajax call
public function get_subcategories() {
        
}

// Add actions in your class constructor

add_action( 'ajaxflow_get_subcategories', array( $this, 'get_subcategories' ) );

add_action( 'ajaxflow_nopriv_get_subcategories', array( $this, 'get_subcategories' ) );

// Function to handle the Ajax call

public function get_subcategories() {

}

If for some reason you get an error message other than zero saying your call $action doesn’t exists, then it means you have forgotten to add the Ajax handler in the back-end or you didn’t add it properly since it can’t find it.

That’s it, give it a try and watch your Ajax calls fly.

Connecting WooCommerce To Salesforce: OAuth2 Authorization

Along with learning Typescript in the fast few months, I’ve also been putting a lot of time an energy into learning Salesforce and the Apex language. So far it has been an amazing journey and my end goal for learning Salesforce is so that I can write REST APIs that would synchronize WooCommerce and Salesforce seamlessly.

With that purpose in mind, I realized doing something like this is no easy task or something you can write in a day or two and never have to touch it again, specially since the whole ecosystem (WordPress, WooCommerce, Salesforce) gets updated very frequent and things change all the time. I’ve taken the approach of dividing this humongous task into smaller modules that would help me accomplish this in faster and more maintainable way. Being able to re-use the components and sort of add or delete them as needed is what I’m after and the first step would be to establish a connection with Salesforce so that I can begin sending my Requests.

Since this would be tied to WooCommerce on this side, I figured I would do it the WordPress/WooCommerce way so I wrote a little plugin that integrates with WooCommerce and handles the saving of all the data received from Salesforce after the initial oAuth2 authorization and saves it to the database for later use. Note that this part doesn’t include the option the revoke the token or to send the refresh token in order to obtain a new access token once the old one has expired.

Register Our Integration With WooCommerce

Let’s start coding and register our registration with WooCommerce so that it appears under the WooCommerce -> Settings -> Integrations tab. This file’s sole purpose is to help WooCommerce know this is an integration and to load other PHP Classes we are going to be using. The actual fields, settings and any other logic will be in another file.

<?php
/**
 * Plugin Name: WooCommerce To Salesforce Integration
 * Plugin URI: https://www.wpsuperstar.com/
 * Description: Connects WooCommerce to Salesforce
 * Version: 0.0.1
 * Author: Yojacnce Rabelo
 * Author URI: https://www.wpsuperstar.com/
 *
 */
if ( ! defined( 'ABSPATH' ) ) {
    exit; // Exit if accessed directly
}

if ( ! class_exists( 'WooCommerce_Salesforce_Integration' ) ) :

    define( 'WC_SF_OAUTH2_PATH',   wp_normalize_path( plugin_dir_path( __FILE__ ) ) );
    define( 'WC_SF_OAUTH2_URL',    plugin_dir_url( __FILE__ ) );

    /**
     * Register the WooCommerce/Salesforce Integration Class
     */
    class WooCommerce_Salesforce_Integration {

        /**
         * Construct the plugin.
         */
        public function __construct() {
            add_action( 'plugins_loaded', array( $this, 'init' ) );
        }

        /**
         * Initialize the Plugin
         */
        public function init() {

            // Checks if WooCommerce is installed.
            if ( class_exists( 'WC_Integration' ) ) {
                // Include our integration class.
                include_once WC_SF_OAUTH2_PATH . 'class-woocommerce-salesforce-integration.php';
                include_once WC_SF_OAUTH2_PATH . 'includes/class-endpoints.php';
                include_once WC_SF_OAUTH2_PATH . 'includes/class-authorization.php';

                $this->oauth2_endpoints = new WC_SF_OAUTH2_EndPoints();
                $this->oauth2_authorization = new WC_SF_OAUTH2_Authorization();

                // Register the integration.
                add_filter( 'woocommerce_integrations', array( $this, 'add_integration' ), 10, 1 );

                // Include the rest of the files here as necessary
            } else {
                // throw an admin error if you like
            }
        }

        /**
         * Register the WooCommerce/Salesforce Integration
         *
         * @param $integrations
         * @return array
         */
        public function add_integration( $integrations ) {
            $integrations[] = 'WC_OAUTH2_SF';
            return $integrations;
        }
    }

    $woocommerce_salesforce_integration = new WooCommerce_Salesforce_Integration( __FILE__ );

endif;

<?php

/**

* Plugin Name: WooCommerce To Salesforce Integration

* Plugin URI: https://www.wpsuperstar.com/

* Description: Connects WooCommerce to Salesforce

* Version: 0.0.1

* Author: Yojacnce Rabelo

* Author URI: https://www.wpsuperstar.com/

if ( ! defined( 'ABSPATH' ) ) {

exit; // Exit if accessed directly

}

if ( ! class_exists( 'WooCommerce_Salesforce_Integration' ) ) :

define( 'WC_SF_OAUTH2_PATH', wp_normalize_path( plugin_dir_path( __FILE__ ) ) );

define( 'WC_SF_OAUTH2_URL', plugin_dir_url( __FILE__ ) );

/**

* Register the WooCommerce/Salesforce Integration Class

class WooCommerce_Salesforce_Integration {

/**

* Construct the plugin.

public function __construct() {

add_action( 'plugins_loaded', array( $this, 'init' ) );

}

/**

* Initialize the Plugin

public function init() {

// Checks if WooCommerce is installed.

if ( class_exists( 'WC_Integration' ) ) {

// Include our integration class.

include_once WC_SF_OAUTH2_PATH . 'class-woocommerce-salesforce-integration.php';

include_once WC_SF_OAUTH2_PATH . 'includes/class-endpoints.php';

include_once WC_SF_OAUTH2_PATH . 'includes/class-authorization.php';

$this->oauth2_endpoints = new WC_SF_OAUTH2_EndPoints();

$this->oauth2_authorization = new WC_SF_OAUTH2_Authorization();

// Register the integration.

add_filter( 'woocommerce_integrations', array( $this, 'add_integration' ), 10, 1 );

// Include the rest of the files here as necessary

} else {

// throw an admin error if you like

}

/**

* Register the WooCommerce/Salesforce Integration

* @param $integrations

* @return array

public function add_integration( $integrations ) {

$integrations[] = 'WC_OAUTH2_SF';

return $integrations;

}

$woocommerce_salesforce_integration = new WooCommerce_Salesforce_Integration( __FILE__ );

endif;

Integration Fields Using WooCommerce’s Settings API

Everything is pretty standard, just a few fields to save our the values we get back from Salesforce.

SF App Consumer Key
SF App Consumer Secret
SF Login URI
SF oAuth2 Token
Salesforce Token (Not actually used to communicate back and forth but it was used for obtaining the Access Token
SF Access Token
Access token sent with every request for authenticating purposes.
SF Refresh Token
Refresh token used whenever the Access Token needs to be renewed/refreshed
SF Instance URI
All REST Request will be send to this base Uri.
Debug Log
Log events such as API requests

<?php

/**
 * Class WC_OAUTH2_SF
 */
class WC_OAUTH2_SF extends WC_Integration {

    public $text_domain = 'wcsf_oauth2';

    /**
     * WC_OAUTH2_SF constructor
     */
    public function __construct() {

        $this->id                 = 'wc_sf_oauth2';
        $this->method_title       = __( 'WooCommerce to Salesforce Connection', $this->text_domain );
        $this->method_description = __( 'Connects WooCommerce to Salesforce', $this->text_domain );

        // Load the settings.
        $this->init_form_fields();
        $this->init_settings();

        // Make sure the settings get saved
        add_action( 'woocommerce_update_options_integration_' .  $this->id, array( $this, 'process_admin_options' ) );
    }

    /**
     * Initialize integration settings form fields.
     */
    public function init_form_fields() {
        $this->form_fields = array(
            'consumer_key' => array(
                'title'             => __( 'SF App Consumer Key', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( '', $this->text_domain ),
                'desc_tip'          => true,
            ),
            'consumer_secret' => array(
                'title'             => __( 'SF App Consumer Secret', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( '', $this->text_domain ),
                'desc_tip'          => true,
            ),
            'login_uri' => array(
                'title'             => __( 'SF Login URI', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( '', $this->text_domain ),
                'desc_tip'          => true,
            ),
            'oath2_token' => array(
                'title'             => __( 'SF oAuth2 Token', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( 'Salesforce Token (Not actually used to communicate back and forth but it was used for obtaining the Access Token', $this->text_domain ),
                'desc_tip'          => true,
            ),
            'access_token' => array(
                'title'             => __( 'SF Access Token', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( 'Access token sent with every request for authenticating purposes.', $this->text_domain ),
                'desc_tip'          => true
            ),
            'refresh_token' => array(
                'title'             => __( 'SF Refresh Token', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( 'Refresh token used whenever the Access Token needs to be renewed.', $this->text_domain ),
                'desc_tip'          => true
            ),
            'instance_uri' => array(
                'title'             => __( 'SF Instance URI', $this->text_domain ),
                'type'              => 'text',
                'description'       => __( 'All REST Request will be send to this base Uri.', $this->text_domain ),
                'desc_tip'          => true
            ),
            // Will be used in the future
            'debug' => array(
                'title'             => __( 'Debug Log', $this->text_domain ),
                'type'              => 'checkbox',
                'label'             => __( 'Enable logging', $this->text_domain ),
                'default'           => 'no',
                'description'       => __( 'Log events such as API requests', $this->text_domain ),
            ),
        );
    }
}

<?php

/**

* Class WC_OAUTH2_SF

class WC_OAUTH2_SF extends WC_Integration {

public $text_domain = 'wcsf_oauth2';

/**

* WC_OAUTH2_SF constructor

public function __construct() {

$this->id = 'wc_sf_oauth2';

$this->method_title = __( 'WooCommerce to Salesforce Connection', $this->text_domain );

$this->method_description = __( 'Connects WooCommerce to Salesforce', $this->text_domain );

// Load the settings.

$this->init_form_fields();

$this->init_settings();

// Make sure the settings get saved

add_action( 'woocommerce_update_options_integration_' . $this->id, array( $this, 'process_admin_options' ) );

}

/**

* Initialize integration settings form fields.

public function init_form_fields() {

$this->form_fields = array(

'consumer_key' => array(

'title' => __( 'SF App Consumer Key', $this->text_domain ),

'type' => 'text',

'description' => __( '', $this->text_domain ),

'desc_tip' => true,

'consumer_secret' => array(

'title' => __( 'SF App Consumer Secret', $this->text_domain ),

'type' => 'text',

'description' => __( '', $this->text_domain ),

'desc_tip' => true,

'login_uri' => array(

'title' => __( 'SF Login URI', $this->text_domain ),

'type' => 'text',

'description' => __( '', $this->text_domain ),

'desc_tip' => true,

'oath2_token' => array(

'title' => __( 'SF oAuth2 Token', $this->text_domain ),

'type' => 'text',

'description' => __( 'Salesforce Token (Not actually used to communicate back and forth but it was used for obtaining the Access Token', $this->text_domain ),

'desc_tip' => true,

'access_token' => array(

'title' => __( 'SF Access Token', $this->text_domain ),

'type' => 'text',

'description' => __( 'Access token sent with every request for authenticating purposes.', $this->text_domain ),

'desc_tip' => true

'refresh_token' => array(

'title' => __( 'SF Refresh Token', $this->text_domain ),

'type' => 'text',

'description' => __( 'Refresh token used whenever the Access Token needs to be renewed.', $this->text_domain ),

'desc_tip' => true

'instance_uri' => array(

'title' => __( 'SF Instance URI', $this->text_domain ),

'type' => 'text',

'description' => __( 'All REST Request will be send to this base Uri.', $this->text_domain ),

'desc_tip' => true

// Will be used in the future

'debug' => array(

'title' => __( 'Debug Log', $this->text_domain ),

'type' => 'checkbox',

'label' => __( 'Enable logging', $this->text_domain ),

'default' => 'no',

'description' => __( 'Log events such as API requests', $this->text_domain ),

);

}

Register Custom WordPress Endpoints

Next we register 2 endpoints which are used in the 2 step process. What follows takes care of registering two endpoints, oauth2 and oauth2-step2. It will also add some quick and dirty logic to overriding what each of these endpoints display. These templates are called authorization-step-1.php and authorization-step-2.php.

<?php
<?php

/**
* Class WC_SF_EndPoints
*/
class WC_SF_EndPoints {

    protected $settings_key_id = 'woocommerce_wc_sf_settings';
    
    public function __construct() {
        $this->includes();
        $this->hooks();
    }
    
    public function includes() {	}
    
    
    /**
    * WordPress Hooks
    */
    public function hooks() {
        // Add the oauth2 Endpoint
        add_action( 'init',                                 array( $this, 'register_authorization_endpoints' ) );
        // Create custom templates for endpoints
        add_action( 'template_redirect',                    array( $this, 'register_custom_template_authorization_step_1' ) );
        add_action( 'template_redirect',                    array( $this, 'register_custom_template_authorization_step_2' ) );
    }
    
    /**
    * Register the endpoints for the Salesforce 2 Step oAuth2 authorization process
    */
    public function register_authorization_endpoints() {
        // register a "json" endpoint to be applied to posts and pages
        add_rewrite_endpoint( 'oauth2', EP_ROOT );
        add_rewrite_endpoint( 'oauth2-step2', EP_ROOT );
    }
    
    /**
    * Register template for the Step 1 of the oAuth2 Authorization
    */
    public function register_custom_template_authorization_step_1() {
        global $wp_query;
        
        if( isset( $wp_query->query_vars['oauth2'] ) ) {
            // include custom template
            include WC_SF_PATH . 'frontend/authorization-step-1.php';
            exit;
        }
    }
    
    /**
    * Register template for the Step 2 of the oAuth2 Authorization
    */
    public function register_custom_template_authorization_step_2() {
    
        global $wp_query;
        
        if( isset( $wp_query->query_vars['oauth2-step2'] ) ) {
            // include custom template
            include WC_SF_PATH . 'frontend/authorization-step-2.php';
            exit;
        }
    }
}

<?php

/**

* Class WC_SF_EndPoints

class WC_SF_EndPoints {

protected $settings_key_id = 'woocommerce_wc_sf_settings';

public function __construct() {

$this->includes();

$this->hooks();

}

public function includes() { }

/**

* WordPress Hooks

public function hooks() {

// Add the oauth2 Endpoint

add_action( 'init', array( $this, 'register_authorization_endpoints' ) );

// Create custom templates for endpoints

add_action( 'template_redirect', array( $this, 'register_custom_template_authorization_step_1' ) );

add_action( 'template_redirect', array( $this, 'register_custom_template_authorization_step_2' ) );

}

/**

* Register the endpoints for the Salesforce 2 Step oAuth2 authorization process

public function register_authorization_endpoints() {

// register a "json" endpoint to be applied to posts and pages

add_rewrite_endpoint( 'oauth2', EP_ROOT );

add_rewrite_endpoint( 'oauth2-step2', EP_ROOT );

}

/**

* Register template for the Step 1 of the oAuth2 Authorization

public function register_custom_template_authorization_step_1() {

global $wp_query;

if( isset( $wp_query->query_vars['oauth2'] ) ) {

// include custom template

include WC_SF_PATH . 'frontend/authorization-step-1.php';

exit;

}

/**

* Register template for the Step 2 of the oAuth2 Authorization

public function register_custom_template_authorization_step_2() {

global $wp_query;

if( isset( $wp_query->query_vars['oauth2-step2'] ) ) {

// include custom template

include WC_SF_PATH . 'frontend/authorization-step-2.php';

exit;

}

Endpoint Templates

Finally, these are the layouts for those 2 endpoints.

<!DOCTYPE html>

<html lang="en">

<head>

    <meta charset="utf-8">

    <meta http-equiv="X-UA-Compatible" content="IE=edge">

    <meta name="viewport" content="width=device-width, initial-scale=1">

    <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->

    <title>WooCommerce To Salesforce — Authorization Process</title>


    <!-- Bootstrap -->

    <link href="<?php echo WC_SF_URL; ?>assets/css/bootstrap.min.css" rel="stylesheet">

    <link href="<?php echo WC_SF_URL; ?>assets/css/bootstrap-theme.min.css" rel="stylesheet">


    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->

    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->

    <!--[if lt IE 9]>

    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>

    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>

    <![endif]-->

</head>

<body>


<div id="authorization-page" class="container"
     style="background: #f5f5f5; border: 1px solid #ccc; padding:50px;margin-top:100px;">

    <div class="row">

        <h2>WooCommerce To Salesforce
            <small>Authorization Process</small>
        </h2>

        <hr/>

        <div class="col-xs-12 col-sm-6">

            <p class="lead">Please use this page to complete the initial WooCommerce To Salesforce Authorization
                Process</p>

            <p>Please enter your Consumer Key. This Consumer key must be obtain from the Salesforce App you created. If
                you haven't created one yet, please go ahead and do so. Login to your Salesforce account and then click
                on <strong>"Setup => Create => Apps => New."</strong></p>

            <p>If you already have an App created bu don't know where to get this information, the login to your
                Salesforce and go to <strong>"Setup => Create => Apps"</strong>. In the Conencted Apps section, click
                <strong>"Edit"</strong> next to the App you previously created and on the new "Edit Screen" just hit the
                save button. On this new screen you can get your Consumer Key and Consumer Secret. Please store these in
                a save place.</p>

        </div>

        <div class="col-xs-12 col-sm-6">

            <form method="post" action="<?php echo $_SERVER['PHP_SELF']; ?>">

                <p>

                    <label for="authorization-app-consumer-key">SF App Consumer Key</label>

                    <input type="text" class="form-control" name="authorization-app-consumer-key"
                           id="authorization-app-consumer-key" required/>

                </p>

                <p>

                    <label for="authorization-app-consumer-secret">SF App Consumer Secret</label>

                    <input type="text" class="form-control" name="authorization-app-consumer-secret"
                           id="authorization-app-consumer-secret" required/>

                </p>

                <p>

                    <label for="authorization-login-uri">SF Login URI</label>

                    <input type="text" class="form-control" readonly="readonly" name="authorization-login-uri"
                           id="authorization-login-uri" value="https://login.salesforce.com"/>

                </p>

                <p>

                    <label for="authorization-step-2-uri">Step 2 URI</label>

                    <input value="<?php echo home_url('/'); ?>oauth2-step2/" type="text" class="form-control"
                           readonly="readonly" name="authorization-step-2-uri" id="authorization-step-2-uri"/>

                </p>

                <hr/>

                <p><input type="submit" class="btn btn-primary" name="authorization-step-1" value="Proceed To Step 2"/>
                </p>

            </form>

        </div>

    </div>

</div>


<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->

<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>

<!-- Include all compiled plugins (below), or include individual files as needed -->

<script src="<?php echo WC_SF_URL; ?>assets/js/bootstrap.min.js"></script>

</body>

</html>

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

120

121

122

123

124

125

126

127

128

129

130

131

132

133

134

<!DOCTYPE html>

<head>

<title>WooCommerce To Salesforce — Authorization Process</title>

<!--[if lt IE 9]>

<![endif]-->

</head>

<body>

<div id="authorization-page" class="container"

style="background: #f5f5f5; border: 1px solid #ccc; padding:50px;margin-top:100px;">

<h2>WooCommerce To Salesforce

<small>Authorization Process</small>

</h2>

<hr/>

<p class="lead">Please use this page to complete the initial WooCommerce To Salesforce Authorization

Process</p>

<p>Please enter your Consumer Key. This Consumer key must be obtain from the Salesforce App you created. If

you haven't created one yet, please go ahead and do so. Login to your Salesforce account and then click

on <strong>"Setup => Create => Apps => New."</strong></p>

<p>If you already have an App created bu don't know where to get this information, the login to your

Salesforce and go to <strong>"Setup => Create => Apps"</strong>. In the Conencted Apps section, click

<strong>"Edit"</strong> next to the App you previously created and on the new "Edit Screen" just hit the

save button. On this new screen you can get your Consumer Key and Consumer Secret. Please store these in

a save place.</p>

</div>

<p>

<label for="authorization-app-consumer-key">SF App Consumer Key</label>

<input type="text" class="form-control" name="authorization-app-consumer-key"

id="authorization-app-consumer-key" required/>

</p>

<p>

<label for="authorization-app-consumer-secret">SF App Consumer Secret</label>

<input type="text" class="form-control" name="authorization-app-consumer-secret"

id="authorization-app-consumer-secret" required/>

</p>

<p>

<label for="authorization-login-uri">SF Login URI</label>

<input type="text" class="form-control" readonly="readonly" name="authorization-login-uri"

id="authorization-login-uri" value="https://login.salesforce.com"/>

</p>

<p>

<input value="<?php echo home_url('/'); ?>oauth2-step2/" type="text" class="form-control"

readonly="readonly" name="authorization-step-2-uri" id="authorization-step-2-uri"/>

</p>

<hr/>

</p>

</form>

</div>

</body>

</html>

<!DOCTYPE html>

<html lang="en">

<head>

    <meta charset="utf-8">

    <meta http-equiv="X-UA-Compatible" content="IE=edge">

    <meta name="viewport" content="width=device-width, initial-scale=1">

    <!-- The above 3 meta tags *must* come first in the head; any other head content must come *after* these tags -->

    <title>WooCommerce To Salesforce — Authorization Process (Step 2)</title>


    <!-- Bootstrap -->

    <link href="<?php echo WC_SF_URL; ?>assets/css/bootstrap.min.css" rel="stylesheet">

    <link href="<?php echo WC_SF_URL; ?>assets/css/bootstrap-theme.min.css" rel="stylesheet">


    <!-- HTML5 shim and Respond.js for IE8 support of HTML5 elements and media queries -->

    <!-- WARNING: Respond.js doesn't work if you view the page via file:// -->

    <!--[if lt IE 9]>

    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>

    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>

    <![endif]-->

</head>

<body>


<div id="authorization-page" class="container">

    <div class="row">

        <h2>WooCommerce To Salesforce
            <small>Authorization Process (Step 2)</small>
        </h2>

        <p>All done! Please make sure that the following settings have been saved to this instance of the WooCommerce To
            Salesforce Integration.</p>

        <ul>

            <li>Salesforce App Consumer Key</li>

            <li>Salesforce App Consumer Secret</li>

            <li>Salesforce Login URI</li>

            <li>Salesforce oAuth2 Token</li>

            <li>Salesforce Access Token</li>

            <li>Salesforce Refresh Token</li>

            <li>Salesforce Instance URI</li>

        </ul>


        <hr/>

    </div>

</div>


<!-- jQuery (necessary for Bootstrap's JavaScript plugins) -->

<script src="https://ajax.googleapis.com/ajax/libs/jquery/1.11.3/jquery.min.js"></script>

<!-- Include all compiled plugins (below), or include individual files as needed -->

<script src="<?php echo WC_SF_URL; ?>assets/js/bootstrap.min.js"></script>

</body>

</html>

<!DOCTYPE html>

<head>

<title>WooCommerce To Salesforce — Authorization Process (Step 2)</title>

<!--[if lt IE 9]>

<![endif]-->

</head>

<body>

<h2>WooCommerce To Salesforce

<small>Authorization Process (Step 2)</small>

</h2>

<p>All done! Please make sure that the following settings have been saved to this instance of the WooCommerce To

Salesforce Integration.</p>

<ul>

<li>Salesforce App Consumer Key</li>

<li>Salesforce App Consumer Secret</li>

<li>Salesforce Login URI</li>

<li>Salesforce oAuth2 Token</li>

<li>Salesforce Access Token</li>

<li>Salesforce Refresh Token</li>

<li>Salesforce Instance URI</li>

</ul>

<hr/>

</div>

</body>

</html>

Download WooCommerce To Salesforce Integration: Initial Integration

WooCommerce To Salesforce Integration: Initial Integration