PhpStorm 2017.1 EAP 171.3566: IP for Zend Debugger, new Find In Path, highlighting of current editor tab

The new PhpStorm 2017.1 EAP build (171.3566) is now available! You can download it here or via JetBrains Toolbox App. Or, if you have the previous PhpStorm 2017.1 EAP build (171.3224) installed, you should soon get a notification in the IDE about a patch update.

This build delivers new features, bug fixes and improvements for PHP and the Web, and takes on the latest improvements in IntelliJ Platform.

Allow choosing IP to be sent to Zend Debugger

In this build, we’ve added a new option enabled by default, which automatically detects all host IPs to sent them to Zend Debugger. That’s especially important when working on a machine with multiple IPs, e.g. in the case of Vagrant/VirtualBox/VPN usage. You can also disable a checkbox and provide required IPs manually. The option can be found in Settings| PHP | Debug | Automatically detect IDE IP.


Redesigned Find In Path

We redesigned  “Find in Path” window, so you get more valuable information within the same frame. Now you have options and preview tab combined in a popup and can see the results of your search with more detailed preview. Let us know what you think!


Highlighting of current editor tab for Darcula

There is a request that active editor tab is too subtle, especially in Darcula, so we’ve introduced an additional highlighting with a blue line. It makes it easier to distinguish between the currently active editor tab and those around it.


Apart from new features, this build brings many bug fixes, including these:

  • Huge gutter icons in latest 2017.1 EAP: IDEA-168194
  • CommonJS: module functions not available when re-exporting module instance: WEB-17099
  • Dead key is processed in editor as a separate symbol JRE-208

See the full list of bug-fixes and improvements in our issue tracker and the complete release notes.

Learn more about other new features in PhpStorm 2017.1:

  • PhpStorm 2017.1 EAP, 171.1834: New code highlights, parameter hint for method and function calls, new quick-fix for undefined variables, support for emoji in the editor
  • PhpStorm 2017.1 EAP, 171.2014: Fixes of reparse errors for alternative syntax, switch statement and namespace names; current scope highlighting for alternative syntax, more
  • PhpStorm 2017.1 EAP, 171.2152: Blank lines before namespace code style setting, align assignment now affects shorthand operators, “Download from…” option in deployment
  • PhpStorm 2017.1 EAP, 171.2272: Regexes support in Copyright Plugin, new Code Style options (Place ‘()’ for constructor, Convert else if/elseif to)
  • PhpStorm 2017.1 EAP, 171.2455: Support of PHP 7 Uniform Variable Syntax, auto-import of functions and constants, auto-import from the global namespace, more
  • PhpStorm 2017.1 EAP, 171.2613: Support of Blade @component and @slot directive document structure, grouping of user-defined constants in Debugger
  • PhpStorm 2017.1 EAP, 171.2822: Support PHPDoc in Blade injections, Recognition of PHP class names in strings
  • PhpStorm 2017.1 EAP, 171.3019: Support of Codeception, Configurable spaces inside declare statements, Support of PHPUnit 6, and more
  • PhpStorm 2017.1 EAP 171.3224: Improvements in PHP Debug, Auto-import and FQN inspection

Download PhpStorm 2017.1 EAP build 171.3566 for your platform from the project EAP page or click “Update” in your JetBrains Toolbox App and please do report any bugs and feature request to our Issue Tracker.

