Readme below:

wp-shopify (WPS) is a Wordpress plugin that integrates the Shopify Buy Button API with Wordpress for easy and powerful store construction.

It consists of two parts:

A syncing tool to keep your Wordpress site connected to your Shopify store, and
A set of templating functions to make building a store and a shopping cart easier.

Installation
Syncing
1. Collections
Templating Products
1. Example
  1. Single Products
  2. Product Archives
2. Product Component Reference
Templating Carts
1. Line Items
  1. Raw Line Item Data
2. Cart Reference
Advanced

Installation

Set up Shopify:
1. Set up a Shopify store and enable the Buy Button Channel.
2. Open your access token and app ID by going to the Buy Button Extensions page at your-site.myshopify.com/admin/apps/private/extensions.
Set up Wordpress:
1. Download this repo and drop it into your plugins folder. Enable it through your plugin settings and then navigate to Settings > WP-Shopify.
2. Put your access token, Shopify domain (ie your-site.myshopify.com), and app ID from earlier into the WPS settings. If you can't find them, take a look here.
3. Save your changes, then click Refresh Products. Your products and collections will auto-populate from your Shopify store.

Syncing

Your Wordpress site will now be synced to your Shopify Products and Collections. Products are stored as a custom post type called wps-product.

The product ID meta field (stored under the key _wshop_product_id on a wps-product) connects a product to its data on Shopify; that data is treated as the source of truth for all product information except Collections.

This means that prices, images, variants, names, etc. - every piece of data except Collections - will pull their information directly from the Shopify store, ensuring that everything is up-to-date.

The only times you need to manually refresh your store (Settings > WP-Shopify > Refresh Products) are when:

You want to add or remove Products from your Wordpress site after setting them up on Shopify, or
You want to update your Collections information.

Basically, it's a good rule of thumb to refresh your store manually after making any significant changes on Shopify.

Collections

WPS imports Collections as a custom taxonomy called wps_collection. Each Collection in Shopify becomes a term in the wps_collection taxonomy.

Each of those terms has a custom piece of metadata called _wps_collection_image that contains the URL to the image associated with a Collection. You can set this image on Shopify, then show the image on your site like this: <image src="<?php echo $your_term->_wps_collection_image; ?>">

Templating Products

Once your Shopify data has been synced to your Wordpress site, you can start templating products and collections easily, following the cardinal rule of WPS products:

Any element with the data-product-id attribute set to a valid Product ID will turn into a product template.

Example

Single Products

Let's say your site, example.com, has WPS set up and synced. Your first product, Tofu, is ready to be sold.

Since WPS treats products as the custom post type wps-product, all you need to do is create a template for a single product called single-wps-product.php in your theme. (See the Template Hierarchy if you need a refresher on custom hierarchies.)

The contents of that file can look something like this:

<?php get_header(); ?>

    <div data-product-id="<?php the_product_id(); ?>">
        <h2><product-title></product-title></h2>
    </div>

<?php get_footer(); ?>

When you go to example.com/store/tofu, you'll see the name of your Tofu product in an h2 tag!

There are a couple things going here:

First, we wrap the product in an element with the data-product-id attribute set. Nothing outside this element will receive the correct product data or render the custom components.
Next, we set the value of data-product-id using the the_product_id() convenience function.
Finally, we included a custom component called product-title, which renders the product title. We'll cover more about WPS custom components later.

Product Archives

Let's say you've added a new product, Seitan, to your store, and you want to create an archive for products.

Just like with any other post type, you can create an archive-wps-product.php file and fill it with something like this:

<?php get_header(); ?>

    <ul>
        <?php if( have_posts() ) : ?>
        <?php while( have_posts() ) : the_post(); ?>

            <li>
                <div data-product-id="<?php the_product_id(); ?>">
                    <a href="<?php the_permalink(); ?>">
                        <product-title></product-title>
                    </a>
                </div>
            </li>

        <?php endwhile; ?>
        <?php endif; ?>
    </ul>

<?php get_footer(); ?>

Now, when you go to example.com/store, you see links for Tofu and Seitan, both leading to their own instance of the single-wps-product template we defined above!

There are a few things to note here:

