PhpStorm 2018.2 is now released!

PhpStorm 2018.2, the second major update for PhpStorm in 2018, is now available! You can download it here or via JetBrains Toolbox App.

Our website has all the details of this release, and here’s a roundup of the notable highlights.

800x400_blog

PHP Language

  • Custom postfix completion templates
  • FQCN completion
  • Structural Search and Replace for PHP
  • Improved SQL Injections
  • The new presentation for Quick Documentation
  • Jumping outside closing bracket/quote with Tab
  • New Inspections and Quick Fixes

PHP Refactorings

  • Move Instance Method Refactoring
  • New Add @method tag quick fix for Undefined method
  • Add method quick fix now inserts parameter type hints

PHP Tools

  • Simple CodeSniffer/MessDetector setup
  • PHPUnit composite configuration

HTTP Client

  • Support for environment variables in the request body
  • Support for POST request body formatting

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

PhpStorm 2018.2 also brings major improvements in its support for web technologies, such as new JavaScript intentions, completion for events in Vue.js, Typescript 2.9 and 3.0 support, the new Code Coverage feature that helps to find unused code, extract and convert React component refactoring, new integrations with Angular CLI, global file
watchers, rerunning failed tests, and much more.

IntelliJ Platform has provided this release with lots of new features as well as bug-fixes. Specifically, updated UI with brand new icons, dark title bars on macOS, and TouchBar support for MacBooks, as well as improved VCS support with new ways to resolve merge conflicts, enhancements in VCS Log, support for multiple GitHub accounts, and even more.

Database tools have been improved with the new SQL formatter, source code migration, query plan diagram, custom data sources and more.

For more details please see What’s New in PhpStorm 2018.2 and download a free 30-day PhpStorm trial for your operating system.

PhpStorm 2018.2 is available as a free update for everyone who has an active subscription for PhpStorm or All Products!

JetBrains PhpStorm Team
The Drive to Develop

