I just used Mike's tutorial from DrupalEasy (http://drupaleasy.com/blogs/ultimike/2009/03/event-registration-ubercart) to fix this, but it seems the feature should be integrated already in the node checkout module.

Out of the box, it doesn't seem there is an option to set so that if a user purchases something that creates a node, but doesn't go through with the purchase, the node they created isn't just lumped together with the ones that have been purchased. With the tutorial I was able to add a custom field to the data type and then use a conditional action to acheive that functionality, but it seems like something very basic that the module--if anything--should do by default, and require work-arounds to disable.

Thanks for all your work...you guys are awesome!

Comments

drewish’s picture

drewish commented

Yeah I think we could do this with the data already in the {uc_node_checkout_order_products} table since the uc_node_checkout_save_product_association() is only called after the order is submitted. I'm guessing that the views work going on in #430016: UC Node Checkout should provide a view to query against the related checkout node would do the trick.

eporama’s picture

eporama commented

Unfortunately, I think the way the #430016 played out it doesn't work for this problem... The latest patch by webchick goes straight to the uc_node_checkout_order_products table which isn't updated until after the order is submitted. Until then, the data is held in the data field of uc_order_products and the relationship doesn't have it.

I'm trying to build a view that shows the orders that are still "in checkout" and which "registration profiles" they relate to.

aidanlis’s picture

aidanlis commented
Status: Active » Fixed

This is done, you can now update a node with the order status.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.