File Genie PHP Support Product Page
Solved
Strict Standards error
Reported 30 Mar 2010 21:59:51
5
have this problem
30 Mar 2010 21:59:51 Fafchamps Thierry posted:
I receive the following error :Strict Standards: usort() expects parameter 2 to be a valid callback, non-static method fileObj::cmp_extension() should not be called statically in ../ScriptLibrary/incFileGenie.php on line 169
What can i do ?
It seems there is a lot of little errors with the last PHP 5.3.2 and your PHP extensions...[V]
Edited by - Fafchamps Thierry on 30 Mar 2010 22:00:08
Replies
Replied 06 May 2010 18:58:04
06 May 2010 18:58:04 Fafchamps Thierry replied:
No answer ???
Any suggestion ?
Thanks for you help.
Any suggestion ?
Thanks for you help.
Replied 20 Nov 2012 20:18:12
20 Nov 2012 20:18:12 Phil Boyle replied:
I am getting this error again on my testing server.
Strict Standards: usort() expects parameter 2 to be a valid callback, non-static method fileObj::cmp_fileName() should not be called statically in C:\xampp\htdocs\HBClub\ScriptLibrary\incFileGenie.php on line 169
I never did get a reply.
Strict Standards: usort() expects parameter 2 to be a valid callback, non-static method fileObj::cmp_fileName() should not be called statically in C:\xampp\htdocs\HBClub\ScriptLibrary\incFileGenie.php on line 169
I never did get a reply.
Replied 01 Jan 2013 12:20:31
01 Jan 2013 12:20:31 Liam Hamer-Nel replied:
I have just started using this extension and am getting the following error. Any assistance would be appreciated.
Strict Standards: usort() expects parameter 2 to be a valid callback, non-static method fileObj::cmp_fileName() should not be called statically in C:\xampp\htdocs\wp2010\ScriptLibrary\incFileGenie.php on line 193
Strict Standards: usort() expects parameter 2 to be a valid callback, non-static method fileObj::cmp_fileName() should not be called statically in C:\xampp\htdocs\wp2010\ScriptLibrary\incFileGenie.php on line 193
Replied 21 Mar 2014 07:00:39
21 Mar 2014 07:00:39 Phil Boyle replied:
Was there ever a solution to this as it was marked as solved. I have the error displaying on a live website at present.