~/talk

Drupal Development with PHPStorm and Xdebug

links:none on file
slides:none on file

Step-by-step setup for PhpStorm + Xdebug and how to make breakpoints actually stop PHP execution: enable Xdebug in php.ini (uncomment the module), set the XDEBUG_IDE_KEY, start PhpStorm listening and add a matching remote server, use the Chrome Xdebug Helper bookmarklet or extension to toggle sessions, and map server paths when using Drupal VM so files match. Demo shows a breakpoint in Drupal bootstrap halting execution and variables visible in the IDE; it works when mappings and IDE key are correct.

AI-written summary · about

  1. 0:00Introduction
  2. 1:51IDE history and selection
  3. 4:56PHPStorm features
  4. 9:30Configuring Drupal in PHPStorm
  5. 14:17Acquia Dev Desktop setup
  6. 18:09Xdebug with Acquia Dev Desktop
  7. 30:19Xdebug with Drupal VM
  8. 39:37Q&A and closing
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.