![]() Thanks Andriy - you've helped clarify a couple of things. But yes - Xdebug Wizard now covers PHP 7.x only - it's just to encourage people to move from old and slower 5.x version, config wise it will be the same. But it will be needed if you plan to run local PHPUnit tests, CodeSniffer / Composer integrations and other tools that require PHP.ģ) You do not need any PHP Interpreter configured in PhpStorm if you plan to debug web pages - they will be handled by your web server (nginx + php-fpm as I understand) and IDE is unable to influence it anyway (provide own starting config options etc).Ĥ) Cannot really comment on Xdebug Wizard - never used it (no real need - it's for those who want simplify their life and pick the right binaries / basic setup without reading all the docs and getting into the details). I'll dive into that again, but if anyone can share guidance I'd appreciate it.ġ) What are you trying to debug - a web page or a CLI script (or both)?Ģ) You do not need local PHP Interpreter if you do not plan to execute anything local. Rereading what I just wrote (sorry about the length), it seems that Xdebug 2.6.1 is a bit of a red herring, and while it would be nice to have the Xdebug wizard say everything is fine, the more immediate issue is the PhpStorm configuration for the deployment server. I installed the earlier version (2.6.0) using Synaptic on Ubuntu with the php-xdebug package. The installation instructions aren't clear at all - particularly on where to place the files. The wizard tells me that I'm not running the latest version of Xdebug (2.6.1) which was released very recently. Next step try to run the Xdebug wizard as suggested elsewhere in the PhpStorm documentation. And I'm totally unsure what to do about any of it. The check settings link brings up a window titled CLI Interpreters, with the SSH button set. ![]() The PHP version shown is 5.6, corresponding to the version I can see on the Ubuntu server. Change takes me to the CLI interpreter - which as I wrote I don't understand why I need to set up. To fit it change project interpreter or check settings. SSH_MSG_DISCONNECT:2 Too many authentication failures. But when I try to debug a file I get the following message: I was able to get the debug configuration to validate and showing PHP 7.2. I switched the PHP version on the virtual host I wanted to use - to PHP 7.2.8-1, running as FPM/Fast CGI.īack to PhpStorm. My top priority is getting PhpStorm able to debug something. What I'm really wanting to work on isn't WordPress, and I can resolve that issue later. The reason that I had PHP 5.6 running for some of the virtual hosts on the Ubuntu server is that they are running WordPress development and there's an old plugin that doesn't work with PHP 7.2. I believe this is new because it was fine earlier. When I tried to get this all working a week or so ago, Xdebug told me - the wizard I think - that PHP 5.6 wasn't supported. Or do I? Messages from PhpStorm didn't make it clear. AFAIK, I don't need a CLI PHP interpreter setup in PhpStorm for this configuration. PhpStorm 2018.2 running on Windows 10, with files served by a Ubuntu 18.04 server for web applications. There are a quite a few moving parts.įirst, what I'm trying to get working. A few days ago, I might have just written configuring because I already had Netbeans working with Xdebug, But then messages from Xdebug, and also the way the original Ubuntu Xdebug installation was done have added to my confusion. I'm very confused about installing and configuring Xdebug for use with PhpStorm. Select your deployment server, and on the Mappings tab, click the Add New Mapping button.Īdd an additional entry that maps the /MyProject/public folder to the server document root /.Īs a result, the URL to access the validation script becomes the correct. In the Settings dialog ( Control+Alt+S), go to Build, Execution, Deployment | Deployment. To solve this, you need to set the explicit mapping between the public subfolder and the server document root. If the entire project root folder is mapped to the server document root, PhpStorm will attempt to access the validation script via the URL, which will result in a 404 error. The server document root is set to its public subfolder, that is /MyProject/public. The project is stored in the /MyProject folder. ![]() The issue can happen in situations when the server document root is different from the project root, and deployment path mappings are not configured correspondingly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |