Now I hit the start deebug bookmark, in the phpStrom press on start to listen to php debug and set any breakpoint in php scope, set the Xdebug extension on Debug mode, browse to localhost/m圜ode/index.php but no any debugging is occur in the phpStrom. Īs described in Xdebug generator, I added two bookmarks - start debug and stop debug for IDE key = PHPSTORM. In this manual I paste all the content of php -i and did all what it required. What is missed here and how to make it works with xDebug?įollowing the suggested in the comments, I followed this tutorial and now I have the chrome extension - Xdebug. Now I mark some breakpoints, go to Chrome and navigate to but no any phpStrom debugger is promted although the entire website is got loaded. Under File > PHP > Servers: Name: m圜odeDebugĪbsolute path on server: (same as the project location). My entire project is located in C:\work\Projects\xampp\htdocs\m圜ode console-logger: Key event not available on GTK2: key=“u” modifiers=“control,shift” (1) in chrome://komodo/content/tail/tail.I try to configure my phpStorm for debugging according to this tutorial. If you get this message, a pref panel is incorrectly modifying prefs and the modified value will be lost. prefs: The ‘ all’ preference has changed while the pref window was open. prefs: The ‘phpConfigFile’ preference has changed while the pref window was open. console-logger: TypeError: tab is undefined (2) in viewbrowser:133 koPHPConfigurator: Unable to retrieve PHP version koAppInfo: could not determine PHP version number for ‘c:\wamp64\bin\php\php8.1.0\php.exe’: PHP interpreter did not return in time. koPHPConfigurator: Debugger extension for PHP version 8.1.0 (path C:\Program Files (x86)\ActiveState Komodo IDE 12\lib\support\php\debugging\8.1\php_xdebug.dll) is not available. koPHPConfigurator: Unexpected compiler: Visual C++ 2019 (1) in less://komodo/skin/global/global.less:1429 console-logger: Unknown descriptor ‘font-display’ in rule. (1) in chrome://global/content/bindings/richlistbox.xml:366 console-logger: Empty string passed to getElementById(). (1) in chrome://global/content/bindings/richlistbox.xml:361 Now I have to get my perl up and running againĭoing what you suggested (without Directory containing php.ini set) ko.launch: Response: (0) You can see what Komodo is looking for in the php.ini file in the php folder I mention above. If local debugging wasn’t working then it’s likely that the folder structure you constructed (perhaps from incorrect instructions from me) was not quite right. You can find that ini file in your Komodo Profile folder in the php folder. Komodo creates a php.ini file based on the PHP you pointed it at. I should note that for local debugging, you don’t need to set the PHP.ini file location in your preferences. One question: can you ellaborate on your comment about Dynamic Extensions? I can’t find any documentation about what that is so I’m not sure I’ve done that correctly. Let me know if that matches what you have. zend_extension="c:\path\to\php_xdebug.dll" Zend_extension_ts="c:\path\to\php_xdebug.dll" I’ve made a diff of what I think your change ended up being compared to the documented php.ini settings: diff -git a/service/dashboard/php.ini b/service/dashboard/php.ini Hey good digging This will be super helpful for others. I also had to comment out duplicate xdebug settings at the bottom of the file. The following php.ini settings under " Dynamic Extensions " seemed to do the trick. Note that xdebug setting names have changed for higher versions. Zend_extension=“C:/Program Files (x86)/ActiveState Komodo IDE 12/lib/support/php/debugging/8.1/nts-vs16-圆4/php_xdebug.dll”Īny ideas how I can get remote debug to work? Zend_extension_ts=“C:/Program Files (x86)/ActiveState Komodo IDE 12/lib/support/php/debugging/8.1/ts-vs16-圆4/php_xdebug.dll” Maybe newer versions op php will not be compatible with komodo? I have updated them as suggested, however I still do not have remote php debug capability. PHP Parse error: syntax error, unexpected ‘Failed’ (T_STRING) in C:\wamp64\scripts\loaded_extensions.php on line 54 Xdebug: The setting ‘xdebug.remote_port’ has been renamed, see the upgrading guide at (See: ) Xdebug: The setting ‘xdebug.remote_mode’ has been renamed, see the upgrading guide at (See: ) Xdebug: The setting ‘xdebug.remote_host’ has been renamed, see the upgrading guide at (See: ) Xdebug: The setting ‘xdebug.remote_enable’ has been renamed, see the upgrading guide at (See: ) So it seems that has changed some of it’s setting names.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |