New to debugging in PhpStorm? Check out the Ultimate Debugging Guide or this Quickstart video on getting started with debugging in Docker. Now, set a breakpoint directly in your template file, just like you would with a PHP file, and begin step debugging! In the case of Laravel, just make sure you’re using version 5.8 or later, and you’re good to go.
In the case of Twig, you also need to set the following configuration options:
In PhpStorm, go to Settings/Preferences | Languages & Frameworks | PHP | Debug | Templates and specify the directories where your compiled files are stored:. Luckily, things have changed, and you can now debug your template files directly – there’s no difference between them and regular PHP files in this regard. So before PhpStorm 2019.1, your only option was to identify the compiled file, something like b84f5d6c0f0d85bb9187843.php, locate the line you want to place a breakpoint on, and then debug this file instead. They are first compiled into regular PHP and saved to a cache directory, and then the application runs those compiled files. I started with this: I can see that Xdebug is working: php-fpm/xdebug status with Xdebug v2.9.6, Copyright (c) 2002-2020, by Derick Rethans This is my PhpStorm config: I added a breakpoint and the debugger is not stopping. The problem was that template files are not the files your application runs. 2 I'm trying to configure Xdebug with PhpStorm and Laradock. 
In PhpStorm 2019.1, we’ve implemented debugging of Twig and Blade templates.
0 kommentar(er)
