PhpStorm 8.0.2 RC1 139.173

PhpStorm 8.0.2 RC1 139.173 is available for download.

This update features significant performance improvements (including massive speed-up for large files with multiple injected fragments), and many other bug fixes (see full list in our issue tracker).

Other changes from IntelliJ platform and web are also included, see complete release notes. Web-related features can be also explored in WebStorm 9 release announcement, as all these features and improvements are available in this PhpStorm build either out-of-the-box or with free plugins in the repository.

Download PhpStorm 8.0.2 RC1 build 139.173 for your platform from project EAP page and please report any bugs and feature request to our Issue Tracker. Patch update is not available this time due to technical issues, sorry for inconvenience.

Develop with pleasure!
-JetBrains PhpStorm Team

This entry was posted in Early Access Program and tagged , , , , . Bookmark the permalink.
  • Henry Garcia

    wow no blade formatting fix

    • Jeff

      Why are you so ungrateful? You’re using an EAP build, which you’re doing so by choice.

      I love PHP Storm!

      • Jeroen

        Considering “Blade template engine” is the first version 8 feature listed on http://www.jetbrains.com/phpstorm/, you would have expected them to have fixed this by now. It’s extremely frustrating if you have to do a lot of blade templating and the editor keeps pasting stuff with wrong indentation etc. Would not have been a problem if a reformat would fix that, but as of today that’s still doing nothing at all.

      • Gary T.

        I was under the impression that I paid $ for PHPStorm, so I’m confused by the “ungrateful” remark. Also, since the EAP release should foreshadow stable release improvements, bug fixes, etc., I think it’s OK to be disappointed that a much requested fix for a very annoying bug/oversight still hasn’t been addressed.

      • Henry Garcia

        Please don’t get me wrong I love PHPStorm and I use it everyday and recommend it to others. But it is frustrating that Blade is now supported but you have to disable it to have indentation support.

        Despite this issue I will continue to use the product and I meant no disrespect to the PHPStorm Community and the developers.

        Also as of today we have an update – see the issue tracker https://youtrack.jetbrains.com/issue/WI-24357

    • Josh

      Write a plugin that fixes it?

    • lol768

      Looks like some work has been done on this but it won’t be ready for the 8.02 release. Basic formatting will be available in the next EAP. See this comment for more info.

  • innocenat

    Does RC release normally has patch to real release?

    • Maxim Kolmakov

      Usually it doesn’t, we usually provide patches between EAP->EAP (unfortunately, we didn’t for this update) and Stable->Stable and RC type is EAP.

  • http://jenko.me Ian Jenkins

    Appears to be a problem with the behat plugin with this build.
    Disable the behat plugin to get your project folders back!

  • Chris

    This won’t install without removing 8.0.2 first. Shouldn’t this EAP install to /JetBrains/PhpStorm 139.173 and not /JetBrains/PhpStorm 8.0.2? I thought EAPs installed to a build number folder as to not interfere with stable releases?

    • Andriy Bazanov

      Latest stable release is 8.0.1 an not 8.0.2. Considering that — it does not interfere with anything.

      • Chris

        True. The initial point being this installation is not smooth. I’ve been using EAPs for about a year now, and this is the first one that had a conflict when having 139.105 installed.

  • Hélio

    I think that 50% of the world population wants format blade files. 25% of the world population voted is this issue at the bug tracker, it is the #1 in votes… but looks like this problem never existed…

    I’m really thankful by using PhpStorm, especially the EAP, but, I’m being a guinea pig for an experimental product. So I think it is a game in which both parties gain …

  • Etki

    Hi.
    PHPStorm tells me that my license will expire at october 30th even after i’ve updated both on my notebook and virtual machine. Do i understand correctly that from now on EAP license isn’t renewed with every build and acts like a trial license?

    • Maxim Kolmakov

      EAP builds for minor/maintenance releases never contain new license every build, they contain the same evaluation license as the major release.

      Only EAP builds for major release contain new 30 day license for every build.

  • Jeff

    When upgrading to this EAP I was asked to uninstall my previous EAP. Now I just opened up PhpStorm but got a warning saying that I only have 5 days left of evaluation. Do I need to do something special for this release?

    • Maxim Kolmakov

      EAP builds for minor/maintenance releases never contain new license every build, they contain the same evaluation license as the major release.

      Only EAP builds for major release contain new 30 day license for every build.

      • Jeff

        Maybe I’m just confused about the EAP terms, but that’s definitely not my experience from the past year or so. I’ve never seen this message before. Also, here’s a few comments from PhpStorm devs from earlier EAP releases:

        EAP builds have their own license which cannot be replaced. Every build has new 30-days license. It’s done so that you do not stay on old EAP build forever (as main purpose of EAP builds is gathering feedback on new features/fixes before it goes public/stable release).

        And here’s another:

        “Mikhail, so you are saying that EAP builds do not require paid licenses as long as you update the release to the next EAP build before the 30 day license expires?”

        “Yes, exactly. We try to make EAP versions as affordable as possible to gather feedback.”

        Amy I missing something?

        P.S. Great product. I’m not complaining or anything, just wondering why this didn’t happen on any other EAP Builds.

        Thanks!

        • Maxim Kolmakov

          Jeff, we haven’t changed any policy regarding EAPs.
          Probably you always used EAP for major versions and as a result you always got a 30-day license for each build. All your citations are still valid for major version EAPs.

          For example, when we will publish PhpStorm 9 EAP you will get a 30 day free license for each new build as always.

          On the other hand that was never the case for EAP of minor updates because basically these EAP are very close to released versions in terms of stability/functionality.

          • Jeff

            Ahh, I see the difference. Thanks for the clarification. Is there a time frame for the PhpStorm 9 EAP yet?

          • Maxim Kolmakov

            It’s going to be in 2015 Q1.

          • Mikhail.Vink

            It’s going to be in 2015 Q1.

      • Jeff

        Not sure why my comment was deleted. Is this a change in your EAP policy?

        • Maxim Kolmakov

          Sorry about delay, we don’t delete any comments (except spam) but we need some time to look through them and approve them for public.

  • http://ClickTeck.com Shairyar Baig

    Glad to hear about

    , as this is my only concern with PHPStorm, it responds really slow on large files.

  • http://ClickTeck.com Shairyar Baig

    Glad to hear about

    “performance improvements (including massive speed-up for large files with multiple injected fragments) ”

    as this is my only concern with PHPStorm, it responds really slow on large files.

  • E.T.Cook

    Will you guys be adding support for non-standard WP structures, like WP Skeleton or Bedrock? http://roots.io/wordpress-stack/