close ad
Install the LAtest Updates to Work with CC 2017 and CC 2018
open ad
View Menu

Technical Support Forums

Free, outstanding support from WebAssist and your colleagues

rating

ecart and Protx

Thread began 3/11/2009 8:56 am by bobwales349753 | Last modified 5/13/2009 3:13 pm by Ray Borduin | 1844 views | 7 replies |

bobwales349753

ecart and Protx

Anyone else troubled by this problem?
Protx upgraded their protocol to 2.23 on 3rd March and so their testing servers will no longer accept the eCart fields, even if you change the protocol version from 2.22 to 2.23.

Fields that were optional have now become compulsory.

If anyone has a fix for this I'd be grateful to hear about it.

Explanation: FindPost7777.aspx

Sign in to reply to this post

bobwales349753

Temporary solution

It appears that only the testing server at Protx requires protocol 2.23

If a full Protx account has been granted, then carts can be tested against a test server which WILL process protocol 2.22, for the time being.

So, Ecart will work with Protx, but only after a formal application is made and approved.

The free test server, which is available without any committment or merchant number, will not work until Ecart is configured for protocol 2.23

Hope this helps

Sign in to reply to this post

sales356151

Protx has now changed to SagePay is there going to be an update for ecart checkout wizard?

Sign in to reply to this post

Ray BorduinWebAssist

Yes we are already working on the protx updates.

Sign in to reply to this post

steve365364

Is there any word on when an update will be available - as nothing i do can get the cart to work with sagepay - therefore my website does not work...

Sign in to reply to this post

Ray BorduinWebAssist

It is my understanding that our current proTX solution should still work. It just doesn't work with thier sandbox any more. Did you actually have a site stop working because of this issue?

Sign in to reply to this post

steve365364

Yes - the site I have has stopped working now - the information that sagepay is requiring is not in anyway the same as is being output by the cart plugin for dreamweaver. I have been in contact with sagepay - they agree.

Sign in to reply to this post

Ray BorduinWebAssist

I was under the impression that they would continue to support their old API for some time. I know we don't match the new sagepay technique, but the old proTX technique shoudl still work.

Please post a support incident and we can get an engineer to work with you directly to try to resolve this problem.

Sign in to reply to this post

Build websites with a little help from your friends

Your friends over here at WebAssist! These Dreamweaver extensions will assist you in building unlimited, custom websites.

Build websites from already-built web applications

These out-of-the-box solutions provide you proven, tested applications that can be up and running now.  Build a store, a gallery, or a web-based email solution.

Want your website pre-built and hosted?

Close Windowclose

Rate your experience or provide feedback on this page

Account or customer service questions?
Please user our contact form.

Need technical support?
Please visit support to ask a question

Content

rating

Layout

rating

Ease of use

rating

security code refresh image

We do not respond to comments submitted from this page directly, but we do read and analyze any feedback and will use it to help make your experience better in the future.

Close Windowclose

We were unable to retrieve the attached file

Close Windowclose

Attach and remove files

add attachmentAdd attachment
Close Windowclose

Enter the URL you would like to link to in your post

Close Windowclose

This is how you use right click RTF editing

Enable right click RTF editing option allows you to add html markup into your tutorial such as images, bulleted lists, files and more...

-- click to close --

Uploading file...