-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clicking on file name opens Windows Store #21
Comments
Same here (Win 10, PHPStorm 2020.2.4,Ray version: 1.0.2.0) |
Same here (Win 10 Pro 20H2, PhpStorm 2020.3.1, Ray v1.0.3). |
I'm looking into this issue, I hope to be able to release a version with this fixed today. |
Fixed it using this: https://github.com/aik099/PhpStormProtocol I followed the instructions for Windows, and I had to change the path in run_editor.js to reflect my real path. Also, note that PhpStorm installs in a new folder every time so this script must be updated too :( |
I'll try my best to find a better solution for this! Do you get this problem only with PhpStorm, or also if you select other editors (that you have installed)? |
It seems like this is a known error, and we'll probably not be able to fix it on our side. See https://laracasts.com/discuss/channels/general-discussion/cant-get-ignition-to-open-file-in-phpstorm |
I have the same problem on Windows 10, Phpstorm 2020.3.1. I tried the protocol handler option posted by @pokmot with no luck. Got shell error running wscript. I found that an IntelliJ Platform supports a Rest API to open a file. Could this be a potential solution and configuration option for the Ray app? Not sure if the api is supported. White flag up. Retreating. |
When I click on a source file file path in Ray, it wants to look for an app in Microsoft Store.
What do I need to do to register the protocol so it opens the correct file in PhpStorm?
Versions
Ray version: 1.0.2.0
spatie/laravel-ray package version (if applicable): 1.1.0
Laravel version (if applicable): 8
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: