FedEx API > PHP4.X
- Started
- Last post
- 7 Responses
- dMullins
Do any of you code whizzes have experience getting the FedEx API to translate for PHP4.X? We have a serious issue with one of our client sites and our freelance PHP guy cannot seem to get a certain feature to work.
We have been working with a developer for a while for a client's e-commerce website. Recently, we have been tasked with integration real-time shipping methods into the store via the FedEx API for the sake of being able to print shipping labels automatically. Our developer was able to integrate the FedEx API via the shopping cart system very easily (Pinnacle Cart, which provides turnkey support for FedEx, UPS, et al.).
The problem is the label printing. Getting the API to talk to the server correctly has been a pain because the server PHP version is 4.39, on non-Red Hat 5. Currently, he has tried using retro-fitting Red Hat with SOAP (introduced in PHP4, non-existent in PHP4.X) and that's about as far as he got. He's used PEAR to get SOAP working somehow, but retro-fitting it does not seem to work.
At this point, we are in a terrible bind because the client is fuming mad, and rather than impart that on the developer I've been trying to stay positive and encouraging. At this point though, we have no other options except to migrate to a new server, upgrade to the Red Hat 5/PHP5 on that server, reinstall the shopping cart, and then re-upload the databases and files. That is unfortunately not an immediate option. We were told the task was completed weeks ago and when we went to turn it on for an internal deadline it did not work as expected.
We are at a loss for a solution right now, and I desperately need to get this figured out, whatever it takes. Losing this account at our agency could be a huge setback for us. Sorry for the lengthy post—I was trying to get as much detail out there as possible for anyone who might be interested and capable.
- acescence0
just installing php5 on the same server is not an option? they can run side-by-side with a minimal amount of tweaking.
- dMullins0
The server runs an older version of Red Hat apparently that doesn't support PHP5?
- ernexbcn0
my best suggestion would be to get a new box with mint versions of everything including of course MySQL, upgrading those redhat installations is tricky and it might break other shit in the process
- vaxorcist0
Sorry for the rant, but I was in situations like this years ago due to braindead management decisions I mistakenly said yes to...
This is a common problem... developers taking the fall on a gig that's lacking in System Administration..... attempting to retrofit almost always wastes TONS of time and may not work anyway
Is there some system that's PHP4 only? Does the box have some old stuff that only works on older kernals? TRY to avoid supporting orphan-ware! It can only suck big time...
PHP4 is end-of-lifed.... get off it as soon as possible and be ready to update whatever has to be updated... and bill the client for this, unless if was your company's decision to stick with PHP4....... if you stay on an old system like PHP4, beware that if somebody finds a security hole, it may not be fixed, and won't get the attention that PHP5 gets...
- vaxorcist0
Honestly, if you have pretty clean code, migrating to a new box is a predictable amount of time, but retrofitting old modules is an unpredictable hell..... so I highly suggest biting the bullet and stopping the dance... breathe deep, tell the client 2 more weeks or whatever, but be willing to stick to it and if you deliver in 2 weeks (or whatever) the client will begin to trust you again....
otherwise it's a treadmill of hell
- mrsprinkles0
I highly recommend using a configuration management tool like puppet for your future sites. It makes provisioning and migrating a snap. I'm rolling it on a 30 server cluster right now and it works wonders.
- dMullins0
Thank you guys! I have been of the opinion since first pushing the site live that we needed to upgrade, but because of the client's aggressive go-live expectations (for last year's holiday rush) we had to just get the site rolling. I knew this would happen in some way.
I've railed against retro-fitting and FINALLY got everyone to agree to my original recommendation from November of '09. We'll be migrating to a new dedicated server instead.
Thanks, again.