We're setting up The Loop just like any other archive page.
data-product-id is again set to the_product_id(), but we have an extra <li> above the data-product-id div.
- This is because the data-product-id element is always replaced with a <div>, no matter what the original's type - an <li data-product-id="..."> would become a <div>.
We can still use normal WP templating functions like the_permalink() in the template. Mixing PHP with Vue will work just fine.

Product Component Reference

These are the custom components available to elements with the data-product-id attribute set correctly.

Unless otherwise noted, all product components have two slots: one named before, which renders its contents before the component information, and the default slot, which renders after the component information.

product-add - Creates a button that adds 1 of the product to the cart. Fires wshop.productAdded event on product container if jQuery installed. No before slot - default slot renders the button content.
product-description - The product description.
product-gallery - Renders a product-image for each image attached to the product.
product-image - Renders an image for the product.
- Picks the first available value of the following:
  - manual image (set via <product-image :image="{ src = \"manual-source.jpg\" }")
  - selected variant image
  - first image attached to product
product-radio - Renders radio selectors for each product option available. Changing the selected option will automatically update the selected product.
product-price - Cost of the product.
product-select - Renders drop-down selection boxes for each product option available. Changing the selected option will automatically update the selected product.
product-title - The name of the product.
product-type - The product type.

Templating Carts

You can easily show the contents of a user's cart in much the same way as products.

Just wrap the cart in a div with the data-cart attribute:

<div data-cart>

    <h2>My Cart</h2>

</div>

From here, you can access any of the custom components in the reference below.

Line Items

One notable difference is iterating through the items in a cart (referred to as "line items"). Instead of the expected

<line-items></line-items>

you'll need to manually set up your line items:

<div v-for="item in this.$root.cartItems">
    {{ item }}
</div>

Replace {{ item }} with any custom templating you'd like to see for individual line items - for example:

<div data-cart>

    <h2>My Cart</h2>

    <div v-for="(item, index) in this.$root.cartItems">
        <h3>Item number {{ index + 1 }}</h3>
        <single-image :item="item"/>
    </div>

</div>

Make sure you include the item prop on every custom component in the line-item loop.

Raw Line Item Data

For most line item templating, it's easiest just to refer to the raw data. Here's some of the most commonly used information:

price - The price of the product.
quantity - The quantity of this product in the cart.
title - The title of the product.

You can also always render out the {{ item }} object to see all available information. For example:

<div data-cart>

    <h2>My Cart</h2>

    <div v-for="item in this.$root.cartItems">
        Price: {{ item.price }}<br/>
        Quantity: {{ item.quantity }}<br/>
        Title: {{ item.title }}<br/>

        <h3>All information:</h3>
        {{ item }}

    </div>

</div>

Cart Reference

Unless otherwise noted, all custom components should have their item prop set to the appropriate line-item.

checkout-link - Renders a link to check out in Shopify using the current cart. No item prop required.
line-price - Renders the price for a single line-item.
remove-button - Renders a button that removes all of a line-item from a cart when clicked.
single-image - Renders a preview image for a line-item.
total-price - Renders the total price of the line-items in the cart. No item prop required.

Advanced

Permalink Structure Slug

You'll see this option under Settings > WP-Shopify. Changing its value will rewrite the store's parent directory:

// Permalink Structure Slug set to 'store'
your-site.com/store/product-1

// Permalink Structure Slug set to 'xyz'
your-site.com/xyz/product-1

Events (TODO)

Wrapper Classes

There are informational classes added to product wrappers upon rendering:

hasVariants will be added to any product that has variants on Shopify.
productUnavailable will be added to any product whose inventory is less than or equal to 0 (or is unavailable for any other reason).

There are also classes added to cart wrappers upon rendering:

empty-cart will be added to an empty cart.

Convenience Functions

WPS comes with PHP convenience functions to check for, fetch, and display product IDs. Note that $post is optional in all of these functions and defaults to the current post.

has_product( $post ) returns true if the page has a product ID set, false if not.
get_the_product_id( $post ) is returns the product ID of a given page, as defined in the 'Product ID' metadata. If there is no product ID attached to a page, it returns a blank string.
the_product_id( $post ) echoes the return value of get_the_product_id().

wp-shopify

http://funkhaus.us

Version: 2.1

Requires at least WP 3.8

banderas328/wp-shopify