© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Hm... actually, if it's an E_STRICT error, what prevents it from being displayed in Mahara is *not* our error_reporting setting. It's that in $error_lookup we haven't mapped them to one of the Mahara error/warning types.
So it's pretty strange you're seeing that message, Kristina. Perhaps it changed error classes at some point...
Well, in any case there are a lot of E_STRICT notices it would be good to clean up in Mahara. But I don't think we want to start showing E_STRICT's to people who have just set productionmode to false, because there are about 30 of them that show up on each page load, due to the fact that we have a lot of abstract static functions in the codebase, and those now throw an E_STRICT notice. We should limit it to people who have turned on developermode, I think, and we should fix those every-page E_STRICT's.