PHPSTORM DEBUG DRUPAL PROJECT CODE

In the left-hand pane, select Drupal Module. For Drupal 8, a module_ file is generated.Ĭhoose File | New Project or click Create New Project on the PhpStorm Welcome screen. PhpStorm generates and configured a project stub in accordance with the selected Drupal version. No need to restart the IDE or PHP, just restart the debugging run configuration, and it works beautifully.You can create a PhpStorm project by a Drupal Module template, this project will be set up and configured in accordance with the Drupal requirements. In PhpStorm 2018.1.2 for macOS, the settings can be found at PhpStorm / Preferences / Languages & Frameworks / PHP / Debug in the External connections part of the right pane, as shown below. So all it takes is increase the number of connections! but is blocked by the single connection limit of the default configuration. The solution was suggested by the always helpful and knowledgeable : PhpStorm happens to set a limit to the number of simultaneous connections it will accept for debugging, and that limit is 1 by default.Īll of a sudden, it made sense: during classical debugging, the PHP interpreter from the host site establishes one connection to the client (the PhpStorm IDE), but when invoking the child site during such a call, a second instance of the interpreter is started and tries to connect too.

PHPSTORM DEBUG DRUPAL PROJECT CODE

And indeed, dumping the page with $this->getSession()->getPage()->getContent() show it to contain a typically timeout page.Įxamining the logs showed the timeout happened at the PHP level, during the opposite direction call performed by Xdebug towards the debugging client, although such calls obviously worked since I'd been stepping through code for hours before that. Indeed, evaluating the result of the call via $this->getSession()->getStatusCode() after that call returned show a 504 Timeout HTTP status code.

Stepping into UiHelperTrait::drupalLogin(), I noticed the delay occurent during the drupalGet('user/login') call early in the method, before submitting the account identification. While converting the old-style functional tests in the MongoDB project from WebTestBase to BrowserTestBase, I stumbled upon a problem: after following the instructions to run PHPunit tests from PhpStorm, doing step-by-step debugging in the IDE worked nicely, but then stopped at the first $this->drupalLogin() call, returning a 404 after a very long delay, although the same call running without debugging worked normally. : The new social network features of Le Figaro are now powered by an OSInet-designed MongoDB implementation.: Completed migration of FranceInfo.FR from SPIP to Drupal.: Sotchi Olympics traffic not a problem for, which I rearchitected on Drupal 7 in 2013.: 400% speedup in 3 weeks for : who said Drupal back-offices had to be slow ?.: Our first Drupal 8 production site at France Télévisions is live.: 50% less server load with MongoDB on the Drupal 7 site factory at France Télévisions.: New Drupal 8 site galaxy (+/- 70 sites) for Agences Régionales de Santé architected and tech-led by OSInet, delivered by Klee.: New headless Drupal 8 / Symfony 3 site at FranceTV Sport, architected and tech-led by OSInet, with RabbitMQ.: New Drupal 8 site at Rue du Commerce, architected and tech-led by OSInet, just went throught Black Friday week with flying colors thanks to RabbitMQ.

Phpstorm debug drupal project