PhpStorm 2016.3 Release Candidate 2 is available

We are glad to announce that PhpStorm 2016.3 RC 2 build 163.7743.39 is now available! If you want to learn all the details about the new features or to get yourself a copy to try right away, please visit our website.


This build takes on the latest improvements in IntelliJ Platform.

See the full list of bug-fixes and improvements list in the release notes.

For more information please look at the overview of all PhpStorm 2016.3 features and download the build from PhpStorm website. A patch update is already available from the previous EAP build (PhpStorm 2016.3 EAP 163.7743.20).

If you have any feedback to share with us, please do so by commenting to this blog post, or in the issue tracker, as the PhpStorm 2016.3 release is just around the corner!

Your JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Cool Feature, Early Access Program. Bookmark the permalink.
  • Ray Ban

    I’m need replace vmoptions after each phpstorm updating. Can you improve this, that file has not been replaced?

    p.s. sorry for my english.

    • Armstrong

      You should edit them via -> Help -> Edit Custom VM Options, Not in bin directory.

      • Ray Ban

        Thank you!

    • Maxim Kolmakov

      The answer by Armstrong below is absolutely correct. Please follow his advice.

  • Michael Taggart

    All I want is for PHPStorm to respect my capitalization when writing a for each loop! Please!

    • Maxim Kolmakov

      Would you like to have foreach loop in the following style: FOREACH($a AS $b) when you complete “foreach” keyword?
      I would like to suggest you to change Settings->Editor->Live Templates->PHP->fore template and use it in future by typing “fore” and pressing Tab.

      • Michael Taggart

        if I have this

        $Foo_Bars = Array(…);

        PhpStorm does this on a foreach

        foreach ($Foo_Bars as $foo_Bar) {}

        the plural to singular is nice, but I want that first letter capitalized. Like this:

        foreach ($Foo_Bars as $Foo_Bar) {}

        We have a coding convention where the first letter capitalized means you are dealing with an object or an array of objects. Every time I do a foreach I have to change the scalar after the “as” to have the right capitalization. A buddy of mine added a feature request but it was closed by JetBrains without ever being done.

        • Maxim Kolmakov

          If I’m not mistaken this is the request: It’s not closed yet and still has the state “Open” but we consider it to be a rare case. Please vote for it so we know how many people are actually interested in it.

  • Maria Flux

    Great job! Give it a try!