PhpStorm 2018.2.2 is released

Posted on by Roman Pronskiy

PhpStorm 2018.2.2 build 182.4129.45 is now available! You can download it here or in JetBrains Toolbox App. If you have installed the previous PhpStorm 2018.2 or PhpStorm 2018.2.2 EAP build (182.4129.18), please invoke the Check for updates action to receive the latest update.

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

PHPCS and PHPMD usability improvements

PhpStorm continues to simplify usage of PHP_CodeSniffer and Mess Detector. Now, if you have phpcs.xml or phpmd.xml config files in the root of your project, they will be automatically detected and grasped by the PhpStorm.

phpcs.xml and phpmd.xml auto-detected

The IDE now also detects custom rules/rulesets for PHPMD specified in composer.json.

Platform updates:

  • The database tools now support ClickHouse out of the box
  • Fixed a couple of performance issues related to VCS (file scanning)

Notable bug fixes and features worth mentioning:

  • PHPUnit: rerun failed tests now works for “defined in configuration file” run configuration (WI-43181)
  • Debugging maximum simultaneous connection configuration setting is now set to 3 by default (WI-35124)
  • Fixed completion for interfaces (WI-43157)
  • Fixed “Deployed file is on server removed” stuck since update 2018.2 (WI-42992)

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

Download PhpStorm 2018.2.2 build 182.4129.45 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

Comments below can no longer be edited.

17 Responses to PhpStorm 2018.2.2 is released

  1. Александр Фролов says:

    August 22, 2018

    > The database tools now support ClickHouse out of the box

    and you still not implemented cassandra support… FeelsBadMan

      • Александр Фролов says:

        August 22, 2018

        already voted, looong ago. this issue has more votes, than all clickhouse-related issues combined, but still, clickhouse goes first.

      • Maarten Wolzak says:

        August 24, 2018

        voting is useless: request for clickhouse support had only 15 votes while request for Cassandra has more then 10 times as much votes…

        • Roman Pronskiy says:

          August 24, 2018

          Thanks for bringing this up. When taking features into development, we consider several factors including user votes, our internal research results, complexity vs. value ratio, and some others. I.e., having more votes does not guarantee that the feature will be implemented faster than the other one, but it affects the priority a lot!

  2. Nguyen Van Anh says:

    August 23, 2018

    I tried place phpcs.xml in project source root but seem it not work. I set coding standard in

    Inspection is: PSR2
    phpcs.xml is: WordPress

    But PHPStorm still report PSR2. Any step I miss?

    • Kristaps Fabiāns Geikins says:

      August 24, 2018

      Yeah, doesn’t work for me either, I still need to enable it as a custom ruleset manually for it to work.

  3. edineibauer says:

    August 24, 2018

    I just download the new version and I get a file in a folder with this extension “___jb_old___”, and I cant remove it, the original file is not saving correctly because this file.

    • Eugene Morozov says:

      August 27, 2018

      What OS do you use? Is it not possible to remove that folder even when PhpStorm is closed?
      Please try to do that with elevated permissions (sudo or Run as Administrator).

      • edineibauer says:

        August 28, 2018

        I remove the program and all settings, install again. Work!

  4. Ralitsa Radeva says:

    August 31, 2018

    I have some trouble after upgrading to 2018.2.2 build 182.4129.45.
    I’m working mostly on Symfony projects and after upgrading for some reason Symfony disappeared from Languages & Frameworks and thus the Symfony plugin is not working.
    Also in Languages & Plugins the PHP version is frozen to 5.5, which is not the one I use.

    See attached for more details.

    Can you give me any advise how to get back the higher PHP version and the Symfony plugin?

    • Ralitsa Radeva says:

      August 31, 2018

      For reference, this is how things look like in 2017.3:

    • Eugene Morozov says:

      August 31, 2018

      The language level is now bound to the PHP version requirement in composer.json. Please consider changing it to something appropriate, or, you can disable settings sync at Languages & Frameworks | PHP | Composer.
      A thread on why your composer.json is wrong if the language level of 5.5 does not fit your project:

      Is the Symfony plugin still there in Settings | Plugins?

    • Ralitsa Radeva says:

      September 1, 2018

      Thanks for your response. I didn’t know that it’s now bound to the version in Composer, and mine was outdated.
      Anyway, the Symfony plugin was still there, enabled, but I couldn’t bind it to any projects, because Symfony was missing from Languages & Frameworks. Is there something else moved, that I missed?

    • Ralitsa Radeva says:

      September 1, 2018

      After several re-installations and restart it all up and running again. Thanks for your advices!

  5. Chris Mok says:

    September 24, 2018



Subscribe for updates