![]() Then I created a new Local site and ported my plug-ins and made sure everything worked fine. To be really precise, I was working on my original test Local site until the end of October. Could this have anything to do with the new Local and/or Xdebug+VS Code add-on? I believe the only thing that has changed in the meantime is Local was update. I just went back to update my program today and I can no longer use the debugger (it doesn’t break on any break point). I had been developing WP shortcode plug-ins using VS Code until the end of this October and everything was working fine. I am dead in the water without debugger and am really desperate with work I need to get done. I’d really appreciate any help, information you could give me. Today I have spent hours reading Xdebug’s documentations but so far things look like what they say they should be. I am very new to WP+Local+PHP+Xdebug so I have little experience. Before Local 6.5 update, I think PHP version was different, even though I cannot remember what it exactly was. ![]() ![]() It also says “Unable to load dynamic library 'php_imagick.dll” even though I have no idea if that has anything to do with it. When I run php -v from the site shell (launched from Local), it says “with Xdebug v2.9.0, …”. I noticed that the newly generated launch.jason as “Listen for Xdebug 3.0” and “Listen for Xdebug” but neither of them works. vscode folder in the site’s app/public folder, regenerated it and restarted Local but it still doesn’t work. ![]() I read some of the previous conversations in the forum, and tried deleting. The only thing that changed in the meantime is Local update. Today I came back to work more on the same plugins and I can no longer debug in VS Code. I have been developing WP shortcode plugins using VS Code (with Xdebug+VSCode add-on) and everything was working fine until the end of October. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |