A little static method declaration error

Fred isn’t noted for answering unless you buy a service contract. He has even been known to tell users who have not anted up that he has more important things to do on the product etc, since support to non subscribers doesn’t make him any money.

I can’t remember the cure, but there may not be one. It is just a “strict standards” notice, useful for future proofing your code. It is there so that plugin and application programmers can write clean, secure code.

I suggest that you look into changing your production errors string in php.ini or your fast cgi conf file to include ~strict. You also need to be sure that you are logging in production of course, not displaying errors. Many people just turn all errors off unless there is some problem, but that means paying attention ot your strict, notice and doingitwrong notes while you develop, and catching all the real world edge cases in testing. Not always possible 😉

Here, I give you a present, not a link to another cache product, but http://wordpress.org/extend/plugins/log-deprecated-notices/ which separates out your depreciated messages during dev and keeps track of them. That way your debug streams are uncluttered by endless repetition with every page load!

You know, I don’t recall at all how I fixed that. New Relic would pick it up in production and alerted me to it. I’m thinking maybe Fredrick did fix it, or maybe an upgrade to APC fixed things up.

Good luck!
Kurt