radders Posted March 11, 2003 Share Posted March 11, 2003 I had two Worldpay payments today which failed to produce any matching orders in my shop. Nothing major wrong with either order (one was a caution and the other had previously gone through Paypal IPN - Pending). It set me thinking. I had previously installed version 3c of the Worldpay module and I still had the old resultC and resultY files around on the server at Worldpay. I wonder if these could be causing the problem. Anyway I have deleted those files and hope this solves it. I'm using Loaded v5 btw. The only other thing I could think of is that my orders_status_id 3 is set to 'posted' rather than 'delivered'. Anyone else still getting these problems with it? Quote Link to comment Share on other sites More sharing options...
scottymcloo Posted March 11, 2003 Share Posted March 11, 2003 None of what you have got should cause that problem. I am using loaded v5 too without any of the problems you describe. I would leave the result (C and Y) file because if Worldpay cannot find wpcallback.php is reverts back to these files. Check wpcallback is still there, the case is correct. Try calling wpcallback directly from your internet connection to test - ie www.yourdomain.com/wpcallback.php The WP cautions are not known to osCommerce as the only thing Worldpay can do is process the payment, or cancel it. Quote Link to comment Share on other sites More sharing options...
radders Posted March 11, 2003 Author Share Posted March 11, 2003 Out of 30 transactions only 3 have failed. This suggests to me that the file exists and that resultC and resultY are not doing their job as a backup system. I'm afraid I may have blindly used an inappropriate version of the file. Do you know what these files should look like? <HEAD> <TITLE>Redirecting...</TITLE> <meta http-equiv="Refresh" content="0; url=<wpdisplay item="MC_failURL">"> </HEAD> <script language="javascript1.1"> <!-- Hide location.replace ('<wpdisplay item="MC_successURL">'); // end hide --> </script> is what I had for resultY.html Quote Link to comment Share on other sites More sharing options...
scottymcloo Posted March 12, 2003 Share Posted March 12, 2003 You have to have these variables set up :- ie MC_successURL must be set to the URL to redirct to. My contribution does not have these set, so you should create the resultY.html to: <HEAD> <TITLE>Redirecting...</TITLE> <meta http-equiv="Refresh" content="0;url=http://www.yourdomain.com/checkout_success.php"> </HEAD> and the ResultC.html to <HEAD> <TITLE>Redirecting...</TITLE> <meta http-equiv="Refresh" content="0;url=http://www.yourdomain.com/checkout_payment.php"> </HEAD> This has not been tested - I cannot get on to my test system right now, so to do the test simply rename your wpcallback.php to a different name, then Worldpay will not be able to find it and use these files instead. Obviously rename the wpcallback.php back when you are finished. If you do this test, maybe you could post if it worked ok. Quote Link to comment Share on other sites More sharing options...
radders Posted March 12, 2003 Author Share Posted March 12, 2003 Thanks, I'll have a go at that next time the site is quiet. Checking out the configuration I now notice that my callback failure count is zero, which leads me to believe the problem may lie elsewhere. :? Quote Link to comment Share on other sites More sharing options...
Guest Posted March 12, 2003 Share Posted March 12, 2003 We use worldpay, and occasionaly we get 'missing' orders, which is a real pain. In an attept to track down the problem, i have been in contact with several customers whose orders didn't get added to the osc database. In every case (so far) it has been due to the user not reaching checkout_success.php. as far as i can see the problems are nothing to do with the payment modules, but due to the customer not allowing the browser to redirect back to checkout_success, several custmers reported that they accidentaly clicked 'no' when asked if they wish to be redirected back (an alert box i assume). Some others browsers just crashed before getting redirected back. If anyone knows different and has any ideas on how to fix this problem it would be most appreciated. There's nothing worse than having to phone/email a customer to ask them what they bought :) Cheers Matt www.consoleplus.co.uk Quote Link to comment Share on other sites More sharing options...
scottymcloo Posted March 12, 2003 Share Posted March 12, 2003 There is a lengthy discussion on exactly this problem here: http://www.oscommerce.com/forums/viewtopic.php?t=31441 Because osCommerce is going away to another web site (Wordpay), and then needs to be redirected back to complete the order and update the database, there is always a chance that the system will crash, customer will not wait, etc, etc. This has been minimised as much as possible as discussed in the above thread. It could be possible to store the order details in another table that is updated just before redirecting to worldpay. Quote Link to comment Share on other sites More sharing options...
radders Posted March 12, 2003 Author Share Posted March 12, 2003 Matt, would I be right in thinking that you didn't get a callback failure email in these cases either? Obviously the problem is nowhere near as bad as with Paypal but I would love a temporary table along the same lines. It is so time-consuming to go through the shopping cart to work out what the customer ordered. Quote Link to comment Share on other sites More sharing options...
Cerberus Posted March 12, 2003 Share Posted March 12, 2003 Take a look at http://www.oscommerce.com/community/contri...ions,871/page,8 This is probably what you are after. Quote Link to comment Share on other sites More sharing options...
radders Posted March 12, 2003 Author Share Posted March 12, 2003 Sounds like just the job! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.