As mentioned, this is a result of php.ini settings.
Technically, it's due to the code violating STRICT standards as identified in the errors.
However, to hide the errors from appearing on your development web pages, you have a few options.
- Disable the PHP messages - or at least reduce what's reported
- Hack the code and temporarily disable warnings around the offending lines code
For Choice #2, I posted the "temp hack" solution separately since the original reply post became *huge* ... well, both still are huge but now it's two less huge chunks ... temp hack post coming up next!
~~~~
For choice #1 ... php.ini
All of the following assume you have access to the php.ini and can restart the web server after making changes.
In the php.ini file ... this should be located in your php.ini installation directory (./php/php.ini)
Locate the line which defines the "error_reporting" flags which will look something like:
Code: Select all
error_reporting = E_ALL | E_STRICT
To hide the "Strict Standards" error messages, remove the "| E_STRICT" portion. For example:
However, "E_ALL" includes the E_NOTICE flag (the "Notice: Trying to get property of non-object..." messages). So you can bitwise that flag out using:
Code: Select all
error_reporting = E_ALL | ~E_NOTICE
Or, alternatively, you can explicitly set the flags you want such as the major errors:
Code: Select all
error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
Remember, you are
hiding the error (and notice) warnings. In other words, errors in any php code
you write will also be hidden. Therefore, I
highly recommend keeping the E_STRICT (and E_NOTICE) flags enabled in development. Otherwise, unsafe coding will happen (accidentally of course).
The "good" news is ... your live web host server probably has all flags disabled except for ERROR messages Or, possibly, redirected to a log file or a devnull - so they probably won't appear. Probably. Maybe.
In my case I ran into it on J1.6 when I installed Jumi ...
The
real solution is to fix the errant code in ./jumirouter/jumirouter.php and ./jumi/jumi.php.
However, I'm reluctant to hack the jumi codebase since I''m
sure a proper fix is on the way in the next release.
[I'm cross-linking the post from
[email protected] (
http://edo.webmaster.am/forum/post2145.html#p2145) to this thread]