{"id":1074,"date":"2009-01-09T13:32:20","date_gmt":"2009-01-09T12:32:20","guid":{"rendered":"http:\/\/blog.ginchen.de\/?p=1074"},"modified":"2009-04-12T15:51:58","modified_gmt":"2009-04-12T13:51:58","slug":"schoenheitsfehler-im-wordpress-plugin-firestats","status":"publish","type":"post","link":"http:\/\/blog.ginchen.de\/en\/2009\/01\/09\/schoenheitsfehler-im-wordpress-plugin-firestats\/","title":{"rendered":"Blemish in WordPress plugin “FireStats”"},"content":{"rendered":"
\"FireStats\"<\/a>
FireStats<\/figcaption><\/figure>\r\n\r\n\r\n\r\n\r\n

Actually I didn’t want to write about this at all, but now I see that some people googled for the very same error message that I recently got from FireStats<\/a> as well:<\/p>\r\n\r\n

Wrong parameter count for debug_backtrace()<\/p><\/blockquote>\r\n\r\n

Obviously Google combed through my site just at the time when it was littered with that unlovely error message, and thereby a couple of searchers wound up here – who probably left soon, because there is really nothing to find about that subject here. :)
\r\nSo in order to not disappoint future guests, I will quickly explain how I got rid of that error again.<\/p>\r\n\r\n\r\n\r\n\r\n

Ganz am Ende der Datei firestats\/php\/utils.php<\/code> befindet sich folgende Funktion:<\/p>\r\n\r\n

\r\nfunction fs_called_by($function)\r\n{\r\n\t$bt = debug_backtrace(false);\r\n\tfor($i = count($bt)-1;$i >= 0;$i--)\r\n\t{\r\n\t\t$frame = $bt[$i];\r\n\t\tif ($frame['function'] == $function) return true;\r\n\t}\r\n\treturn false;\r\n}\r\n<\/pre>\r\n\r\n
Die Funktion debug_backtrace()<\/code> hatte ursprünglich gar keine Parameter. Erst seit PHP 5.2.5 ist es möglich, der Funktion einen Boolean-Wert, also true<\/code> oder false<\/code>, zu übergeben:”debug_backtrace(php.net)”:http:\/\/www.php.net\/manual\/de\/function.debug-backtrace.php . Wenn man nun aber auf seinem Server ein älteres PHP laufen hat als Version 5.2.5 – was heutzutage durchaus noch oft vorkommt – dann kennt er natürlich nur eine Funktion debug_backtrace()<\/code> ohne<\/em> Parameter. Und deshalb streikt er dann auch, wenn FireStats versucht, der Funktion einen Wert zu übergeben.<\/p>\r\n\r\n
Die Lösung ist simpel, man muß den Parameter einfach löschen – ich weiß gar nicht, warum er da überhaupt steht, er wird ja sowieso nicht gebraucht. Also einfach Zeile 1042 ändern in:<\/p>\r\n\r\n
$bt = debug_backtrace();<\/pre>\r\n\r\n\r\n\r\n
At the very end of the file firestats\/php\/utils.php<\/code>, you find the following function:<\/p>\r\n\r\n
\r\nfunction fs_called_by($function)\r\n{\r\n\t$bt = debug_backtrace(false);\r\n\tfor($i = count($bt)-1;$i >= 0;$i--)\r\n\t{\r\n\t\t$frame = $bt[$i];\r\n\t\tif ($frame['function'] == $function) return true;\r\n\t}\r\n\treturn false;\r\n}\r\n<\/pre>\r\n\r\n
Originally, the function debug_backtrace()<\/code> had no parameters at all. Only since PHP 5.2.5 it is possible to pass a Boolean value, i. e. true<\/code> or false<\/code>, to the function:”debug_backtrace(php.net)”:http:\/\/www.php.net\/manual\/en\/function.debug-backtrace.php . Now, if your server is running a PHP version prior to 5.2.5 – which still occurs quite often these days – it will only know a function debug_backtrace()<\/code> without<\/em> any parameters. And that causes it to fail as soon as FireStats tries to pass a value to the function.<\/p>\r\n\r\n
The solution is simple, you only have to delete the parameter – I don’t know why it’s there anyway, it isn’t needed at all. So, just change line 1042 into:<\/p>\r\n\r\n
$bt = debug_backtrace();<\/pre>","protected":false},"excerpt":{"rendered":"Actually I didn’t want to write about this at all, but now I see that some people googled for the very same error message that I recently got from FireStats as well: Wrong parameter count for debug_backtrace() Obviously Google combed through my site just at the time when it was littered with that unlovely error […]","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[77],"tags":[196,197,144,606],"_links":{"self":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/1074"}],"collection":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/comments?post=1074"}],"version-history":[{"count":25,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/1074\/revisions"}],"predecessor-version":[{"id":1083,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/posts\/1074\/revisions\/1083"}],"wp:attachment":[{"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/media?parent=1074"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/categories?post=1074"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.ginchen.de\/en\/wp-json\/wp\/v2\/tags?post=1074"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}