PhpStorm 2017.3.7 and PhpStorm 2018.1.7 are released

Posted on by Roman Pronskiy

We’ve already released PhpStorm 2018.3 but haven’t forgotten about those who still use earlier releases. Today we are releasing bug-fix updates for both PhpStorm 2017.3 and PhpStorm 2018.1. These updates bring important fixes to the platform.

Download the updates here or via our Toolbox App.

PhpStorm 2017.3.7 (build 173.4674.69):

PhpStorm 2018.1.7 (build 181.5540.39):

Make sure to get these bug-fix updates as they include a fix for the possible freezes (IDEA-194992).

For information on all changes included in the updates, please refer to the Release Notes.


Please do report any bugs and feature requests to our Issue Tracker.
Your feedback is also very welcome in the comments below and Twitter.

Your JetBrains PhpStorm Team
The Drive to Develop

Comments below can no longer be edited.

17 Responses to PhpStorm 2017.3.7 and PhpStorm 2018.1.7 are released

  1. Nagi Springfield says:

    December 18, 2018

    may you fix the bug that make phpstorm indexing forever?

    • Dmitry Tronin says:

      December 18, 2018

      There are no unresolved bugs related to indexing taking too much time currently. You might be experiencing an issue with misconfiguration or broken 3rd party plugin. Please contact us directly via Help > Contact Support.

      • Nagi Springfield says:

        December 19, 2018

        maybe because i used old version (ver 2017)
        the latest version work perfect, at least for now

        • phartsandwich says:

          December 28, 2018

          “At least for now”… lol, c’mon how about a positive attitude 🙂

          • Jes says:

            January 5, 2019

            I LOVE My IDE finally…. finally.

  2. Mellouli chrif says:

    December 21, 2018

    Please remove this warning :
    ||| Redundant closing tag .. Closing tag ‘?>’ is redundant for files containing only PHP code. |||
    Because i will never removing this tag XD, i like it XD

    • Dmitry Tronin says:

      December 24, 2018

      You can manually disable this inspection via Alt+Enter menu: https://uploads.disquscdn.com/images/8f756d516b567315c42cf87781fd4faf00ef55e5aedd3994daee82043d6a7a42.png

      • Mellouli chrif says:

        January 11, 2019

        thank you.

    • Fabian Picone says:

      January 11, 2019

      Closing tag ‘?>’ can cause errors. You should not like it from now on.

      • Mellouli chrif says:

        January 11, 2019

        how?

        • Fabian Picone says:

          January 11, 2019

          Its PHP Basic. The documentation says: “If a file contains only PHP code, it is preferable to omit the PHP closing tag at the end of the file. This prevents accidental whitespace or new lines being added after the PHP closing tag, which may cause unwanted effects because PHP will start output buffering when there is no intention from the programmer to send any output at that point in the script.” http://php.net/manual/en/language.basic-syntax.phptags.php

          • Mellouli chrif says:

            January 11, 2019

            thank you very much.

  3. Fabian Picone says:

    January 11, 2019

    Why the update does not happen in the software like before, instead forwarding me to this page for manual download? I dont like this.

    • Eugene Morozov says:

      January 14, 2019

      Please clarify what version were you on when the new version was released?

      • lelospapoul says:

        January 15, 2019

        Same happens to me, current version 2017.3.2 (build 173.4127.29)

        • Dmitry Tronin says:

          January 15, 2019

          Update from any version is available starting PhpStorm version 2018.3 only.
          If you’re on 2017.3.2 – you’ve missed .3.3, .3.4 and so forth. Please follow the instructions at https://blog.jetbrains.com/phpstorm/2017/09/taking-control-of-phpstorm-updates/ to install the updates one by one. Or else you can just download & unpack 2017.3.7 from the scratch (your settings should be left intact).

      • Fabian Picone says:

        January 15, 2019

        Already updated it manually, dont know which version exactly it was before. I think the version was a year old.

Subscribe

Subscribe for updates