Le 18/05/2011 20:48, Javier Garcia a écrit :
Hi,
I'm getting this error:
Declaration of PayPal::raiseError() should be compatible with that of
PEAR::raiseError()
These are PayPal::raiseError() and PEAR::raiseError() respectively:
function&raiseError($message = null,
$code = null,
$mode = null,
$options = null,
$userinfo = null,
$error_class = null,
$skipmsg = false)
{
class PayPal extends PEAR
{
function raiseError($message, $code = null)
{
return parent::raiseError($message, $code, null, null, null,
'PayPal_Error');
}
I have found also this:
http://bugs.php.net/bug.php?id=46851
http://www.devnetwork.net/viewtopic.php?f=19&t=79211
The problem is maybe the class PEAR.php is been loading before
Paypal.php? How to control that in symfony?
sf 1.4
Javi
This has nothing to do with the order of autoloading. The issue is that
you overwrite a method without respecting the signature.
And btw, autoloading the child class will always trigger the autoloading
of the parent one as it is needed to have the complete definition.
--
Christophe | Stof
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
