Has anyone solved the strict standards error reporting problem, encountered when trying to use jms in joomla 2.54? I've tried various methods, culled from the net. I've changed the php.ini file, I've changed the Joomla config file. No luck. I've attached an images, here, to show the problem.

Strict standard message is a notification message that you can remove in the PHP.ini configuration.

You have to setup the error level.

In production (live), it is recommended to hide all the PHP error message.

See the parameter
- display_errors
- error_reporting

Here are the possible error reporting value that you can find in your php.ini

;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
; Error handling and logging ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;

; error_reporting is a bit-field. Or each number up to get desired error
; reporting level
; E_ALL - All errors and warnings (doesn't include E_STRICT)
; E_ERROR - fatal run-time errors
; E_RECOVERABLE_ERROR - almost fatal run-time errors
; E_WARNING - run-time warnings (non-fatal errors)
; E_PARSE - compile-time parse errors
; E_NOTICE - run-time notices (these are warnings which often result
; from a bug in your code, but it's possible that it was
; intentional (e.g., using an uninitialized variable and
; relying on the fact it's automatically initialized to an
; empty string)
; E_STRICT - run-time notices, enable to have PHP suggest changes
; to your code which will ensure the best interoperability
; and forward compatibility of your code
; E_CORE_ERROR - fatal errors that occur during PHP's initial startup
; E_CORE_WARNING - warnings (non-fatal errors) that occur during PHP's
; initial startup
; E_COMPILE_ERROR - fatal compile-time errors
; E_COMPILE_WARNING - compile-time warnings (non-fatal errors)
; E_USER_ERROR - user-generated error message
; E_USER_WARNING - user-generated warning message
; E_USER_NOTICE - user-generated notice message
;
; Examples:
;
; - Show all errors, except for notices and coding standards warnings
;
;error_reporting = E_ALL & ~E_NOTICE
;
; - Show all errors, except for notices
;
;error_reporting = E_ALL & ~E_NOTICE | E_STRICT
;
; - Show only errors
;
;error_reporting = E_COMPILE_ERROR|E_RECOVERABLE_ERROR|E_ERROR|E_CORE_ERROR
;
; - Show all errors, except coding standards warnings
;

Thanks for the suggestion. However, I've tried as many combinations of error display and reporting settings (in the php.ini file) as I could find on the net, and still I've had no luck. I've worked on it for hours. (We're talking Xampp 1.7.7, with Joomla 2.5.4)

Here's how my settings look at present:


; display_errors
; Default Value: Off
; Development Value: Off
; Production Value: Off

; display_startup_errors
; Default Value: Off
; Development Value: Off
; Production Value: Off

; error_reporting
; Default Value: Off
; Development Value: Off
; Production Value: Off

; html_errors
; Default Value: Off
; Development Value: Off
; Production value: Off

; log_errors
; Default Value: Off
; Development Value: On
; Production Value: On

Any suggestions?

I've got it down to only these errors showing, now. However, they are significant, in that they turn up on the frontend, and so I can't use the multisite softwared on this my main computer.

Strict Standards: Non-static method Jms2Win::matchSlaveSite() should not be called statically in C:\xampp\htdocs\joomla254\administrator\defines.php on line 45

Strict Standards: Non-static method Jms2Win::_getCurrentURL() should not be called statically in C:\xampp\htdocs\joomla254\includes\multisites.php on line 6

Strict Standards: Non-static method Jms2Win::_getHostInfo() should not be called statically in C:\xampp\htdocs\joomla254\includes\multisites.php on line 6

(I just managed to get it loaded successfully - no error notices - on my laptop. Which is great.)

In general, in production the php.ini contain

error_reporting = E_ALL & ~E_NOTICE
display_errors = Off

We can close this one, for me. I couldn't get it to work, no matter what changes I wrought to the php.ini file, to the joomla configuration file, or to the global configuration settings - anywhere that I could find error reporting settings.

At last, I read someone saying that the problem arrived in January 2011. So, I uninstalled Xampp 1.7.7 and installed 1.7.3; and - voila! - problem over.