This entry was posted in Newsletter, Release Announcements and tagged . Bookmark the permalink.
  • http://www.zemistr.eu Zemistr

    For more details please see What’s New in PhpStorm 2018.1 and download a free 30-day PhpStorm trial for your operating system.

    You sure you mean:

    For more details please see What’s New in PhpStorm 2018.*2* and download a free 30-day PhpStorm trial for your operating system.

    😉 😀

    • Maxim Kolmakov

      Sure, fixed! Thank you for noticing and reporting!

      • http://www.zemistr.eu Zemistr

        Copy, paste… Right? 😀

        • Maxim Kolmakov

          You bet :)

  • Vladislav Shumkin

    Where is my snap package update? :)

  • Oleksandr Kurakin

    Just have infinitive “Synchronizing files…” indicator and code is not highlighted properly. I tried invalidating cache, disabling plugins… nothing helps

  • dense_alpha

    The dark window headers is damn cool

  • Михаил Красильников

    This is already becoming a tradition: in addition to all the cool things to add a couple of usability regressions.

    New:
    https://youtrack.jetbrains.com/issue/IDEA-192025

    Some old regressions:
    https://youtrack.jetbrains.com/issue/PY-9627 (5 years)

    https://youtrack.jetbrains.com/issue/IDEA-84694 (6 years)

    https://youtrack.jetbrains.com/issue/IDEA-162214 (2 years)
    https://youtrack.jetbrains.com/issue/IDEA-161208 (2 years)

    • Dmitry Tronin

      Thanks for bringing this up. New one is hardly a regression – that’s a simple cosmetic change, which was positively received by users (but not all, yeah).
      Next one was just fixed and planned for a next major update. Others are indeed little bit on halt: there are no updates since 2016 & May 2017. Probably it’s time to leave few comments checking for any updates/estimates.

  • Jason Gu

    PhpStorm 2018.2 snap still isn’t available in the Ubuntu Software store; please update the snap to the latest version.

    • Maxim Kolmakov

      That is strange. Maybe some local issue with cache? The snap package for 2018.2 is available since Friday: https://snapcraft.io/phpstorm

  • Luck

    “As of PHP 5.2.0, the JSON extension is bundled and compiled into PHP by
    default.” but PHPStrom still warns “ex-json is missing in composer.json” which is wrong.

  • Misha van Tol

    The TouchBar config seems to be missing? It was in the keymap section in the EAP.

  • Aleksey Vasilenko

    After update from eap it just wouldn’t start on mac os. After that i download a installer, but problem is still here…

    • Aleksey Vasilenko

      It starts! After about 5 mins after i launch app

      • Dmitry Tronin

        Please check your etc/hosts file: probably there’s an aux record for “localhost”

  • Aimal Sami Amiri

    The best like always before

  • Andreas Otterstein

    Problem with the 2018.2 version? “Loading modules” at startup was very slow, now a blank window.. what is wrong? https://uploads.disquscdn.com/images/adab3dd4b98298eb3c248cb55dcc282d91dc6626e0465bcd263cf6426ad4808e.png

    • Eugene Morozov

      No similar reports so far.
      Please move the .idea folder out of the new-client-2 project, start PhpStorm 2018.2 and check if it starts OK this time.
      If it doesn’t, please rename the %USERPROFILE%.PhpStorm2018.2 folder, start 2018.2 once again not importing settings and check again.

  • Tony Dorchak

    2018.2 seems very buggy on Mac OS. PHPStorm is constantly indexing and shelving and committing changes locks up my computer until PHPStorm eventually just crashes. The interface enhancements look nice but not worth the issues that it introduces. I hope JetBrains has an incremental release soon.

    • Eugene Morozov

      Those enhancements probably have no relation to the issue you are seeing.
      We need to take a look at the logs to get down to it. Please send us the logs bundle (Help | Compress Logs…) within a support ticket:
      https://intellij-support.jetbrains.com/hc/en-us

    • https://egor.sh Egor Kokorin

      I’m using new phpstorm at the latest mac os (high sierra). Everything works well. But some time ago i faced with same indexing problem because of buggy lua plugin (emmy lua or something like that). Check your plugins. Try to toggle them off.

  • Kenji Olivier

    2018.2 is very buggy to me (Windows 10).
    – Settings won’t open
    – Configured IDE colours are messed up
    Any fixes available?

    • Dmitry Tronin

      I would suggest installing 2018.2 again & then contacting our support team to inspect those issues closely.

  • https://hackercombat.com/fix-malware-from-your-website-free William Harvey

    Looking to update phpstorm 2018.2..!

    • Dmitry Tronin

      Should be available soon!

  • AlexeyGfi

    In debugging via SSH-tonnel with xDebug, PHPStorm not highlight catch like before.
    Program Icon of the project which catch xDebug signal on windows task bar not blinking like before. Just nothing happend. It is unuseful case.

    • Vladimir Luchansky

      Nothing changed on that matter. Was PhpStorm added into firewall exceptions after the update? Are you able to connect to PhpStorm’s port through the tunnel?

  • Nina Cording

    Have to go back to previous version as this version is quite buggy. (2018.2, Windows 10)
    When editing a certain css file (not other css files), it shows me the “before” state in the editor so it looks like the changes were never made and have been lost.
    Looking at the file with another editor reveals, that the changes have indeed been made, but for what reason whatsoever, the PHPStorm editor reverts to the previous state of the document after hitting save.

    Also tried clearing the system cache and whatnot – to no avail. Somehow PHPStorm just doesn’t like that specific CSS file very much.

    This is an absolute showstopper, and I had to use sublime text again and a separate FTP client and GIT client to get things done in time.

    • Dmitry Tronin

      The issue went away after we’ve started to investigate it in details. The cause was a state of a file watcher checkbox that wasn’t saved between PhpStorm restarts. Unfortunately we weren’t able to track down the very root cause of it.