2 simple debugging tips for WordPress developers

[@TechiePress]

I have a snippet I wrote for my editor similar to your wp_var_dump for all projects use. Had never considered coloring it. Yours looks more appealing.

[@HighriseDigital]

Thanks. Glad you found it useful.

[@Traveltoppereu]

On my website, which has been translated into five languages ​​with Polylang, all pages except Dutch suddenly show a 404 error message. I tried to solve this with a 301 but it doesn't help. I read that debugging would help but I have no knowledge of how to do that. Greetings from Eddy

[@TonyGirling]

I either use xDebug - that way it's easy to see the call stack as well as all variables and structures, and inline outputting. When I have to I will insert inline debug information - the trick is to make sure all instances are removed BEFORE uploading to the live server. Easy for automated deployments, but another step when manually FTP'ing. For inline outputting I prefer using a code snippet in VS Code. That way it will work for any PHP project. Here's a view of my php.json file. "Pre": { "prefix": "pre", "body": [ "echo '' . print_r($foo, true) . '';", ], "description": "Echo Var Dump" } In the use case for debugging on a live server (sometimes required) then the output debug file is my preferred route - avoids screen dumps which visitors will see.

[@HighriseDigital]

Thanks for sharing the snippet, Tony! I need to get into the habit of using those more often - they're so useful! KD