Great! How about letting developers know before ToolBox automatically updates with plugin incompatibilities and then prevents rollback to previous version! You’ve taken down a whole international development team at Easter during an emergency.
Although you put a post up on 01 March this type of critical version break should have been emailed to long-standing loyal customers who’ve recommended JetBrains 100s of times.
You forced my review of your products as compared to competitors.
We expect that you can easily use the previous stable 2024.3 version without a disruption. Please do not forget that we never promised forward compatibility for it and it was your choice to depend on the plugin.
Also Toolbox always lets you install previous version side by side and keeps all configs as before for them.
You never promised forward compatibility with 2025.1… In fact you did nothing at all except allow ToolBox to give an update PhpStorm flag. Incompetent, and inexcusable.
A bit of helpful advice from one of the very rare grandfathers of the digital age. Give the links as to how to fix this issue, including alternative plugins, provide the plugin flags under settings->plugins, and show how to uninstall 2025.1 as being a product that does not work without fixes until JetBrains provides what it’s paying customers should do.
Mike, your post lacks details on what happened and how we can help you. You do not even tell us which plugin you have.
I can’t agree that there is any kind of emergency when we are talking about upgrading to a new major version.
Accepted. ToolBox with all apps; ToolBox PhpStorm update flag accepted resulting in v2025.1 being installed. Boom! A plugin incompatibility notice, and PhpStorm not starting any projects from the project list.
Whether you agree or not is irrelevent. Basic marketing and support requires not putting barriers between provider and customer. My tenth year of recommending JetBrains over VScode and others, and insisting on my developer teams using it as a condition of getting gigs but hey, if you want to debate to prove how right you are go ahead.
Now provide the fixes suggested above. I’ve just advised two teams to switch to VScode for now. We cannot waste time.
PhpStorm not starting any projects from the project list.
Could you please comment how it is related to JavaFX dependency? I can’t see how so far.
And we still don’t know the plugin you have problem with.
Nor can I. Just a message about that plugin incompatibility and PhpStorm no longer loading projects. Same for me in Scotland and developers in Thika, Nairobi and elsewhere. Different client machines and OS.
Could you may be post a screenshot of what you observed?
Not now. We’re in the middle of a development emergency for an intelligence site so have had to switch off machines, clear caches, and install previous PhpStorm version. That now hides the issue. We’re using VScode to avoid further delay.
Most likely your request is not really relevant to the topic. You should have better contact our support and they would help
Most likely very important feedback for other paying customers with same problem who need link to full fast resolution. JetBrains made the problem and knew: now help customers resolve it at the point of issue: here!
In ToolBox, this does not go away. Always “loading”, no rollback apparently available…
Sorry to say, but it is definitely not related to the topic above
Oh dear. Would you like to try this from a help-the-paying-customer then?
Given that a) several PhpStorm IDEs on different operating systems stopped working the instant a JetBrains-advised ToolBox update button was clicked for v2025.1, b) there is no apparent rollback to uninstall v2025.1, and c) (according to you) the issue “is definitely not related to the topic above”, are you willing to be helpful and signpost to what the problem is in 2025.1, why the removal of JavaFX runtime admitted as having affected so many plugins did not affect anything in PhpStorm, or refer to a link that states what else JetBrains have done in 2025.1 to cause substantial issues with PhpStorm?
Do feel free to be technical. I developed my first PC and operating system before Woz.
Please contact our support. This forum is for plugin developers, not a support service
JavaFX is not part of our IDEs for 5 years already, only small number of plugins depending on a dedicated plugin required it. Moreover, even with this plugin unavailable for fresh install it still works in the current installations including 2025.1 and does not block upgrade and IDE start