Your JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Early Access Program, Newsletter. Bookmark the permalink.
  • Yevhen Tretiak

    When stable version will be available?

    • Maxim Kolmakov

      I can’t say the precise date yet, but it will be available somewhere in March/April.

  • Paul Yakubets

    Hi, and many thanks for the new build.
    I have just reported about the issue with class_alias() function using.

    • Maxim Kolmakov

      Thank you for the report! Let’s continue there.

  • RobM

    The huge gutter icons was a bug? I actually liked it!

  • therrst

    I like what you’re trying to do with “Find/Replace in Path” windows except:

    I don’t like how they automatically close when they lose focus. Even switching to a different program on a different screen closes the window.

    In the “Replace in Path” window: Using the keyboard to navigate between fields actually places a literal tab into the text boxes instead of changing focus to the next text box.

  • Ashok Gelal

    Project scopes + Autoscroll from Source combo is broken in PS 2017.1 EAP since the beginning. I couldn’t verify whether it is just me or if it is really broken.

  • Venimus

    I’m missing ‘filter by path/extension’. In a projects with tens of thousands of files finding common words is tedious without filtering the file extension.

  • Zemistr

    “Highlighting of current editor tab for Darcula”
    It’s not working properly with splitted window.

  • BlueM

    I hate the new “Find in Path” dialog. What I especially find a major usability drawback is the pretty narrow File mask input field. Often, I have something like “*.ts,*.html,*.sass,*.php,*.less” in there, and with the new dialog, I can’t see this.
    Apart from that: again, the keyboard mnemonics for switchin the scopes are broken on macOS (they will enter a character instead of being recognized of shortcuts). I really don’t recall how many bug reports I have filed regarding exactly at this issue (not only in this window, but also in the editor’s Search bar) in the last years …

    • Anna Lebedeva

      Thanks for your feedback! Will pass it to the development team

  • disqus_A206IMJQiP

    I really don’t like the new “Highlighting of current editor tab for Darcula” style. It makes all the tabs equally bright resulting in a huge area at the top of the screen a lot brighter than the rest of the IDE even that’s not the most important area. I prefer the old styles, where only the active tab was brighter and the rest were darker.

    The new blue line at the bottom of the current tab is fine, but I cannot find where to change its color. Is it possible? Also, a setting to completely disable it would be nice. Or even make it the same color of the file according to its VCS status (modified, new, etc).

    • Anna Lebedeva

      Thank you for the feedback, will pass to the development team

  • Adam

    What with supporting php7/7.1? Can’t use return types :(

    abstract class A
    * @return A
    public function foo(): A
    return $this;

    class B extends A
    * @return string
    public function bar(): string
    return ‘foobar!’;

    $b = new B();
    echo $b->foo()->bar();

    “Method bar() not found in ‘A'” warning… It used to work before (with “@return $this” annotation), but I can’t use “@return $this” with return type (“Return type does not match”).

    It is really funny thing, but scratch buffer (with PHP lang set) doesn’t see any method of $b… But it works in regular file…

  • maddocnc

    Cucumber.js plugin also updated, but still no support for 2.0.0-rc7(default in npm)?
    Test passed via cli, but Run(cucumber) window shows “Test framework quit unexpectedly”, and there is some cucumber output parsing errors I think, because I see something like this:

    2 scenarios ([33m1 undefined[39m, [32m1 passed[39m)

    6 steps ([33m2 undefined[39m, [32m4 passed[39m)


  • xandr

    Not a fan of the new “Find in Path” dialog window. I liked having it docked at the bottom of the screen with file names left aligned. Could easily scroll, click and open multiple files over time. Can you make the new find in path optional for those who like how it worked before?

    • Eugene Morozov

      You still can get this view – just click Open in Find Window.

      • aqwantonio

        сделайте опцию в настройках, чтобы можно было настроить как открывать это окно по умолчанию! или чтобы сохранялось расположение последнего открытого окна поиска (внизу или по центру)

      • xandr

        OK, glad to see it’s still there. Do you know how to default that view though?

        • Eugene Morozov

          It was not default in previous versions – you had to click OK previously, you have to click Open in Find Window now.
          Also, this view doesn’t have a search field, as before.

  • PAC

    I quite dislike the new “Find in Path” too. Especially because it disappears when the window losses the focus, which is a pain if I want to copy’n’paste stuff from other windows. Now I have to concatenate several pieces of strings in a separate editor before copying al that so I can paste in the “Find in Path” window. Even though this is not something I do often, it is annoying when the situation arises.
    Another thing less important bu still: moving and resizing the “Find in Path” window feels like the system is struggling like hell as it is anything but smooth. Not really a problem though. Seems weird, that’s it.

    Honestly all in all, I’m sorry but I don’t see how the new design brings any advantages over the previous version :/
    Maybe I’m just not used to it.

    • Olaf

      The fact that the window closes when it loses focus is so annoying, it almost but me off using PhpStorm altogether (almost, but not quite :-) ). It totally disrupts my workflow. Please add at least a pin button. Better still: an option to use the old dialog.

      • PAC

        I agree, and yes I’d like an option to get the old version back too. Plus, Time to time, the focus is not automatically put on the search field, and I end up typing my string to search nowhere. That is frustrating. And I could not narrow down when exactly this happens.

        Really, I don’t like this new search interface :(

  • Marcin Marcinkowski

    I dislike the new “Find in Path” too. Is any way to open find in path like in prev version ?

  • Patrick Ratelband

    I would really like the option to have the “Find in path” to automatically open in the find window without having to press CTRL+ENTER to do so.

    • Eugene Morozov

      How would we know when you have finished entering the search request?
      Previously, you had to click OK, now you have to click Open in Window. Not much of a difference, don’t you agree?

      • Patrick Ratelband

        I am sorry, I see now I was not clear in what I meant.

        I would like to have the option to make ENTER instead of CTRL+ENTER open the results in the “find in path” window. I often am not looking for a single instance of something when I do a search in path, but for all instances of something. The default behavior of going to the found file and closing the window is counter productive for that.

        • PAC

          I agree with that. I was expecting to switch to the ‘find in path’ when hitting “ENTER” too.

  • afisher88

    Having lots of problems with the new “Find in path” window. Keep having to restart Webstorm because I’m not able to close the window when I click off of it.

    Would much rather have an “x” to close the window rather than having to click off of it. This problem is made worse by it being very buggy.

  • Steve Ardagh-Walter

    I’m using 2017.1.2. I actually like much of the new window, however one bug is that this is impossible to close unless I ‘Open in Find Window’ . If I see what I want in the initial dialog, I shouldn’t have to open a new window to close it …