1/17/2024 0 Comments Snagit version 22They were able to get it working just by following the steps on the Xdebug Add-On page. Hi of our Devs tested getting this working on a Windows machine with Local 7.2.1 and VSCode. The double backslashes are not showing above because this editor corrects them for some odd reason (yet another thing that makes no logical sense). “”: “C:\Users\kitte\AppData\Local\Programs\Local\resources\extraResources\lightning-services\php-8.1.23+0\bin\win64\php.exe” I don’t know why this is the case, but if you enter something like I just assumed it was like a php.ini file and each line would hold a different setting.Īlso, although I am still not clear on why, when adding a path to the settings.json file for you must convert every backslash into double-backslashes. In fact, if you look at Microsoft’s own documentation about VS Code settings at Visual Studio Code User and Workspace Settings, you will find nothing that states the most basic thing about editing the settings.json file - that all settings should be inside brackets. In other videos that I had seen, it appeared that the person talking about did not have their variables within the brackets and I only found this error through continuous trial and error. The first was not knowing that the settings in settings.json must be within brackets. I found part of the problem - at least the “Cannot validate…” PHP issue.īeing new to VS Code and web development I made a couple of rookie mistakes. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed. Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. ![]() I don’t know what you are asking for here…Īttach your Local Logs here ( Help Doc - Retrieving Local’s Log) Use the setting ‘’ to configure the PHP executable.” at lower right in VS Code. Then I saw the error “Cannot validate since d:\Local Sites\wptest\ is not a valid php executable. Open VS Code and open the directory (D:\Local Sites\wptest for me). Install the Xdebug + VS Code extension for that site.Ĭlick the “Add Run Configuration to VS Code link”. What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc Use the setting ‘’ to configure the PHP executable. What issue or error are you experiencing?Ĭannot validate since a PHP installation could not be found. Nginx doesn’t state a version on the site’s dashboard What versions of site software (Nginx, Apache, PHP, MySQL) is used? Environment InfoĮxperience Windows Feature Experience Pack 1000.19052.1000.0 This is not a great video as I had already been trying to figure this out for over 12 hours on my own and I am coming down with a cold or something, but it illustrates the problem just the same.Īs precisely as you can, list the steps it takes to reliably reproduce the issue. I made a video of the installation of Local and VS Code so that you can see the exact steps that I took and how it fails. Summarize the issue in one to two sentences. You cannot connect to a Local WordPress site using the plugin and step through the code using the instructions given. ![]() If you have created any workarounds for this rule (for example, a force elevate rule) make sure you remove this workaround for users that get the new version, before you deploy it.Xdebug + VS Code does not work. If you are testing it yourself first, make sure your A/V / endpoint security agent is fully up to date and investigate the log files for any sign of our files being marked as a false positive after you install this new version. Perhaps deploy out to a few users first and release to others gradually. We don't public sub-point release versions in production, so the download file will appear not to have changed in your tenant, however if you download the MSI and right click > properties > details tab and then go to 'comments' you will see the full point release which will confirm to you that this MSI is a new / updated version.Īs some of our file checksums will have changed in this production update, I recommend letting this new version 'bed in' a short while before deploying it over your entire organisation. ![]() I have just received notification from our developers that the issue you reported on this ticket (Snagit) has been resolved, and the latest production endpoint code has been updated. ![]() ***FYI*** I just got his so let's see if they did indeed fix it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |