by admin » Wed Sep 10, 2014 2:48 pm
hello Simon, the "strict standards" are due to compatibility with upcoming php 5.6 and they are nice to fix, but it's not always that easy especially for Virtuemart's or Joomla's core files. They do not cause any specific problems, but it's known that once you get them all fixed, the php processor should be much faster. You can disable the strict notices within joomla's error reporting to "none" or within php fpm's config files. I am using this config on production:
php_admin_value[error_reporting] = E_ALL & ~E_STRICT & ~E_NOTICE & ~E_DEPRECATED
and this config on demos:
php_admin_value[error_reporting] = E_ALL & ~E_STRICT &~E_DEPRECATED
an example of the strict error is:
class TestClass {
function Test()
{
}
}
calling function statically with TestClass::Test(); results to the strict notice because the function is missing "static" declaration.
Especially artio sef used to have problems of using a function both in an object way:
$nc = new TestClass();
$nc->Test();
together with calling the same function statically
TestClass::Test();
best regards, stan