#PHPStorm

Ortwin Pinkejust downgrading <a href="https://programming.dev/c/jetbrains" class="u-url mention" rel="nofollow noopener" target="_blank">@jetbrains</a> <a href="https://mastodon.online/tags/PHPStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHPStorm</a> from 2025.2.1 to 2025.1.4.1 because newest version always freezes while checking files (maybe) so you only can kill the process. 🙁

PhpStorm BlogThe Laravel Idea Plugin is Now Free for PhpStorm Users <a href="https://techhub.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://techhub.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://techhub.social/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#News</a> <a href="https://techhub.social/tags/Laravel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laravel</a> <a href="https://techhub.social/tags/Laravelidea" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laravelidea</a><a href="https://blog.jetbrains.com/phpstorm/2025/07/laravel-idea-is-now-free/" rel="nofollow noopener" translate="no" target="_blank">https://blog.jetbrains.com/phpstorm/2025/07/laravel-idea-is-now-free/</a>

Florian WeberLove the most recent <a href="https://chaos.social/tags/PHPStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHPStorm</a> splash screen! 🥳 <a href="https://furry.engineer/@ret/114670342662638779" rel="nofollow noopener" translate="no" target="_blank">https://furry.engineer/@ret/114670342662638779</a>

MarcHere’s a `phpstorm <dir>` bash function that works like `code <dir>`, i.e. opens the given directory as a project in <a href="https://mastodon.social/tags/phpstorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#phpstorm</a>.``` phpstorm() { local dir=$1 (nohup PhpStorm nosplash "${dir}" >/dev/null 2>&1 &) >/dev/null } ```I couldn’t find this anywhere, and it seems to work for me.You probably need to set Settings→Tools→Generate shell scripts in the JetBrains Toolbox App to have the `PhpStorm` command available.My usual flow is:``` cd /some/project/dir phpstorm . ```<a href="https://mastodon.social/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a>

Matthias Andrasch<a href="https://social.tchncs.de/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> is a cost factor in web development - and I expect increased prices, not cheaper solutions in future. Has anyone experience with local models (without cloud pricing), which CPU is required, etc.? E.g. for <a href="https://social.tchncs.de/tags/jetbrains" class="mention hashtag" rel="nofollow noopener" target="_blank">#jetbrains</a> <a href="https://social.tchncs.de/tags/phpstorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#phpstorm</a> AI offline mode or other tools? 🤔 (And is there any chance that they might be a bit more sustainable in regards to energy usage? 🌱) <a href="https://www.jetbrains.com/help/ai-assistant/switching-to-offline-mode.html" rel="nofollow noopener" translate="no" target="_blank">https://www.jetbrains.com/help/ai-assistant/switching-to-offline-mode.html</a> <a href="https://social.tchncs.de/tags/KI" class="mention hashtag" rel="nofollow noopener" target="_blank">#KI</a>

Ben RamseyI haven’t had many problems with <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a>’s <a href="https://phpc.social/tags/Xdebug" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xdebug</a> integration in a long time. Most of the time, it Just Works, but today, it decided it doesn’t like me, and so now, my afternoon has been spent trying to get it to work again.This is the error I see in the step debugging console. The only thing I know has changed is PhpStorm (it upgraded).``` Cannot find file '/path/to/ramsey/uuid/Standard input code' locally. ```<a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a>

Ben RamseySince <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> uses <a href="https://phpc.social/@3v4l" class="u-url mention" rel="nofollow noopener" target="_blank">@3v4l</a> for its “scratch files” feature, I hope they’re donating much more than € 250 a month (€ 3,000/year). They’re getting a lot of value out of 3v4l.<a href="https://www.jetbrains.com/help/phpstorm/scratches.html#run-scratch-files" rel="nofollow noopener" translate="no" target="_blank">https://www.jetbrains.com/help/phpstorm/scratches.html#run-scratch-files</a>

🇵🇸 Álvaro GonzálezThe commit message generated by AI Assistant to fix a typo in a method name is literally: "Updated all occurrences of X to Y for consistency. Simplify code by unifying Z logic into a single method." <a href="https://mastodon.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://mastodon.social/tags/AI" class="mention hashtag" rel="nofollow noopener" target="_blank">#AI</a> <a href="https://mastodon.social/tags/LLM" class="mention hashtag" rel="nofollow noopener" target="_blank">#LLM</a> <a href="https://mastodon.social/tags/GenAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GenAI</a>

PhpStorm BlogHow PhpStorm Helps Maintain PHP Open-Source Projects: Interviews and Real-World Examples <a href="https://techhub.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://techhub.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://techhub.social/tags/Community" class="mention hashtag" rel="nofollow noopener" target="_blank">#Community</a> <a href="https://techhub.social/tags/Communitysupport" class="mention hashtag" rel="nofollow noopener" target="_blank">#Communitysupport</a> <a href="https://techhub.social/tags/Opensourceprogram" class="mention hashtag" rel="nofollow noopener" target="_blank">#Opensourceprogram</a> <a href="https://techhub.social/tags/Ossprojects" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ossprojects</a><a href="https://blog.jetbrains.com/blog/2025/06/10/how-phpstorm-helps-maintain-php-open-source-projects-interviews-and-real-world-examples/" rel="nofollow noopener" translate="no" target="_blank">https://blog.jetbrains.com/blog/2025/06/10/how-phpstorm-helps-maintain-php-open-source-projects-interviews-and-real-world-examples/</a>

