We've all used echo, printr, and vardump to figure out why our code doesn't work. But did you know there's an easier way? This talk will demonstrate the use of two popular PHP tools: Xdebug and PhpStorm. Instead of littering your code with statements to send variable values to the browser, using these tools it's possible to pause script execution on a specific line, allowing you to view and edit any variable as well as arbitrary code. Never again will you forget to remove test code before sending it to production!

Comments

Comments are closed.

Holy crap, I feel like a carpenter that has been building houses for 30 years and just learned about this thing called a Tape Measure. I ?

Can't wait to start using the tools and techniques Tim showed us today. Thanks

Chris Gearhart at 11:24 on 9 Feb 2019

Great talk, I'm very interested in taking this back to my team to try this out!

Nate Bockoven at 11:55 on 9 Feb 2019

I've used xdebug before, and learned there's a skip method list and conditionals. Thank you!

James LaChance at 12:15 on 9 Feb 2019

This was a great overview of not only xdebug, but debugging in general, as well!

Great talk. Awesome job of connecting the dots and explaining everything.

I really liked the variety of ways covered on ways to use XDebug, and the specific examples and screenshots were nice, too. Using the integration with PHPStorm was a good call since so many people use it.

Not much to say. Great talk

Dana Luther at 12:00 on 10 Feb 2019

I’ve never gotten xdebug to work in PHPStorm before with our stack setup, so I’m very excited to try this out now that I know where to find the proper settings! I’ve only used it for coverage reports in the past.