Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#2790 MIME 5.4 php Strict error

closed-invalid
nobody
None
5
2012-05-29
2012-05-28
No

mime.php error Strict warning apparently a php bug in v5.4 solved by setting
error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT
or some have
error_reporting = E_ALL | E_DEPRECATED
work for them I would suggest including a .htaccess file if you don't have access to php.ini

It is a snaffu caused by new OOP Strict Static methods and being that this is not written OOP it conflicts with PHP OOP Standards. Pear has this problem too and PHP insists that it is not there problem. HMMM

So it appears that until aspell is rewritten using class files that this will be a continuing problem
the actual solution is :

class { // something in the class declaration but it would cause a complete code rewrite
public static function mime_structure ($bodystructure, $flags=array()) {

Discussion

  • You should always include full error text with any bug reports you make.

    Thank you for taking the time to try to make a report, but you cite a couple different parts of the SquirrelMail code without specifics, and your analysis is scattered and inaccurate/misinformed.

    You might be referring to the second to last and third to last warning messages here:

    https://sourceforge.net/tracker/?func=detail&atid=100311&aid=3491925&group_id=311

    If so, yes, they will go away if you turn off E_STRICT, but no, that matter is not a bug - either in PHP or in any other application. Generally speaking, if you run a production server, you should never have E_STRICT (or E_ALL for that matter) turned on.

    Thanks again.

     
    • status: open --> closed-invalid