PayFlow Pro and PHP >5.1

[kevinkimt]

I upgraded to 5.1.6 and code that used to be able connect to versign stopped working, specifically pfpro_init calls are no longer recognized. The manual states that since 5.1 these functions are no longer apart of PHP and that you should get them from PECL.

The PECL website does not seem to have any PayFlow Pro modules available for download and there isnt any reasonable documentation on what someone who wants to use PayFlow pro should do to get it working.

Any help would be greatly appreciated.

[bradgrafelman]

I found this site (http://www.doctortux.com/pages/howto_pfpro.php) which talked about compiling PHP with Payflow support. Specifically, this paragraph might help:

Next, you need to see if pfpro extention is available in the current build that you are building. Go to the root directory of the php source code and change into the ext/ directory. If there is no directory for pfpro, which would mean the at pfpro has been deprecated from the version of php source code that was downloaded from php.net, download pecl extention for pfpro by executing the "./ext_skel --extname=pfpro" from the "php_source/ext" directory. This will download and install the pfpro module from pecl. If you can not download using "ext_skel", I have a placed a copy of the pfpro pecl release in the DoctorTux pfpro pecl directory (http://www.doctortux.com/pecl/pfpro-pecl.tar.gz). If you download this version, extract it in the ext directory. The pecl pfpro module will allow you to compile the VeriSign pfpro SDK into php module.

Once the pfpro pecl module is extracted in the ext directory, you must run from the php source directory the following command:

"./buildconf --force"
After the buildconf is finished, you can add the following line to your "Command Configure" script '--with-pfpro=/usr/local/pfpro'. This is assuming that you have place the VeriSign pfpro SDK that you download from VeriSign in the /usr/local directory. This SDK is not the same a the pecl pfpro configuration module.

[kevinkimt]

Thanks for getting back to me, while I was waiting I ended up just writing a class that wraps and abstracts the exec calls necessary to do it "manually". So I skirted the problem and won't bother with trying to get those php functions working as this was easier and won't require me to compile and install various modules on a dozen webservers.