PhpStorm 11 Early Access Program Started

We are glad to announce the start of the Early Access Program for PhpStorm 11. The fresh build 144.3010 is available for download and we are waiting for your feedback in the issue tracker.PhpStorm11EAP_splash_2@2x

This build includes a lot of new features, bug fixes and improvements for PHP, Web and on the IntelliJ Platform side. PhpStorm 11 release is currently planned for Spring 2016 (roadmap will be available soon).

Project level interpreters

Now you are able to configure interpreters not only at application, but also at project level. This might be useful when you have lots of projects, each having a distinct server used only there. Another case for project level interpreters it’s when you want to share your interpreter settings with teammates or put them under version control.

Project Interpreter

Support of XDebug for REST client

For those using REST client but missing debugger functionality, now we support XDebug. You can also trigger PHP debugger from the REST client.


Compact function support

PhpStorm now resolves variables from compact function string arguments (WI-2023), helping you navigate, find usages and refactor your code easily.


See the complete list in our issue tracker and read the full release notes for PhpStorm 11 EAP 144.3010.

WebStorm 12 EAP is available as well (read more in WebStorm blog), and from the Web side we are delivering:

  • Inline rename for TypeScript
  • Improvements in Angular 2 support
  • Smarter imports for TypeScript
  • Debugging JS async code

To read more about other improvements planned for the next release, please see the WebStorm blog post.

And finally, IntelliJ Platform brings many new goodies such as:

PhpStorm running on Java 8

The whole IntelliJ IDEA platform is migrating to Java 8. That means PhpStorm is now running on Java 8 and can only be launched now under a JDK for Java 8 or later. The change affects all the EAP builds (144.*) and further major releases in this upcoming spring.

Download PhpStorm 11 EAP build 144.3010 for your platform from project EAP page, and please report any bugs and feature request to our issue tracker.

The Drive to Develop!
-JetBrains PhpStorm Team

This entry was posted in Early Access Program and tagged . Bookmark the permalink.
  • Josh Taylor

    xdebug helper is super nice, before I was just using Chrome, then use ‘Copy to CURL’, then using that curl request.

    What month/quarter is spring 2016?

    • Alexey Gopachenko

      Early Q2

  • Ruud Kamphuis

    It won’t start on Mac OS. I have installed Java:

    $ java -version
    java version “1.8.0_66”
    Java(TM) SE Runtime Environment (build 1.8.0_66-b17)
    Java HotSpot(TM) 64-Bit Server VM (build 25.66-b17, mixed mode)

  • Morten Bergset

    Any improved support for Laravel?
    I really miss code completion in blade.php files…

    • Alexey Gopachenko

      Not really, but we still reviewing this iteration plans. Note that we won’t work on Blade templates. Please watch

      to get updates on this.

      • Evgeniy Nikonorov

        Maybe i miss something, but symfony and yii have native storm support, why laravel not?
        Support of Blades template was most-voted on tracker, but
        this opened more than year ago… and still no results.
        “Note that we won’t work on Blade templates” – what does it mean?

        • Alexey Gopachenko

          symfony and yii support are build by 3rd parties.

    • Josh Taylor

      Symfony support is provided by a plugin, why isn’t Laravel?

  • Shehi

    Older than Java 8? Do you mean younger than Java 8?

  • MrHaroldA

    Please fix some bugs first before you introduce more bugs.

    This annoys the living crap out of me every day for way too long now:

    • Maxim Kolmakov

      The issue you’ve mentioned is already fixed (at least partially). What exactly doesn’t work for you?

      • MrHaroldA

        That issue has been duplicated numerous times, and has a vast amount of votes to get fixed. I guess this is the latest open bug:

      • MrHaroldA

        This remark captures it nicely, although it’s not very nice to hear:

        “This has been an open issue for over 2 YEARS now. Two years of me having to open up a separate terminal app when I have one right there, staring at me. Two years of accidentally hitting ctrl+left only to realize that if I want to prepend ‘git add .;’ to my current commit, I have to hold down the left arrow key and contemplate on my frustration that there’s been yet another release without a fix.”

        • sakis

          The home and end buttons work btw. As does escape

          • MrHaroldA

            Ctrl left/right, alt backspace, ctrl k, etc … without them, editing a line is really painfully slow.

          • sakis

            The new EAP has finally fixed this. ( But they failed to fix it for windows – should be fixed for windows soon enough as well)

    • Alexey Gopachenko

      This issue is being taken care of by other (non-php-IDEs) teams. We in turn doing our best to improve PHP related functionality.

      • MrHaroldA

        This issue has been open (an annoying) for over two years now … that’s not what I call “being taken care off”.

  • plog

    I really hope that PHPSpec will be supported in PHPStorm 11!

  • Alex

    You guys make by far the best php editor on the planet, it always annoys me to read the comments here because they are so self centered. For the small amount of money you charge, your software makes my job so much easier and more productive. Keep up the good work!!!

  • Aurimas

    Guys again I do not see anything worked on PHP7 support… I am annoyed that I cannot use anonymous classes because IDE threats them as array

  • Morgan Touverey Quilling

    YEAH the font is finally anti-aliased on Linux !! My eyes are cicatrizing.

    • Michał Opiełka

      I use OpenJDK with tuxJDK to fix this problem in version 9.

      Then I edit file bin/ to update path to Java folder there. I add something like:


      about line 108, right before “if [ -z “$JDK” ]; then”

      • Jordan

        Thank you for sharing that!

  • Ganey

    I’ve just updated and the EAP expiry hasn’t updated, when you’ve previously stated this resets with major versions.

    • Maxim Kolmakov

      You should have 30 day free EAP license for this build. So when you open “About” dialog it should be something like: “Expiration date: February 13 2016”. Is that something different for you?

      • Ganey

        It does have February 13th 2016, but I that’s the same date I had from installing 10 last week.
        I installed this build yesterday, shouldn’t it set the EAP to 17th Feb (30 days)?

        • Maxim Kolmakov

          No, since each build provides 30 day license from the date of the build and not an installation time. This allows us to make sure that all EAP users use more or less the latest available EAP build.

          • Ganey

            Ah I see! Thanks for clarifying that :)

  • Jose Hernandez

    are the roadmap features available yet?

    • Maxim Kolmakov

      Unfortunately not yet, we’re still busy finalizing it.