$ composer require -dev drupal/twig_xdebug In theory, you should just be able to run: To continue execution, you would press the green play button or to stop execution you would click the stop icon in the debugger panel.īack on your host machine, open a terminal window and navigate to your project root, where your composer.json file exists. You can then use your debugger to inspect the available php variables. If all goes well, PHPStorm will listen for the xdebug connection and “catch” the request on the line you added the breakpoint to. Jump back to chrome and navigate to your site’s homepage. Start Listening for Debug Connections: Click the icon on the top that looks like a “old-timey” phone handset with a crossed out red circle at the top and little green bug at the bottom.
Add a breakpoint somewhere by clicking in the gutter, to the left of the code, and to the right of the line numbers.
Blt drupal vm install#
Install the chrome xdebug helper extension if you don’t already have it installed.īack in PHPStorm, navigate to your Drupal project index.php file. Let’s test to see that xdebug is running. On the following screen, you can just click “ok”. You may get an RSA warning that you can ignore and click yes. PHPStorm will automatically fill in the remaining settings after which you can just click ok. In my case it’s the box folder for my project.
Blt drupal vm plus#
Click on the plus icon, choose “Remote” and then select the “Vagrant” radio button and navigate to the “Vagrant Instance Folder”. Hint: type “CLI Interpreter” in the search field to find this quicker. Click the “…” to the right of the CLI Interpreter field. Open up the PHPStorm Preferences (⌘ + ,) and go to Languages & Frameworks > PHP. Next, we will need to setup PHP to use the remote interpreter on your VM. The next step is to get PHPStorm setup to listen to xdebug breakpoints.įirst, make sure your VM is running - $ vagrant up. If xdebug is running, you should see a bunch of lines related to xdebug on the screen. In your terminal window, ssh into the Virtual Machine (VM) with: $ vagrant ssh and run $ php -i | grep xdebug. Save config.yml and then open the terminal app, navigate to the same folder that your config.yml file lives in, and run: # Use PHPSTORM for PHPStorm, sublime.xdebug for Sublime Text. XDebug is disabled by default for better performance. Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/build/core/phing/tasks/local-sync.xml:12:30: Execution of the target buildfile failed.
Blt drupal vm code#
Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/build/core/phing/tasks/setup.xml:73:85: Drush exited with code 1 The drush command 'site-install lightning install_configure_form.update_status_module='array(FALSE,FALSE)'' could not be executed. Command site-install needs a higher bootstrap level to run - you will need to invoke drush from a more functional Drupal environment to run this command.
Ĭalling proc_open(ssh -o PasswordAuthentication=no -i /Users/XXXXX/.vagrant.d/insecure_private_key 'env COLUMNS=272 drush -local -alias-path=/Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/drush/site-aliases -nocolor -yes -verbose -uri=default -root=/var/ Loaded alias from file /Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/drush/site-aliases/ īegin redispatch via drush_invoke_process(). Executing '/Users/XXXXX/Documents/Clients/XXXXXX/dev/blted8/vendor/bin/drush -site-name="BLTed 8" -account-name="admin" -account-pass="admin" -l="default" -nocolor -yes -verbose site-install "lightning" "install_configure_form.update_status_module='array(FALSE,FALSE)'"'.
0 kommentar(er)
