Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Follow: https://drupal.org/node/2055947 first
Following optional - if you want debugging with Komodo IDE 8
Summary of steps, followed by detail:
13. Download xdebug.so from komodo - downloads.activestate.com/Komodo/releases/8.0.2/remotedebugging/ (get correct version of PHP remote debugging 32 or 64)
14. Extract out the contents of the download from 13, sftp as root to the guest VM, rename the existing xdebug.so (to keep) and put xdebug.so from komodo
15. ssh into the VM, as root, edit php.ini with xdebug setings from komodo - http://docs.activestate.com/komodo/8.0/debugphp.html
16. restart the apache webserver on VM for the php changes to take effect
17. Launch Komodo, create new project - specify path to be the drupal folder on the VM (in step 11) - folder is shared with host and it is a subfolder off the vagrant folder of the host - where you unzipped vagrant to and run vagrant up from e.g. vagrant/wheezy64/drupal8
18. In Komodo preferences for debugger - settings: break on first break point, listen on port 9000, allow the debug connection
19. Find a bit of your website code in Komodo that you know will be executed when the front page of the site is visited, set a breakpoint there
20. Visit the site on a browser, e.g.: http://192.168.56.101/drupal8/index.php?XDEBUG_SESSION_START=1
21. Observe that Komodo breaks on the breakpoint and asks about URI mapping (one-off question) - specify the local path as in 17. You can also set this up beforehand in URI settings in preferences to avoid being asked.
In detail:
13.
Komodo (for example v8 - ought to work with earlier, and later) debug setup
http://downloads.activestate.com/Komodo/releases/8.0.2/remotedebugging
Choose Komodo-PHPRemoteDebugging-8.0.2-78971-linux-x86_64.tar.gz
(v8 is now at 8.5.2 and there is also a v9 released - I will confirm v9 works in a little while but I expect it will)
14.
Extract the contents
For this VM, the version of php is 5.4
(can also check the version it in the vm at the commandline by typing php -v)
So navigate to the extracted content folder '5.4' where you will find ActiveState Komodo's especially compiled version of xdebug.so
open a terminal session / command line window
cd to the 5.4 folder (or wherever you moved the ActiveState Komodo's especially compiled version of xdebug.so to )
(in general:)
sftp root@ipaddressofvm
- where ipaddressofvm is the ip address of the vm, e.g. 192.168.56.101
e.g.:
sftp root@192.168.56.101
password root
once in sftp, go to the usual location of xdebug.so
For this wheezy64 setup this is:
/usr/lib/php5/20100525/xdebug.so
(note: different Linux distros and versions can have different path locations for xdebug.so )
you may want to keep the existing xdebug.so for other purposes so rename it
e.g.
sftp> rename xdebug.so xdebug.so.default
then place ActiveState Komodo's especially compiled version of xdebug.so in the folder
issue the command:
put xdebug.so
15.
ssh in as root
need to add some xdebug config lines to the php.ini
find the path of the php.ini file by issuing
php --ini
(e.g. for this distro on this vm it would be: /etc/php5/apache2/php.ini for the web server, if debugging drush commands you'll want to set this up in the CLI version of the php.ini - e.g. /etc/php5/cli/php.ini)
At the end of the php.ini file (logged in as root), add the following
; xdebug config for Linux and Mac OS X
zend_extension="/usr/lib/php5/20100525/xdebug.so"
xdebug.remote_enable=1
xdebug.remote_handler=dbgp
xdebug.remote_mode=req
xdebug.remote_host=127.0.0.1
xdebug.remote_port=9000
xdebug.idekey=<idekey>
; You may also want this - to always start a remote debugging connection.
;xdebug.remote_autostart=1
save the file and exit
reference:
http://docs.activestate.com/komodo/8.0/debugphp.html
(for later versions of Komodo, replace the 8.0 with the later version, e.g. 8.5)
note about the line:
zend_extension="/usr/lib/php5/20100525/xdebug.so" ; (path to the xdebug.so file (which is now ActiveState Komodo's especially compiled version of xdebug.so - note this path location varies with linux distributions and versions of php)
restart apache - I think this is necessary for the changes to take effect
16. restart apache
sudo /etc/init.d/apache2 restart
Credit/reference: http://www.cyberciti.biz/faq/star-stop-restart-apache2-webserver
17.
Launch Komodo, create new project - specify path to be the drupal folder on the VM (in step 11) - folder is shared with host and it is a subfolder off the vagrant folder of the host - where you unzipped vagrant to and run vagrant up from e.g. vagrant/wheezy64/drupal8
18. Set komodo debugger preferences to listen on 9000
19.
Find a bit of your website code in Komodo that you know will be executed when the front page of the site is visited, set a breakpoint there
20. Visit the site on a browser
e.g.
http://192.168.56.101/drupal8/index.php?XDEBUG_SESSION_START=1
21.
Observe that Komodo breaks on the breakpoint and asks about URI mapping (one-off question) - specify the local path as in 17. You can also set this up beforehand in URI settings in preferences to avoid being asked.
Detail:
Will be prompted about URI mapping in Komodo
- this is so that komodo can edit the files on the VM as you develop
file://192.168.56.101/var/www/drupal8
/Users/robdaviswork/work/projects/vagrant/wheezy64/drupal8
