Now that we've covered debugging Drupal 8 in PhpStorm using local web-based approaches, let's move on to command line debugging.
I started out writing articles for print media in the late 1990s. My passion for technology made transitioning
into web development a natural progression. Since 2000 I have been working for successful startups like
Systinet (currently HP Software), and Home24, and big companies like Telefónica O2 and Sita. In 2010 I began
officially freelancing as a Drupal developer, quickly developing any and all skills required by a diverse array
of clients in Germany.
I joined Acquia in 2015, and my experience as a developer, consultant, and analyst gives me unique insights
into every aspect of dreaming, building, and deploying Drupal web applications.
- Acquia Certified Developer
- Acquia Certified Developer - Back End Specialist
- Acquia Certified Developer - Drupal 8
Recent Blog posts
Lots of people think that template engines like Twig cannot be interactively debugged. I heard this several times as an argument against template engine, and for using legacy php processing like phptemplate (standard in Drupal 7).
Well, it’s not entirely true.
Debugging Drupal 8 in PhpStorm: Local Web-based Debugging in Mac OS X, Acquia Dev Desktop 2, and XDebug
Welcome to Post #2 in my series about debugging in Drupal 8.
Welcome to my series of blogs about debugging in Drupal 8.
The reason why I decided to create this series is that a lot of Drupalists use ”legacy” ways of non-interactive debugging based on php-native commands like
debug_print_backtrace() or commands provided by contributed modules or themes like
dump() inside of twig templates.