The following guide was used in a presentation at DrupalCamp Montreal 2014. The presentation focused on how to install Drupal Commerce from scratch (i.e. without the Commerce Kickstart distribution). This is an elevator guide. So get in now because we're going up!
- Install & enable required modules
- drush dl ctools views entity rules addressfield commerce
- drush en ctools views entity rules addressfield commerce -y
- Installation instructions
- use the provided drush commands
drush en commerce commerce_ui -y
drush en commerce_customer commerce_customer_ui -y
drush en commerce_price -y
drush en commerce_line_item commerce_line_item_ui -y
drush en commerce_order commerce_order_ui -y
drush en commerce_checkout commerce_payment commerce_product -y
drush en commerce_cart commerce_product_pricing -y
drush en commerce_product_ui -y
drush en commerce_tax_ui -y
- Add a few more useful modules
- drush dl admin_menu module_filter zurb-foundation-7.x-4.x-dev jquery_update -y
- drush pm-disable toolbar
- drush en admin_menu_toolbar module_filter jquery_update -y
- Create a responsive Zurb subtheme
- drush fst Your Subtheme Name your_subtheme_name 'A subtheme of ZURB Foundation.'
- Set jQuery update to 1.7+, required by Zurb (admin/config/development/jquery_update)
- Enable your new responsive subtheme (admin/appearance)
- Quick tour of what we've got soo far
- 1 Product type named 'Product'
- 2 tax types
- LOTS of hidden functionnalities
- NO visible products
- and NO, you don't get a store out-of-the-box
- Commerce Kickstart gives you that but you won't know how to get there if you don't try from scratch
- Create a new product type 'Download'
- add file & image fields
- Revisit 'Product', the product type installed by Commerce
- add an image field
- Let's create products
- a physical product (Product)
- a virtual product (Download)
- Now what? where's the store?
- Out-of-the-box Store is for wimps! ; )
- Commerce products only exist in the backstore
- products are like brown boxes in a warehouse: they're only accessible to the store's employees
- in order to make products accessible to customers, you need to put them on display in a nice and attractive way
- how do we do that in Drupal?
- we use nodes, of course
- Create a content type for displaying products - you can call it Product display if you want
- how does Commerce differentiate & recognize product displays from regular content types?
- a product reference field; so your Product display must have a product reference field
- create product displays for both content types and configure them
- Alright, let's shop!
- wait a minute, nothing happens when i click Add to cart!
- In case you didn't read the fine print: some assembly is required, like Ikea, but without the KISS diagrams
- Introducing Rules... doh! where's the Rules UI ?
- drush en rules_admin -y
- go to admin/config/workflow/rules and add a rule that redirects to the cart
- Welcome to the cart
- Time to checkout wouldn't you say ?
- doh!... something isn't right
- where are the taxes?
- Like I said, Out-of-the-box taxes are for wimps! ; )
- Commerce's tax model is simple
- there are tax types; like there are content types
- and then there are tax rates like there are nodes e.g. Pages and Articles
- Create GST & PST tax rates (note - these taxes are specific to the Province of Quebec in Canada where the camp was held)
- Revisit the checkout
- Darn, the taxes are not displayed in the expected order! (i.e. GST on the first row, PST on the second row)
- How do we change the order in which taxes are displayed ?
- the hard way: by overriding theme_commerce_price_formatted_components() in the theme's template.php (see https://drupal.org/node/1095576#comment-8721217)
- the easy way: by creating separate tax types for GST and PST and playing with their respective weight (note that at the time of this writing, the behaviour for tax weights does not follow the convention where lighter weights float to the top; see this issue)
- Are we in business yet? Not quite.
- Setting up a payment method
- for simple tests, use the 'Example payment' module (provided by Commerce)
- For serious tests and real sales, you can use Stripe or Paypal or whatever works for you. For the purpose of this presentation, I used Stripe.
- setup an account
- get the API keys (secret and publishable)
- Install & configure Stripe
- drush dl commerce_stripe
- drush en commerce_stripe -y
- add both keys to the Stripe payment method rule (admin/commerce/config/payment-methods/manage/commerce_payment_commerce_stripe)
- download the latest Stripe library v1.x from GitHub and extract it to sites/all/libraries/stripe-php
- As mentioned on the Stripe project page, NOTE: this module currently only has support for the 1.x versions of stripe-php. 2.x versions will not work.
- Time for some tests
- for this, we use the dummy credit cards provided by Stripe
- When you're happy that all works like it should you can replace de test API keys by the live API keys.
Well, we're not really done. But now you know a bit more about the process and the various pieces of the puzzle. Now simply try a few more times. Practice makes perfect, right?
I have CentOS 7 installed on my server. I installed Solr by following the instructions at www.rosehosting.com/blog/install-apache-solr-4-9-on-a-centos-7-vps/
I'm wondering if you know the process of setting up Drupal Commerce to work with Solr?
1.04. drush dl admin_menu module_filter zurb_foundation-7.x-5.0-rc6 jquery_update -y
I have litterally lost my mind to figure out how work commerce module! This pompous and exhibitionists commerce guys are to concerned and anxious to show how cool they are that is really impossible to understand anything at all!!! But it is so simple!!! Thank you!!!!!!!!!!!!!
thanks, this was really useful.
One thing that tripped me up is that I had to install stripe-php, and then it took me a while to figure out that I needed to install an older version of stripe-php (c1.18.0) for it to work. I was getting "Failure to load Stripe API PHP Client Library." Then it all worked for me. Thanks again.
Hey Matt, glad it all worked out for out in the end. I've added a line to the guide to make this clear. Cheers