Re: php update 5.3 -> 5.4; parseStructure() should not be called statically

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/11/2012 11:57 AM, David C. Rankin wrote:
> On 05/10/2012 10:19 PM, Paul Lesniewski wrote:
>> Thanks, we are aware of this.  We do not recommend E_STRICT error reporting.
>
> Thanks Paul -- that is just the default set by Archlinux with its php install.
> I'll look into changing the setting.
>

Paul,

   I'm still having difficulty turning the warnings/notices off in php . I 
currently have the error_reporting set at:

error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT & ~E_NOTICE & 
~E_USER_WARNING & ~E_USER_NOTICE

   I have tried:

error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
error_reporting = E_ERROR

(with server stop/start between each -- not just reload)

   However, squirrelmail 1.5.2 svn still displays the following at the bottom 
of each page:

SquirrelMail notice messages
Category: 	PHP
Message: 	Non-static method Message::parseStructure() should not be called 
statically
FILE: 	/srv/http/htdocs/squirrelmail/functions/mime.php
LINE: 	59
Category: 	PHP
Message: 	Non-static method Message::parseBodyStructure() should not be called 
statically
FILE: 	/srv/http/htdocs/squirrelmail/class/mime/Message.class.php
LINE: 	296

   What magic '& ~E_foo' do I need to set to safely prevent the display of the 
notices, but still preserving the display of actual errors?

   I'm beginning to think this is a php bug itself with error_reporting. 
Regardless what I do, I still get the following in the error log:

[Fri Jun 15 11:22:30 2012] [error] [client 192.168.7.124] PHP Strict 
Standards:  Non-static method Template::get_default_template_set() should not 
be called statically in /srv/http/htdocs/squirrelmail/include/load_prefs.php 
on line 34, referer: 
http://phoenix/squirrelmail/src/right_main.php?PG_SHOWALL=0&startMessage=1&mailbox=INBOX

[Fri Jun 15 11:22:30 2012] [error] [client 192.168.7.124] PHP Strict 
Standards:  Non-static method Template::construct_template() should not be 
called statically in /srv/http/htdocs/squirrelmail/include/load_prefs.php on 
line 499, referer: 
http://phoenix/squirrelmail/src/right_main.php?PG_SHOWALL=0&startMessage=1&mailbox=INBOX

[Fri Jun 15 11:22:30 2012] [error] [client 192.168.7.124] PHP Strict 
Standards:  Non-static method Template::calculate_template_images_directory() 
should not be called statically in 
/srv/http/htdocs/squirrelmail/include/load_prefs.php on line 530, referer: 
http://phoenix/squirrelmail/src/right_main.php?PG_SHOWALL=0&startMessage=1&mailbox=INBOX

[Fri Jun 15 11:22:30 2012] [error] [client 192.168.7.124] PHP Strict 
Standards:  Non-static method Template::calculate_template_images_directory() 
should not be called statically in 
/srv/http/htdocs/squirrelmail/include/load_prefs.php on line 531, referer: 
http://phoenix/squirrelmail/src/right_main.php?PG_SHOWALL=0&startMessage=1&mailbox=INBOX

[Fri Jun 15 11:22:30 2012] [error] [client 192.168.7.124] PHP Strict 
Standards:  Non-static method Template::get_default_template_set() should not 
be called statically in /srv/http/htdocs/squirrelmail/include/init.php on line 
537, referer: 
http://phoenix/squirrelmail/src/read_body.php?account=0&mailbox=INBOX&passed_id=42695&startMessage=1

[Fri Jun 15 11:22:30 2012] [error] [client 192.168.7.124] PHP Strict 
Standards:  Non-static method Template::construct_template() should not be 
called statically in /srv/http/htdocs/squirrelmail/include/init.php on line 
760, referer: 
http://phoenix/squirrelmail/src/read_body.php?account=0&mailbox=INBOX&passed_id=42695&startMessage=1

   I'll see if there are any bug reports open with php or Arch on the issue. 
If you can think of anything else, please let me know. Thanks for your 
continued work on squirrelmail!

-- 
David C. Rankin, J.D.,P.E.



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-----
squirrelmail-users mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx
List archives: http://news.gmane.org/gmane.mail.squirrelmail.user
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-users


[Index of Archives]     [Video For Linux]     [Yosemite News]     [Yosemite Photos]     [gtk]     [KDE]     [Cyrus SASL]     [Gimp on Windows]     [Steve's Art]     [Webcams]

  Powered by Linux