ansaurus

Question

Answer 1

+2 A:

I assume that PayPal Code is an external library from the PEAR Package your using that isn't 5.3 Strict comparable. There quite some Code that suffers from that Problem.

Assuming you don't want to change that Code and Submit it back ( ;) ) there aren't so many things you can do.

To name the first two that come to mind:

In your wrapper Code for the Paypal access turn of E_STRICT everytime before the call and back on after. E.g.

<?php
class myPayPalWrapper { 
    public function doX() { 
         $x = error_reporting(E_ALL & ~E_STRICT); # or something
         $this->externalPaypalClass->doX();
         error_reporting($x);
    }
}

doesn't look really pretty and requires a good amount of code.

If your are already using a custom errorhandler in your project you could extend that to filter out all errors of that lib. E.g.

<?php
function myErrorHandler($iErrno, $sErrstr, $sErrfile, $iErrline) {
    if(error_reporting() & $iErrno) {
        if(strpos("libFolder/paypal", $sErrfile) !== false) {
            return true;
        }
    }
    return false;
}

Hope that helps

edorian 2010-07-28 09:36:07

+1 for the turn-off-strict wrapper for ugly third-party code.

Charles 2010-07-28 16:15:42

That's great! :) We're using the first option but the second sounds more reasonable :)Thanks

DiogoNeves 2010-07-29 08:54:31

ansaurus

tags:

views:

answers:

PayPal error messages on PHP 5.3.1

related questions