We should optionally make it so the customer can specify attributes on the node add form for their node. These would then be specified when the product gets added to the cart. This would enable store administrators to take advantage of price and SKU adjustments for the various options.
Ultimately, we'll probably want to allow fields that change which product gets added to the cart...
Comments
Comment #1
alanburke commentedThis sounds just like the feature I was about to request.
I was looking as to how this system could handle a site with multiple different events, each at their own price point.
In its current incarnation, this would mean one node type per event, and also one product per event.
It would work, but it's a bit cumbersome.
One product per event is fine [makes logical sense to me].
And one 'registration' node type should suffice for all events [same fields being captured by and large].
Selecting the proper 'product' on the registration form should mean the correct product is added to cart.
Good module.
Only yesterday I was looking at how the 'attribute' system might be able to capture these details, but this system, combined with CCK is much more robust, even as it stands right now.
Regards
Alan
Comment #2
iaminawe commentedMe too....
The ability for attributes to be chosen in the content node and then passed over to the cart when the content is added would be very useful.
There could be a simple workaround for now and although it adds an extra screen to click through it might not be too hard to implement.
What if after adding the content you were automatically redirected to the relevant product page where you chose the relevant attributes and then added to cart to continue the process.
An additional check could be made if the person added the order to the cart or not and if they didn't then maybe the node could be removed.
Comment #3
iaminawe commentedCan anyone assist with this modification? I have had a look through the code and unfortunately my php knowledge is a little too sparse to go fiddling.
Basically I would just like the redirect to go to the associated product node instead of the cart once the content node has been created. It would be great if it could still retain the functionality of being editable from the shopping cart and also allowing the content node to be deleted if it is removed from the cart.
So essentially all I want to introduce is one more step to the existing process where users can alter the product price by selecting various attributes before going to the cart and continuing with the checkout process.
Comment #4
mrfelton commented+1 for this feature request
Comment #5
alanburke commentedThere is another way to approach this problem, currently being explored by EclipseGc .
He has created two modules
http://drupal.org/project/uc_webform_productize
http://drupal.org/project/webform_associate
which approach the problem from a different angle, using webform, rather than the node system, to capture the details.
Should the following feature request
#273837: Views Integration for Webform
get acted on, then that would complete the circle.
Just throwing another option out there.
Alan
Comment #6
mrfelton commentedYes indeed, I have explored these modules too and they definitely seem like a viable solution to the problem, although neither of them are really ready for use yet (based on my testing). Definitely one to keep an eye on.
Comment #7
rszrama commentedComment #8
clevername commentedanother +1 for this feature request, specifically a redirect to the product page, rather than the cart
Comment #9
davegan commentedI'm currently working on a patch to add the attribute options to the node add form for the D6 version of the module and will release it here when I'm done.
Comment #10
rszrama commentedWait wait wait. ^_^
It's already been done and is just waiting to be committed. I thought I mentioned that in another issue, but I guess I forgot. I can commit it to a 2.x dev branch soon, I just realized that I'm going to have to make some update functions and will need to get those tested.
For an example, go click add to cart here: http://livetest.ubercart.org/uc2/product/one-day-uberevent
Comment #11
rszrama commentedAlrighty, this is actually fixed in the version in CVS for DRUPAL-6--2. I haven't gotten around to making an update function for coming up from 1.1, though.
Comment #12
davegan commentedargh. Already went and made the changes myself. Oh well.
Comment #14
bdimaggioHey all -- I'm stuck with Drupal 5 for the event-registration site I'm going to build. That means I'm also stuck with uc_node_checkout 5.x-1.0. However, I do need to allow registrants to pick some price-changing attributes at some point in the process. Can anyone (davegan?) let me know generally what method I should use to do this?
Thanks!
Ben