Or I misunderstand the way to configure Ubercart Webform Integration, or there's something wrong.
What I can do :
From add content menu, create or edit a product and bind it to an existing webform. Then if I submit my associated webform, product is added to cart and I'm redirected to checkout. Fine!
What I cannot do :
It is said into UC Webform : After you install this module, you will have four more component types for a webform: 'product', 'product list', 'product grid' and 'hidden product'. When you add these types of components, you will be asked to select which products you'd like to offer to those filling out the webform. The products you select will be added to your webform.adding a hidden field with or special field".
These components don't appear in add content ->webform .
And if I bind a node type to webform, and then embed a webform into a node of this type (let's call it a "nodeform"), there is no way to bind these "nodeforms" to a product :
In the add content -> product page, the autocomplete field "Application Form" doesn't see these "nodeforms". Into the webform tab of the node :
• into form settings, nothing related to products.
• Into form components, none of the promised new components types appear.
Further, when I submit either the "nodeform", it returns many warnings and notices, as already said in other issues, like "is not a product. Unable to add to cart."
So did I missed something or something's wrong? How to set up these components as above and where ?
Comments
Comment #1
mgiffordThe released D7 version of UC Webform works quite differently from the D6 version. I prefer the D6 version and the patch we provided does support this.
Comment #2
Kojo Unsui commentedUnfortunately for that module, I'm on a D7 project.
Does this patch you provided support the features I'm talking about ? And I didn't keep clear which version I have to apply this patch to ?
Thanks a lot.
Comment #3
mgiffordYup, that's the patch I was referring to and it should apply nicely to the git repository for Drupal 6 for this project.
I perhaps wasn't clear enough. The current D7 release does not keep the same functionality as the D6 release. My patch takes D6 and upgrades it to D7 with it's functionality intact.
Comment #4
Kojo Unsui commentedIndeed you were clear enough, this is what I had understood, like two branches for D7, but I was not sure.
I'll apply your patch then and see if it solves my needs. Thanks again.
Comment #5
liliplanet commentedPlease @mgifford would you be so kind to release your patched D7 version, most appreciated :)
Comment #6
mgiffordI posted it here - https://drupal.org/node/1255832#comment-6008910
Worth reading that thread.
Comment #7
deja711 commentedThis should not be an issue in 7.x-2.x branch. Note 7.x-1-x branch is not supported and was one of initial (abandoned) attempts for porting this module from Drupal 6.
If this is an issue with 7.x-2.x please reopen the issue.