Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

Protx Form - failed transactions still create orders


rjavery

Recommended Posts

I am using version 1.06 of the protx form module and everything is working OK except that when Protx fails validation or customers cancel the transaction my customers are still taken to the Finished page.

 

My customers then receive a fail message from Protx and a success message from our shop (http://www.kidEstore.co.uk) which is confusing (for both them and me).

 

Anyone know what the answer is?

 

Do I just need to change failureURL in protx_form.php. Currently both successURL and failure URL point to checkout_process.php :-

 

$plain .= "SuccessURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&";

$plain .= "FailureURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&";

 

I would have thought someone else would have had this problem but other threads on Protx failure indicate that they get an error code if someone cancels - we do not.

 

Richard

Link to comment
Share on other sites

  • 1 month later...
I am using version 1.06 of the protx form module and everything is working OK except that when Protx fails validation or customers cancel the transaction my customers are still taken to the Finished page.

 

My customers then receive a fail message from Protx and a success message from our shop (http://www.kidEstore.co.uk) which is confusing (for both them and me).

 

Anyone know what the answer is?

 

Do I just need to change failureURL in protx_form.php. Currently both successURL and failure URL point to checkout_process.php :-

 

$plain .= "SuccessURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&";

$plain .= "FailureURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&";

 

I would have thought someone else would have had this problem but other threads on Protx failure indicate that they get an error code if someone cancels - we do not.

 

Richard

 

Did you get a fix to this problem as I have the same issue?

Link to comment
Share on other sites

$plain .= "SuccessURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&";

$plain .= "FailureURL=" . tep_href_link(FILENAME_CHECKOUT_PAYMENT, '', 'SSL', true) . "&";

 

 

Works for me, except for the protx issue which I and a few others are having at the moment.

Link to comment
Share on other sites

It seems the common element here is that those of us having this problem are hosting with 1and1 (I tracerouted kidestore.co.uk and your site is there, as is mine).

 

I have yet to receive a reply from 1and1 about this issue.

 

I would suggest we all contact them.

 

k.

Network Webcams - The IP Camera Specialists

Link to comment
Share on other sites

I have just spoken with 1and 1 and on Thursday 3rd November they upgraded php from 4.3.10 to 4.4.1. This is most likely to have caused the problem.

 

Does anyone know what changes need to be made in the store to fix this issue based on the new php version?

 

k.

Network Webcams - The IP Camera Specialists

Link to comment
Share on other sites

Another issue people using Protx and 1and1 should be aware of is that because this failure is causing the customer to return to the payment page, it is quite likely that some customers will assume that their order did not get processed and that they need to do it again. This can, and will lead to duplicate successful payments processed through Protx with no record of each order in your DB.

 

Just remember to 'void' the duplicate payment in your Protx admin pages until this problem is fixed. This is far easier than allowing the payment to go to settlement and then having to refund the customer.

 

This issue seems more and more limited only to OSCommerce stores hosted at 1and1.

 

k.

Network Webcams - The IP Camera Specialists

Link to comment
Share on other sites

Sorry recidivist - I think this thread is about something different.

 

On a fresh install of Protx some time ago, the default failure and success URLs are the same so a customer pressing cancel in the Protx forms would still create an order in OSCommerce.

 

 

It seems the common element here is that those of us having this problem are hosting with 1and1 (I tracerouted kidestore.co.uk and your site is there, as is mine).

 

I have yet to receive a reply from 1and1 about this issue.

 

I would suggest we all contact them.

 

k.

Link to comment
Share on other sites

  • 4 weeks later...

Hi guys,

 

It sounds like the .php page the response from Protx is being returned to is not being handled properly and therefore is not taking the customer to the failed or cancellation page. I'm going to run a few tests and see if I can get back with a proper answer. I need to work out the status that is being returned to the page to make sure it is coming back correctly.

 

J

Link to comment
Share on other sites

Hi guys,

 

It sounds like the .php page the response from Protx is being returned to is not being handled properly and therefore is not taking the customer to the failed or cancellation page. I'm going to run a few tests and see if I can get back with a proper answer. I need to work out the status that is being returned to the page to make sure it is coming back correctly.

 

J

 

 

I sent a message to Protx and they responded with this:

 

"Hi,

 

I have to say it does sound like the page we return our response to is not handling that response properly. We can decrypt the information we are sending back to prove that we are sending the correct status back in the result of a cancellation if you can provide a link so we can put a transaction through your site.

 

Best wishes,

 

Protx Support"

 

 

They are looking at my coding at the moment, so hopefully they or anyone can help

 

 

this is the only bug i have....once done I can launch my site :)

Link to comment
Share on other sites

$plain .= "SuccessURL=" . tep_href_link(FILENAME_CHECKOUT_PROCESS, '', 'SSL', true) . "&";

$plain .= "FailureURL=" . tep_href_link(FILENAME_CHECKOUT_PAYMENT, '', 'SSL', true) . "&";

 

 

Works for me, except for the protx issue which I and a few others are having at the moment.

 

 

With the line: $plain .= "FailureURL=" . tep_href_link(FILENAME_CHECKOUT_PAYMENT, '', 'SSL', true) . "&";

 

what I have done is change it to: $plain .= "FailureURL=" . tep_href_link(FILENAME_ACCOUNT, '', 'SSL', true) . "&";

 

So when a user presses Cancel in protx, it takes them to their account screen and no order is process and you get a Protx Failure email

 

This is the only thing i could come up with :(

Link to comment
Share on other sites

  • 3 months later...
  • 1 month later...
Hello... Did somebody solve this problem in this last couple of months?

 

I faced the same problem. Payment transactions have not been confirmed by the shopping cart. I.e. Protx cannot re-direct to your shop success page.

 

The 2 line job didn't do the trick for me.

The PHP version had nothing to do with it on my website - my web host kindly upgraded my account to the newest PHP version - the problem persisted.

 

Registered Globals are turned on.

 

I have come up with a workaround which I uploaded to the contrib page:

 

http://www.oscommerce.com/community/contributions,441

 

Hope it helps. :)

Link to comment
Share on other sites

Hi I'm having the exact same problem

 

I have emailed a couple of people within the forums to see it they have been able to resolve the same issue, however I have now downloaded your own fix and will let you know how I get on with it...

 

Many Thanks for posting on this issue

 

Marie

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...