Hello,
I've noticed that multiple nodes can be created for the same order. That's not correct.
A simple test I made : not filling all the required fields on the checkout page and clicking the submit button. A new node is created each time I'm redirected to the checkout page to fill the required fields.

I'll post here if I find a good solution.

Thanks.

Comments

m.stenta’s picture

It's coincidental that you mention this! I am dealing with a similar bug right now in another module. I don't think it's related, but funny that both should be occurring at the same time.

Please do let me know if you think of a good solution. I'll try to sit down and take a deeper look at it myself soon.

Quick question: are you sure that there are multiple nodes being created for the SAME order? By that I mean: are there more order NODES than there are orders in Ubercart? It may sound like a silly question, but this is what I'm dealing with in my other project. I've noticed that in some cases, checkout will create more than one order in Ubercart. If that's happening, then this is an Ubercart issue, not an issue with this module. Look at your content list (/admin/content/node) and look at your order list (/admin/store/orders). Are there more nodes than orders? Or are there also orders that were created that you didn't notice before?

In either case, thanks for the bug report!

Anonymous’s picture

Status: Active » Fixed

I guess you're right. The number of orders and the number of nodes is the same.
A new order is created by Ubercart even if there was a checkout validation problem.

That's not good at all... Well, at least, it's not an issue with this module :-)

I hope I'll find the solution to solve the Ubercart issue.

Thank you for the answer.

m.stenta’s picture

Status: Fixed » Closed (fixed)

Cool, glad to know it's not an issue with this module. I did some searching around but couldn't find any threads in the Ubercart issue queue about multiple orders being generated. If you do fine one, please post a link to it here.

It seems that it happens:
a) When checkout validation fails (as you pointed out - I haven't tested this myself)
b) When a customer gets to the "Review Order" page, and then hits the back button and does checkout again (which makes sense, I suppose, but is still annoying to have multiple orders created).

Anonymous’s picture

Indeed. I've found this issue http://drupal.org/node/841862 where TR explains that it's not a bug.
Well, it's not really a problem to have multiple orders in "checkout" status, but for nodes, it could be a problem to have 10 or 15 nodes created.
Right now I can't find a good solution to avoid this. Maybe doing something with "rules" to delete order nodes linked to "wrong orders"

Edit : I forgot to say , thank you for this module :) Now I know there's no issue with it, I'll try to do something with node orders and Ubercart Marketplace...

m.stenta’s picture

Ah ok, thanks for the link.

I think the best thing to do in your case is to simply delete the extraneous "In Checkout" orders. This will, in turn, delete the nodes that are linked to them. That cleans up both sides and keeps them synced. Perhaps you can use Rules to do that.