Active
Project:
Commerce Bulk Product Creation
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
7 Dec 2011 at 23:02 UTC
Updated:
15 Dec 2011 at 12:55 UTC
Hi,
I think I did everything correct and was able to build products with this great module.
So now I have variants of a product.
But I do not see this module to add also those 2 producs to product-nodes (productdisplays). There are no new nodes build up. Am I thinking wrong that selecting [Create products and create display] should also show 2 new nodes on admin/content/node?
I use Commerce 1.1 and BPC RC1.
Thanks for your reply in advance.
greetings, Martijn
Comments
Comment #1
summit commentedHi,
I am a step further!
1) I see I have to change some settings on:
admin/commerce/products/types/product/commerce_bpc
I changed to: Create a display node automatically for every product created.
2) I had to change the token from: [bulk_defaults:title_fragment]
to: [bulk_defaults:entered_title] and [commerce-product:field_categorieen] to have different titles for the different product displays (nodes).
Would love to have also the [bulk_defaults:combination_labels] on the nodedisplay title!
I have stuff working now! Thanks for this great module!
Greetings, Martijn
Comment #2
sven.lauer commentedI see that you have realized that the default configuration with the "Create products and create display" wizard creates only ONE display node, referencing ALL created products. The "Create a display node automatically for every product created" is intended for your use case.
Ah, thanks for pointing this out. Indeed, the update function that was supposed to take care of the change from "title_fragment" to "entered_title" is faulty. I just committed a change that should take care of this in existing installations (in new installations, this issue will not arise).
That makes sense. Re-categorizing this as a feature-request for this.
Comment #3
sven.lauer commentedCommerce bpc will use a "core like" release management, meaning that new features will go into the 2.x branch (but might be backported).