commerce_vado 3.0.4

Issue #3629437: Move child order item creation to it's own service
Issue #3629761: Child variations reference views would break in 11.4
Issue #3302856: Add Quantity for Group Items
Issue #3629227: Allow child variations to set a quantity
Issue #3629714: Allow all child order items to be collapsed or hidden under the parent order item

Updating existing sites

Issue #3629227: Allow child variations to set a quantity adds a quantity to the now custom child_variations Vado reference field. Update 8205 adds the quantity column to the database table and updates the field configuration, so if you use child variations you should update locally and test. Then export the configuration with drush cex and push it to production, so you can import the updated configuration after running the update there.

If you use child variations, update locally and test first. Sites that sync configuration should then:

1. Run the updates locally (drush updb) and test.
2. Export the configuration (drush cex) and commit it. The export includes the changed child_variations configuration.
3. Deploy, then run the updates on production before importing the exported configuration. drush deploy runs the updates before the configuration import, so it works in that order.

Importing the new field configuration before the update has run will fail.

The other 2 updates for group and group item quantity and hide collapse should be pretty straight forward.

Documentation

See docs for how to use child quantity, and for new child quantity view field. Also see docs on the new Hide child items field.