drabbytux

1. Copy this code and paste it at the bottom of your Assets/vendor.js file, or if your theme doesn't have a vendor.js file, place it at the very top of the theme.js file. (At the moment, POP requires this to be added at the very bottom of the theme.js file, followed by the next bit).

2. Add this to the bottom of the Assets/theme.js file:

Shopify.Cart.ShippingCalculator.show( {
  submitButton: theme.strings.shippingCalcSubmitButton,
  submitButtonDisabled: theme.strings.shippingCalcSubmitButtonDisabled,
  customerIsLoggedIn: theme.strings.shippingCalcCustomerIsLoggedIn,
  moneyFormat: theme.strings.shippingCalcMoneyFormat                                     

randallreedjr

Working with git remotes on Heroku

Generally, you will add a git remote for your Heroku app during the Heroku app creation process, i.e. heroku create. However, if you are working on an existing app and want to add git remotes to enable manual deploys, the following commands may be useful.

Adding a new remote

Add a remote for your Staging app and deploy

Note that on Heroku, you must always use master as the destination branch on the remote. If you want to deploy a different branch, you can use the syntax local_branch:destination_branch seen below (in this example, we push the local staging branch to the master branch on heroku.

$ git remote add staging https://git.heroku.com/staging-app.git

shopifypartners

# Use an array to keep track of the discount campaigns desired.
CAMPAIGNS = [
  # $5 off all items with the "sale" tag
  ItemCampaign.new(
    AndSelector.new(
      TagSelector.new("sale"),
      ExcludeGiftCardSelector.new,
    ),
    MoneyDiscount.new(5_00, "5$ off all items on sale",),
  ),

shopifypartners

# Takes a product id, and a map of variant ids and quantities
def update_inventory(id, vid_quantities)
  variants = vid_quantities.map do |vid, qty|
    { "id" => vid, "inventory_quantity" => qty }
  end
  data = {
    "product" => {
      "variants" => variants
    }
  }

zulhfreelancer

1. Assuming you have multiple Heroku apps and Git remote like so:

development https://git.heroku.com/xxx.git (fetch)
development https://git.heroku.com/xxx.git (push)
origin      [email protected]:xxx/xxx.git  (fetch)
origin      [email protected]:xxx/xxx.git  (push)
production  https://git.heroku.com/xxx.git (fetch)
production  https://git.heroku.com/xxx.git (push)
staging https://git.heroku.com/xxx.git (fetch)

davidemaser

Shopify.queue = [];
  Shopify.moveAlong = function() {
    if (Shopify.queue.length) {
      var request = Shopify.queue.shift();
      Shopify.addItem(request.variantId, request.quantity, request.properties, Shopify.moveAlong);
    }
    else {
      document.location.href = '/cart';
    }
  };

amratab

Suppose you have two heroku remote apps
myapp-dev & myapp-prod
and two git branches 
master(for dev) & production
Now lets setup heroku on the existing git repo in your local machine
Assuming the branches and the apps exist already
git remote add heroku-myapp-dev https://git.heroku.com/myapp-dev.git 
git remote add heroku-myapp-prod https://git.heroku.com/myapp-prod.git 

CodeBrotha

## This is your TEST dev theme [in Test env]. You should make all your changes here and view on test store while working.
development:
  <<: *shared
  store: STORE_NAME_HERE.myshopify.com ## Test Store name.
  password: ADD_PASSWORD_HERE ## Private App password from Shopify.
  theme_id: 'ADD_THEME_ID_HERE' ## ID number of your Dev theme on live store.

## TEST Staging theme [in Test env]
staging-test:
  <<: *shared

minionmade

<form action="/cart/add" method="post" enctype="multipart/form-data" id="AddToCartForm">
  {% if collection.products_count > 0 %}
      {% for product in collection.products %}
        {% if product.available %}
              <div class="row">
                <div class="col-xs-12 col-sm-4">
                    <img src="{{ product.image | default: product.featured_image | img_url: 'large' }}" alt="{{ variant.title | escape }}" />
                </div>
                <div class="col-xs-12 col-sm-8" style="padding: 15% 40px 0">
                <div class="col-xs-12 col-sm-12">

NigelEarle

Migrations & Seeding

What are migrations??

Migrations are a way to make database changes or updates, like creating or dropping tables, as well as updating a table with new columns with constraints via generated scripts. We can build these scripts via the command line using knex command line tool.

To learn more about migrations, check out this article on the different types of database migrations!

Creating/Dropping Tables