PhpStorm 2016.3 Public Preview

We are happy to announce that today we released PhpStorm 2016.3 Public Preview for this year’s third and last major update of PhpStorm.

Everyone is very welcome to download and try its new features, bug fixes and other important improvements. As usual, we’re eager to hear your feedback on it in comments to this post or in our public issue tracker.


Learn all the details about the new features by visiting our website. Here are some notable highlights of this release:

Frameworks, Tools, more: 

  • Support of Docker in Remote Interpreters
  • Support of PHPSpec test framework
  • Auto-detection and configuration of PHPUnit, Behat, and PHPSpec from composer.json
  • Ability to open multiple projects in one frame
  • Support of Codeigniter Code Style

PHP Language & Editing Experience:

  • Semantic highlighting for variables and parameters
  • Сompletion of overridden methods and fields without function and var keyword
  • Improved support of PSR-0/PSR-4
  • New setting to select variable name without ‘$’ on double click
  • Support of list() and array of objects
  • Improvements in support for anonymous classes
  • Code Style Settings for PHP 7 return types

Code Quality Analysis:

  • Project-wide PHP 7 strict types,
  • New naming convention inspections
  • Improved Runtime Error Prevention

Please see our issue tracker for the full list of PHP-related issues fixed and release notes from the previous EAP build.

PhpStorm 2016.3 also brings major improvements in its support for top-notch web technologies, such as Flow support, improved TypeScript support, PostCSS support, Stylelint and much more.

From IntelliJ Platform this release borrows many new features and bug-fixes, such as enhancements in Version Control, which include better ergonomics and speed of VCS Log, reworked Merge dialog, syntax highlighting in the Diff and Merge dialogs, and an interface for managing Git remotes in the project.

Database tools have been significantly improved with the possibility to edit several similar cells at once, integration with mysqldump and g_dump utilities. Also, changes made in the Table Editor are now stored locally and submitted in bulk.

Please look at the overview of all PhpStorm 2016.3 features and download the build from the PhpStorm website. A patch update is already available from the previous EAP build (PhpStorm 2016.3 EAP 163.6957).

If you have any feedback to share with us, please leave your comments to this blog post or in our public issue tracker. Keep tuned as the PhpStorm 2016.3 release is just around the corner!

JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Early Access Program, Release Announcements. Bookmark the permalink.
  • Paul Yakubets

    Thnaks! What’s the difference with EAP?

    • Maxim Kolmakov

      Please see for the issues that have been resolved since the last EAP.

    • Anna Lebedeva

      In addition to new added changes from the last EAP, the difference is also in expected quality of the build. In our understanding EAP is an experimental version which you can use but on your own risk, we can’t guarantee anything. Public Preview it is still unfinished, but more stable version when we are ready to present features and we need more feedback.

      • Casp

        Does the Public Preview have 30 days license from the day you released it (like EAP) or is it a 30 day trial (i.e. 30 days from the day it is installed)

        • Maxim Kolmakov

          The Public Preview has the same license as EAP so its 30 days are not count as a trial.

  • Alexander Obuhovich

    Not sure if change was intended, but now:

    1. all folder/file icons are different
    2. the PHP file icon showing that it contains 1 class/interface/trait is gone and I see regular PHP file icon again
    3. the fonts on macOS Sierra look different (good, but different)

    • Maxim Kolmakov

      Thank for rising up the differences!
      1. Icon change is intentional. Unfortunately, some type of files are still waiting for the new icons.
      2. That is indeed a new regression. I’ve reopened
      3. I couldn’t find any related issue but may be the custom JDK have been updated but since the font became better it shouldn’t be a problem, should it :)?

      • Alexander Obuhovich

        3. Not an issue of course.

      • Alexander Obuhovich

        Turns out 2 might not be a bug after all. It uses custom icon when class/interface/trait name in a file matches filename of that file. I thought it works differently by using custom icon based on file content only and not comparing it with filename itself.

    • Jordan de Laune

      Haven’t downloaded it but I think I read on the webstorm blog that San Francisco is now the font used on macOS. Which IMO is a very nice font.

  • Joeri Thissen

    Why are you already moving beyond the EAP status? There are 166 issues still open that have 2016.3 listed as the fix version. One hundred sixty-six!

    When you say that something is going to be fixed in a specific release, I do expect it to actually be in the release. Right now, it just seems like you made a LOT of false promises.

    • Artem Khvastunov

      I’m sorry to see you disappointed. But to be clear the fix version is not a promise, it’s our estimation. Each release cycle we set up a backlog with issues we wish to have fixed during the current iteration. Some of them will definitely be fixed, some of them are not. As soon as we feel the product is ready to be delivered, we switch from EAP to RC. It’s a part of our routine, nothing more. Still it’s possible for some issues to be postponed more than once. If you know such issues and really need them to be fixed, please contact our support and provide them with issue IDs.

      • Joeri Thissen

        But if there are 166 issues that did not make it into the release despite your estimation, the estimation is not just a little bit off, it’s way off. To make it worse, in total there are only 209 issues marked with 2016.3 as the fix version. That means you only actually delivered about 20% of that estimation. That’s not a very good number.

        It’s mostly a communication issue. The only real update I get for a ticket is when it is assigned to someone else or suddenly gets assigned a fix version. No one replies with any actual information. So yes, when it gets 2016.3 as the fix version, I really do expect it will be included in the release.

        To be clear, I’m waiting for a fix to WI-31873, but I’m sure there are people waiting for other fixes as eagerly as I am for this one. And if about 80% of the issues that you mark as estimated for this release, don’t make it into the release, well, something is definitely not right.

        Obviously, there are many other things that did make it into the release, and I’m definitely not trying to say you’re not doing enough. However, better communication on what to expect and a more realistic estimation about the amount of issues you can fix in a release would prevent disappointments like this.

        • Artem Khvastunov

          Your numbers are not really correct. ATM we have about 190 issues ( already fixed and included in the release, about 360 issues ( were planned and some of them still will be fixed. But I’m not trying to say that there’s no communication issue. I agree that it’s not always clear from outside of the company how we make decisions what to fix and how you (as a client) can influence. We’re already discussing this problem internally and I hope will address it in the near future. Thank you for raising it up.

          Back to the issue you’ve mentioned. We (developers) don’t have strict rules how to choose the next issue to fix. However there’re certain metrics that make sense for us. One of them is the number of votes. The best thing how you can highlight the issue is to vote for it and ask you colleagues who encounter this problem to do the same. The more votes the issue has, the more likely it’ll be solved sooner (no promises here, too).

  • Иван Пшеницын

    I’m disappointed :(
    I saw on EAP the same problem.
    Asks me to login to bitbucket every several minutes:

  • Marcel Hernandez

    WRT the Docker remote interpreter*, will it be possible to select a _container_ name rather than an image name? Most of us already manage the whole container configuration (volumes, networks, etc.) with docker-compose.yml files, so it doesn’t make too much sense to select an image and configure an isolated container from a PHPStorm menu.


  • magnetik

    What are the improvments of “Improved support of PSR-0/PSR-4” ?

  • serdar_d


    thanks for each update for P.Storm BUT please revert back that windows code! Old one was so easy to navigate. This is just annoying..