| CARVIEW |
Select Language
HTTP/2 301
server: nginx
date: Mon, 02 Feb 2026 17:17:47 GMT
content-type: application/rss+xml; charset=UTF-8
location: https://westi.wordpress.com/comments/feed/
x-hacker: Want root? Visit join.a8c.com/hacker and mention this header.
host-header: WordPress.com
link: ; rel="https://api.w.org/"
vary: accept, content-type, cookie
last-modified: Mon, 02 Feb 2026 17:17:46 GMT
etag: "e3eb175c8245af640ec5f67bf5ae2f29"
x-redirect-by: WordPress
x-ac: 1.bom _dca MISS
alt-svc: h3=":443"; ma=86400
strict-transport-security: max-age=31536000
server-timing: a8c-cdn, dc;desc=bom, cache;desc=MISS;dur=438.0
HTTP/2 200
server: nginx
date: Mon, 02 Feb 2026 17:17:47 GMT
content-type: application/rss+xml; charset=UTF-8
vary: Accept-Encoding
x-hacker: Want root? Visit join.a8c.com/hacker and mention this header.
host-header: WordPress.com
link: ; rel="https://api.w.org/"
vary: accept, content-type, cookie
last-modified: Mon, 02 Feb 2026 17:17:47 GMT
etag: W/"759b28e22c3de7ede04c78fe699c7f53"
content-encoding: gzip
x-ac: 2.bom _dca MISS
alt-svc: h3=":443"; ma=86400
strict-transport-security: max-age=31536000
server-timing: a8c-cdn, dc;desc=bom, cache;desc=MISS;dur=435.0
Comments for westi on wordpress
https://westi.wordpress.com
the often forgotten diary of a wordpress developer
Wed, 07 Aug 2013 13:50:09 +0000
hourly
1
https://wordpress.com/
-
Comment on SSL all the things by Ryan Hellyer
https://westi.wordpress.com/2013/08/07/ssl-all-the-things/comment-page-1/#comment-19829
Wed, 07 Aug 2013 13:50:09 +0000
https://westi.wordpress.com/?p=6394#comment-19829
Random. I assumed it always used https
]]>
-
Comment on SSL all the things by Joseph Scott
https://westi.wordpress.com/2013/08/07/ssl-all-the-things/comment-page-1/#comment-19828
Wed, 07 Aug 2013 13:49:35 +0000
https://westi.wordpress.com/?p=6394#comment-19828
Hard to argue against more SSL. More SSL, more better.
]]>
-
Comment on Tracing things back to where they came from by Peter Westwood
https://westi.wordpress.com/2012/01/28/tracing-things-back-to-where-they-came-from/comment-page-1/#comment-14183
Sun, 29 Jan 2012 11:14:02 +0000
https://westi.wordpress.com/?p=6337#comment-14183
In reply to Luke Gedeon.
-
Comment on Tracing things back to where they came from by Luke Gedeon
https://westi.wordpress.com/2012/01/28/tracing-things-back-to-where-they-came-from/comment-page-1/#comment-14182
Sun, 29 Jan 2012 05:38:59 +0000
https://westi.wordpress.com/?p=6337#comment-14182
I add backtrace to deprecation notice filters in my functions.php so I can find when plugins are using deprecated stuff. Needed because notices only tell you where in the core code the bad arg/func happened, but not the plugin that called the core code.
-
Comment on Tracing things back to where they came from by Stephane Daury
https://westi.wordpress.com/2012/01/28/tracing-things-back-to-where-they-came-from/comment-page-1/#comment-14179
Sat, 28 Jan 2012 18:12:38 +0000
https://westi.wordpress.com/?p=6337#comment-14179
Nice! From your “guess I need to give better trace results” the other week to this? Love it. Thanks Westi!
]]>
-
Comment on Tracing things back to where they came from by Ryan McCue
https://westi.wordpress.com/2012/01/28/tracing-things-back-to-where-they-came-from/comment-page-1/#comment-14178
Sat, 28 Jan 2012 15:42:04 +0000
https://westi.wordpress.com/?p=6337#comment-14178
In reply to Peter Westwood.
-
Comment on Tracing things back to where they came from by Peter Westwood
https://westi.wordpress.com/2012/01/28/tracing-things-back-to-where-they-came-from/comment-page-1/#comment-14177
Sat, 28 Jan 2012 15:23:23 +0000
https://westi.wordpress.com/?p=6337#comment-14177
In reply to Ryan McCue.
-
Comment on Tracing things back to where they came from by Ryan McCue
https://westi.wordpress.com/2012/01/28/tracing-things-back-to-where-they-came-from/comment-page-1/#comment-14176
Sat, 28 Jan 2012 15:09:57 +0000
https://westi.wordpress.com/?p=6337#comment-14176
This is why I like exceptions; they automatically include a backtrace with them. 😉
]]>
Nice.
With the development version of the Debug Bar you will get the simple backtrace for Deprecated function calls / includes too. Of course this only catches the ones on pages you interact with as a (Super) Admin user. Being able to find these more easily was one of the reasons this came about 🙂
]]>Let’s see if this sample code will paste:
function plugin_backtrace() {
var_dump(debug_backtrace());
}
add_action( ‘deprecated_argument_run’, ‘plugin_backtrace’ );
add_action( ‘deprecated_function_run’, ‘plugin_backtrace’ );
Yep, and you have to handle WP_Errors before you try using them 🙂
]]>True, but you do have to catch them before they run away 😉
]]>