Search:

Just providing a bit of closure: I was told that the pfpro binaries don't work on a Solaris 6_x86 server, which is the hardware we are using. If that's true, then we are stuck until we switch to a...

Version 1.3.7

This is not necessarily a bug, but an inconvenience -- the image filename (products_image) is not saved in the products table if the string "none" appears anywhere in the filename. ...

Thank you for the follow-up.

There is no PF support presently -- I wrote a quick script that calls pfpro_version() to verify this.

The PHP version is 5.1.6 -- I noticed on the Payflow page on...

Thank you for your response...

I don't know how to enable/disable exec(). I looked in the configuration file, and I see that safe_mode is off (this would disable exec() unless it was trying to...

Thanks for the response...

No, 137 is not a Payflow error code. Even if it was, I think there would be a full payflow response message coming back with the error code.

I double checked that...

I constantly get an error 137 from the payflow pro module when I try to check out either in test or live mode. My Paypal/Verisign account is working fine -- I tested it from another server using my...