Closed (fixed)
Project:
Ubercart Atos/Sips
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Nov 2008 at 15:49 UTC
Updated:
10 May 2010 at 16:30 UTC
Hi zmove,
I'm having some orders registered as anonymous user i.e. $user->uid == 0.
It was working great until I upgraded from uc_atos first release on Ubercart.org to now using the version called 1.2.1.
There's a lot of code changes between those two versions, so it's kind of hard to debug things.
After a lot of testing, I'm pretty sure this only happens with new customers (and maybe old ones), that do not come back to the store after having filled their payment info. They do not click on "Retour à la boutique".
Do you have any clue on this?
Thank you so much!
Jérémy
Comments
Comment #1
jchatard commentedI think I just found it !
This is the exit statment that breaks all!
Because, it stops, but it should let Ubercart call all the function like uc_cart_checkout_complete() which calls uc_cart_complete_sale() which is in charge of creating the new user!
Don't you think?
Comment #2
zmove commentedThank you for your feedback and your suggestion, I will try that and commit if it's the great fix !
Comment #3
jchatard commentedHi zmove,
I tried, but the problem is more tricky!
Let's say, you just leave the exit statment, then the autoresponse will be in charge of terminating the order (creating the new account if needed, sending emails, dicreasing the stock, etc.).
This is great, but :
In fact, I really don't see any solution, apart from forcing the user to come back to the site, but how?
Jérémy
Comment #4
zmove commentedHmmm, I remember I had lots of problems with google analytics integration cause lots of people don't clock on "retour a la boutique" button. The only solution would be to ask to ATOS if it's possible to directly return to our shop url after a successfull payment.
It was on my todo list long time ago, but lots of project came between, and I never had time to take this task.
So, I let the release as it is, waiting (and searching too, a little ^^) for another solution.
I didn't let anonymous user order on my shop because of this issue...
Comment #5
jchatard commentedOk,
Maybe you could put this issue in a README file and/or on the project page, because it's really an anoying problem!
Thanks,
Jérémy
Comment #6
zmove commentedI updated the module description to notice that problem.
Comment #7
zmove commentedChanged the priority cause it affect only anonymous order. I prefer to keep critical issue for fatal error problems.
Comment #8
modjodandy commentedDoes any of you guys found a good fix for this module?
Comment #9
anrikun commentedIt is now fixed in the last 6.x-1.x dev version.
Please review it.