Marcus Jaschen🎉 I saw this startup image when launching PHPStorm this morning. PHP turned 30 over the weekend!I've been part of those 30 years for 28 of them, and the last 10 years (since PHP 7) have been the best. I'm constantly amazed at how much the language and the whole ecosystem have evolved (looking at you, Composer).<a href="https://skylightaccess.de/tags/30yearsofphp" class="mention hashtag" rel="nofollow noopener" target="_blank">#30YearsOfPHP</a> <a href="https://skylightaccess.de/tags/phpstorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHPStorm</a> <a href="https://skylightaccess.de/tags/composer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Composer</a> <a href="https://skylightaccess.de/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a>

PhpStorm BlogJoin JetBrains PHPverse to Celebrate 30 Years of PHP <a href="https://techhub.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://techhub.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://techhub.social/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#News</a> <a href="https://techhub.social/tags/Php30" class="mention hashtag" rel="nofollow noopener" target="_blank">#Php30</a> <a href="https://techhub.social/tags/Phpverse" class="mention hashtag" rel="nofollow noopener" target="_blank">#Phpverse</a><a href="https://blog.jetbrains.com/phpstorm/2025/05/join-jetbrains-phpverse-to-celebrate-30-years-of-php/" rel="nofollow noopener" translate="no" target="_blank">https://blog.jetbrains.com/phpstorm/2025/05/join-jetbrains-phpverse-to-celebrate-30-years-of-php/</a>

Ben RamseyI've not been this frustrated with a new version of PhpStorm in a long time. There are so many tiny, irksome issues, and they keep piling up. I've come to expect some rough patches each year when they release a new major version, but this time, it's really impacting my productivity and making me think about looking at alternatives. I can't be the only one experiencing these issues, and it's too cumbersome to stop what I'm doing to file support requests or bugs.<a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://phpc.social/tags/JetBrains" class="mention hashtag" rel="nofollow noopener" target="_blank">#JetBrains</a>

Ben RamseyThis is merely annoying for creating new files, but when I move files in the tests/ directory, it completely mangles the namespaces. I think this is new in 2025.1.0.1, but I’m curious if others are seeing it before I spend time opening a ticket. Maybe I’m just missing some new setting.<a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a>

Ben Ramsey<a href="https://mastodon.social/@digitalcraftsman" class="u-url mention" rel="nofollow noopener" target="_blank">@digitalcraftsman</a> I found the setting, and that didn’t fix things. Whenever I create a new file in the tests/ directory, it starts out in the global namespace, and I have to manually change it. If I create a file in tests/Foo/, the namespace is simply Foo. It’s not respecting my PSR-4 prefix set in autoload-dev.<a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a>

Ben RamseyPhpStorm appears to have forgotten how to deal with PSR-4 namespaces in autoload-dev. Or maybe I'm losing my mind.<a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a>

Ben RamseyI think the latest version of PhpStorm (I have 2025.1.0.1) doesn't properly read `autoload-dev` from `composer.json`. It thinks all my test namespaces are wrong.Is anyone else seeing this?<a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a>

Ben RamseyIt turns out I had my PHP CodeSniffer settings set to "By default project interpreter," but I didn't have `phpcs` configured with the default project interpreter?I'm not sure how the UI was showing me code style warnings, based on my `phpcs.xml` file settings, but it was.When I added a `phpcs` configuration for "By default project interpreter," things began working as expected.<a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://phpc.social/tags/JetBrains" class="mention hashtag" rel="nofollow noopener" target="_blank">#JetBrains</a>

Ben RamseyIs it just me, or does PhpStorm 2025.1 have a bug where it's not running phpcbf when you select "PHP Code Beautifier and Fixer: fix the whole file?"It's getting very annoying, and I have checked and re-checked my settings a million times.<a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a> <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> <a href="https://phpc.social/tags/JetBrains" class="mention hashtag" rel="nofollow noopener" target="_blank">#JetBrains</a>

Ben RamseyThis is pretty funny:I finally got annoyed enough with an issue in <a href="https://phpc.social/tags/PhpStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PhpStorm</a> that I decided to create a ticket for it in their bug tracker.It turns out there's already a ticket for it, and it links to a GitHub issue that references a Mastodon post that I made over two years ago.🤣🤣🤣Issue is here: <a href="https://youtrack.jetbrains.com/issue/WI-78517/PHPUnit-annotation-inspection-suggests-CodeCoverageIgnore" rel="nofollow noopener" translate="no" target="_blank">https://youtrack.jetbrains.com/issue/WI-78517/PHPUnit-annotation-inspection-suggests-CodeCoverageIgnore</a><a href="https://phpc.social/tags/PHP" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHP</a>

Pedro FonsecaThank you <a href="https://masto.pt/tags/jetbrains" class="mention hashtag" rel="nofollow noopener" target="_blank">#jetbrains</a> for the <a href="https://masto.pt/tags/PHPStorm" class="mention hashtag" rel="nofollow noopener" target="_blank">#PHPStorm</a> product. My renewal is done for another year ;)

Recent searches

Search options

Administered by:

Server stats: