Drupal Commerce Blog

What's happening in the world of Drupal Commerce.

Enabling Fancy Attributes in Commerce 2.x

In Drupal Commerce 1.x, we used the Commerce Fancy Attributes and Field Extractor modules to render attributes more dynamically than just using simple select lists. This let you do things like show a color swatch instead of just a color name for a customer to select.


Fancy Attributes on a product display in Commerce Kickstart 2.x.

In Commerce 2.0-alpha4, we introduced specific product attribute related entity types. Building on top of them and other contributed modules, we can now provide fancy attributes out of the box! When presenting the attribute dropdown, we show the labels of attribute values. But since attribute values are fieldable, we can just as easily use a different field to represent it, such as an image or a color field. To accomplish this, we provide a new element type that renders the attribute value entities as a radio button option.

Read more to see an example configuration.

Posted: May 3, 2016
2 Comments

Commerce 2.0-alpha4 released

Almost two months and seven thousand lines of code later, here's Commerce 2.0-alpha4. This release brings checkout and revamped product attributes. We've also added upgrade path APIs in preparation for beta1. Meanwhile, we helped push Drupal 8.1 out the door and fixed many Inline Entity Form bugs.


The new checkout flow configuration form.

Reminder: Commerce 2.x alphas are NOT production ready. No upgrade path is provided between alphas. A full reinstall is needed each time.

Read on to find out what's new...

Posted: April 28, 2016
11 Comments

Upgrade paths between Drupal 8 module versions

Over time, modules update their shipped configuration such as rules, views, node types. Users expect to get these updates when they update the modules. For example, Drupal Commerce 1.x provides over eleven default views and rules. From release to release, these Views and Rules were enhanced with new features or bug fixes reported by the community.

Take the order management view. In a future release of Drupal Commerce, we may add a newly exposed filter to the view. In Drupal 7 the view would automatically be updated unless it was overridden. That is not the case in Drupal 8.

Drupal 8 introduces the Configuration Management system. While robust, it changes how we work with the configuration in comparison to Drupal 7. Instead of a module owning configuration, configuration is now owned by the site. When a module is installed, its configuration is imported. On module update, no configuration updates are performed. Instead, the module must write an update hook to perform one of the following updates:

Posted: April 22, 2016
0 Comments

Commerce 2.0 alpha3 released

It's time show you what's kept us busy in February. Say hello to alpha3! Aside from the many bug fixes, the focus is on improving cart functionality. We've also been busy stabilizing Inline Entity Form, with dozens of commits and two new releases.

Reminder: Commerce 2.x alphas are NOT production ready. No upgrade path is provided between alphas. A full reinstall is needed each time.

Read on to find out what's new...

Posted: March 2, 2016
6 Comments

Commerce 2.0 alpha2 released

The holidays are a distant memory, and Drupal 8 contrib work is happening in full force. Time for another 2.x alpha. The past three weeks have seen bug fixes, test work, and many internal cleanups. But let's focus on the bigger changes.

Reminder: Commerce 2.x alphas are NOT production ready. No upgrade path is provided between alphas, a full reinstall is needed each time.

Read on to find out what's new...

Posted: January 22, 2016
2 Comments

Commerce 2.0 alpha1 released

2016 will be the year of Drupal 8 and Commerce 2.x projects.
In order to start tracking our progress towards our first productive ready release (which will be beta1), we're releasing alpha1 of Commerce 2.0.
Behind the scenes we've also created new releases of several dependencies: inline_entity_form 1.0-alpha3, profile 1.0-alpha1, and state_machine 1.0-beta1.

Download alpha1 here, then follow the installation instructions in our documentation.

Read more...

Posted: December 25, 2015
4 Comments

Contributor Spotlight: Josh Taylor

Say hi. (who are you and what do you do in the Commerce ecosystem)

Hello! I'm Josh Taylor, a PHP Developer living in Melbourne, Australia who focuses on Drupal 7/8 and Symfony2 projects. I've been involved with helping Commerce 2.x in my spare time (not as much lately due to time constraints) to help make it the go-to eCommerce platform for users.

How did you get involved with contributing to Drupal Commerce?

benjy (Ben Dougherty) mentioned that Drupal Commerce was in the planning phase. I got really excited and checked it out, and started to contribute back small fixes with the help of bojanz (Bojan Zivanovic). Then I just kept going - I hope to contribute more back in 2016 when I have more time, especially as clients start to move onto Drupal 8.

Posted: December 14, 2015
0 Comments

Commerce 2.x Stories: Workflows

Now that we’ve covered products, it’s time to jump into orders. We are improving many aspects of orders based on previous feedback. One such aspect is the concept of order statuses and states.

In Commerce 1.x orders have a status. The status indicates the current checkout page, whether the order is a cart, whether it has been paid and fulfilled (shipped), or maybe cancelled/refunded. Statuses are sequential, one goes after another. They are grouped by states, e.g. all checkout statuses belong to the “checkout state“.

The problem with this model is that one list of statuses indicates multiple concepts (checkout state, payment state, fulfillment state, etc). These concepts are parallel and trying to handle them sequentially creates bugs and confusion. For example, an order might be paid before or after checkout completes due to the async nature of certain payment gateways, or because the business is invoicing clients at the end of the month. Furthermore, there is no requirement for the status to change sequentially, it can be set to any other status at any point. There is no way to express rules such as “only completed orders can be refunded“ or “completed orders can’t be sent back to checkout”.

Read on to find out how we're fixing it...
Posted: December 10, 2015
2 Comments

Commerce 2.x Stories: Products

Previously we talked about currencies and stores. This week we’ll focus on products.

Drupal 8 product list.

Commerce 2.x ships with much better UX out of the box, thanks to a revamped product architecture. It also features under the hood improvements that allow developers to implement custom product architectures for different use cases.

Read on...

Posted: November 20, 2015
10 Comments

Contributor Spotlight: Joël Pittet

Say hi. (who are you and what do you do in the Commerce ecosystem)

Hi:) My name is Joël Pittet and I’m out of Vancouver, BC, Canada. I offered to help co-maintain commerce_discount and a few other Commerce modules as well as likely involved in messing about with patches all over Commerce ecosystem.

How did you get involved with contributing to Drupal Commerce?

Started working on a Drupal Commerce project, noticed things could use some fixing up and jumped in the deep end. I was recognized for helping triage the commerce queue in a fervor to fix all the things.

Posted: November 16, 2015
0 Comments

Pages

Subscribe to Blog