Similar to this issue here with Atom php-debug 0.2.6. (although I have it working on PHPStorm so guess Xdebug setup is OK).
With Atom php-debug I get a socket error ... See screenshot below.
php-debug works fine at the point when execution hits Drupal's index.php and stepping through some PHP statements thereafter but as things progress towards MYTHEME.theme PHP program statements, php-debug will halt at the breakpoint but will show no variables and the vagrant Apache server will timeout? giving a Bad Gateway
First php-debug stops at index.php and shows variables.
Then it hits MYTHEME.theme (which is in a directory subordinate to the path mapping that allowed index.php to work. And yes, the statement was green moments before I took the snapshot but the variables were not shown - per the screenshot)
Similar to this issue here with Atom php-debug 0.2.6. (although I have it working on PHPStorm so guess Xdebug setup is OK).
With Atom
php-debug
I get a socket error ... See screenshot below.php-debug
works fine at the point when execution hits Drupal'sindex.php
and stepping through some PHP statements thereafter but as things progress towards MYTHEME.theme PHP program statements,php-debug
will halt at the breakpoint but will show no variables and the vagrant Apache server will timeout? giving a Bad GatewayFirst
php-debug
stops atindex.php
and shows variables.Then it hits MYTHEME.theme (which is in a directory subordinate to the path mapping that allowed
index.php
to work. And yes, the statement was green moments before I took the snapshot but the variables were not shown - per the screenshot)