Calling all pre-beta testers

This is a quick call for help before I package up a beta release of Drupal Commerce. The last few weeks I've been working around the clock on blocking issues, dependency issues, Rules based pricing and tax (incl. VAT) support, and last minute database tweaks. My wife has been incredibly supportive of me thus far, but now I need help from my friends with a bit more technical acumen.

Here's the deal: for all intents and purposes, this code is beta ready. Database schema changes have mellowed out. The modules have solidified. The core feature set lets you start selling quickly. The Views and Rules integration provides for some fine standard interfaces and workflows. The last few weeks, pcambra has been our SimpleTest hero, and now he's working with recidive to flesh out the functional tests even further.

What it really needs is eyes. Your eyes. If you have a few spare moments, you could greatly help by testing an installation and ensuring there aren't any crazy bugs that I just don't see because of my development environment or selective blindness. These could take the form of installation bugs, odd default configurations in Views / Rules, typos, broken access control, and more. There are bound to be things I'm missing, and I really need your help to know what they are.

Here's how to get started very quickly:

  1. Download Drupal 7.
  2. Download into your sites/all/modules directory the latest dev versions of the following dependencies:
    1. Address Field
    2. Ctools
    3. Views 3
    4. Entity API
    5. Rules 2
  3. (Note: Getting these from CVS would be better to get their latest commits.)

  4. Download into your sites/all/modules directory my Git dev version of Drupal Commerce (or just git clone git://
  5. Download into your profiles directory my Commerce Dev installation profile and download into your sites/all/modules directory Admin Menu (a dependency of the installation profile).
  6. Now install Drupal 7 using the Commerce Dev installation profile and see what happens!
  7. If you're feeling adventurous, use the Standard installation profile and then try to enable the Commerce modules manually to make sure the standard install process works. (You'll have to adjust some permissions, enable the cart block, and build a product display node type from scratch - read more about that in the first issue of Drupal Watchdog. )

Once it's all installed, cruise through the various admin interfaces, settings forms, and front end features and let me know what breaks. Note, I'm not looking for support requests, "How do I...?", or feature requests, "Needs flat rate shipping support." Rather, I want to know what, if anything, of the core feature set just doesn't work.™

One of the latest features to test will be to configure a tax rate for your country / state. Simply browse to admin/commerce/config/taxes and add the tax rate. If you made it a sales tax, it'll show up once you get to checkout. If you made it a VAT, it'll show up inclusive in product prices. Additionally, if you made it a VAT, you can edit products and enter their prices including VAT. Taxes work through the same Rules event as other product pricing rules, so you can try adding a discount rule and fiddle with its weight to see how it interplays with your tax rules.

Drupal Commerce comes with an example payment method module that lets you just put a name in on the checkout form to test payment. You can test additional payment methods if you have developer accounts for Authorize.Net, CyberSource, or PayPal.

Please report any bugs you can turn up (or +1 existing bugs) in our issue tracker. I'll also be hanging out in #drupalcommerce on if you're into IRC.

While you do this, I'll be running tests of my own, reviewing the names and descriptions of all our permissions, and ensuring the customer profile integration with Checkout and Order administration is up to snuff.

With any luck, we'll all be beta testers tomorrow.



There's a makefile in the repo. For your convenience
drush make commerce-test


There are known issues with the make file I believe, so if you use that be prepared to provide a patch to fix it. Wink

Just committed a patch to make sure it gets the latest dev versions of Address Field and Ctools. Should all be working now.

A build out of latest build.make (refering to latest commercedev.make) fails me. addressfield and ctools in profiles/commercedev/modules/contrib is both empty after drush has made it's magic. : (

G'day Ryan,

As requested, I am sending you a bug that is coming up on my system since i installed the 7.x-1.0-beta1b Commerce module.

This is the message I get when I try to edit a view:

* Notice: Undefined variable: type in views_get_handler() (line 871 of E:\xampp\htdocs\drupal\sites\all\modules\views\views.module).
* Notice: Undefined variable: type in views_get_handler() (line 871 of E:\xampp\htdocs\drupal\sites\all\modules\views\views.module).
* Notice: Undefined variable: type in views_get_handler() (line 871 of E:\xampp\htdocs\drupal\sites\all\modules\views\views.module).

As you can see, it is repeated 3 times - I don't know why.



Don't know if you want more, but here goes:

When I go to store/products I get this message:

* Notice: Undefined variable: type in views_get_handler() (line 871 of E:\xampp\htdocs\drupal\sites\all\modules\views\views.module).
* Notice: Undefined property: stdClass::$unknown in views_handler_field->render() (line 736 of E:\xampp\htdocs\drupal\sites\all\modules\views\handlers\
* PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column '' in 'field list': SELECT base.product_id AS product_id, base.sku AS sku, base.type AS type, base.language AS language, base.title AS title, base.uid AS uid, base.status AS status, base.created AS created, base.changed AS changed, AS data FROM {commerce_product} base WHERE (base.product_id IN (:db_condition_placeholder_0)) ; Array ( [:db_condition_placeholder_0] => 1 ) in DrupalDefaultEntityController->load() (line 196 of E:\xampp\htdocs\drupal\includes\


I imagine you've found the beta1b by now, but if corrects the missing files. We'll never have that problem again thanks to d.o's migration to Git. Additionally, I've +1'ed a patch to Views to remove the notices - it was a misnamed variable bug.

EDIT: We had to rename the beta1b to beta2, but it's the same release.

Thanks Ryan,

I'll check out the patch Monday - I need my beauty sleep now! Smile

I only ever used the beta1b, never downloaded the beta1 at all. In the meantime I got on with other work in building my website - lots of info other than just products to go up!

BTW, I just want to say that I really do appreciate the work you guys put in. Thanks.


G'day Ryan,

I'm still getting the same problems, even with the latest of everything loaded. I'm not a developer so I am not of much use to you here. I'll just carry on with building the rest of the website until you guys get it all sorted.



Well, follow along in the issue tracker. That's a better place to track bugs and fixes than my blog:

I'm really not sure what your problem could be. This is the only pertinent issue, but it's been solved for everyone by them updating to the beta2 (was beta1b, but we had to rename) and ensuring the use of dev versions of all dependencies.

Can I install it without Drush? Thanks. I don't have shell access. Sad