1. Why should I use PhpStorm?
1.1. General Info
Get PhpStorm from:
General info from:
Started during http://tiki.org/TikiFestBarcelona3 !
1.2. Top 10+ Reasons to Love PhpStorm
- Navigate -> File... (and Class... and Symbol...)
Especially the way you can type the initials of the words in the filename
e.g. "t a t o o" gets you tiki-admin_toolbars (the php, tpl and js files if you want)
- Edit -> Copy Reference
Except the way it includes the leading slash... must looks for a pref for that!
makes me smile, but seriously, the debugger knows what's going on to a far deeper level than any other PHP IDE i've tried
- Code -> Refactor as... (variable, method etc)
Common on Java IDE, but not seen it on PHP
- Code -> Comment/Un-comment
Sounds trivial but it's the first thing i've found that does it correctly in all languages, not just PHP and JS, but Smarty, HTML and CSS too
- View -> Compare with clipboard (you can merge changes form the clip board into an open file)
- CSS colour indicators
- Column select
- Tools -> Deployments -> Sync and Diff with Deployment
- Code completion on SQL files (fills in tables and column names from your database - thanks Luci ;)
- Branch merging - as you would expect, far more civilised (and quick) than any other IDE i've tried, and so much more controllable (for me) than using a shell
- Shelve changes which reverts your current changes and keeps them in a safe(ish) place until you want them back again
- Live templates: create your own idiosyncratic code snippets and insert them by typing an abbreviated name followed by TAB
- You can get a free version for use on your Tiki work (see details below)
2. Setting it up
2.1. Getting a Free OpenSource license for your Tiki work
If you are a regular contributor to the TikiWiki project, then you may be eligible for a free license to PhpStorm.
Just contact Nelson (nkoth on IRC) and ask him for the user name and license key. Then:
- Start PhpStorm
- Help > Register
- Enter the user name and license key exactly as in the email
Don't enter the key as a single line!
The license key you will have received, may be on several lines.
You must enter it exactly like that, without trying to "unwrap" the key into a single line.
2.2. Configuring the Debugger
Choose some debugger like Xdebug:
sudo apt-get install php5-xdebug phpunit
Under Mac 10.9 Maverick using MacPorts (couldn't manage to install phpunit) Bernard Sfez / Tiki Specialist :
sudo port install php5-xdebug
or similar (Zend_debugger)
Settings to be pasted from Robert's config at the end of /etc/php5/apache2/php.ini
[debug] ; Remote settings xdebug.remote_autostart=off xdebug.remote_enable=on xdebug.remote_handler=dbgp xdebug.remote_mode=req xdebug.remote_host=127.0.0.1 xdebug.remote_port=9000 ; General ;xdebug.auto_trace=on ;xdebug.collect_includes=on ;xdebug.collect_params=on ;xdebug.collect_return=on ;xdebug.default_enable=on ;xdebug.extended_info=1 xdebug.manual_url=http://www.php.net xdebug.show_local_vars=0 xdebug.show_mem_delta=0 ;xdebug.max_nesting_level=100 ;xdebug.idekey= ; Trace options xdebug.trace_format=0 xdebug.trace_output_dir=/tmp xdebug.trace_options=0 ;xdebug.trace_output_name=crc32 ; Profiling xdebug.profiler_append=0 xdebug.profiler_enable=0 xdebug.profiler_enable_trigger=1 xdebug.profiler_output_dir=/tmp/ xdebug.profiler_output_name=cachegrind.out.%t-%R
2.2.1. Remote Debugging
Some useful info on setting up xdebug and phpstorm to do remote debugging can be found here: https://confluence.jetbrains.com/display/PhpStorm/Remote+debugging+in+PhpStorm+via+SSH+tunnel, mainly the part about the ssh port 9000 tunnel - that's the bit that was missing for me Jonny Bradley
2.3. Configuring the PHP interpreter & path
PhpStorm expects to find the Php interpreter in a particular location (ex: on my mac, it's /usr/bin/php). But it could be that you are using an interpreter that is in a different location.
Here is how you can do that. The particulars of the steps seem to depend on the version of PhpStorm you use. Below are the steps as described originally by Jonny, and those for PhpStorm 6.0 (written by Alain)
# For PhpStorm 6.0
1. PHP Interpreter
- Preferences > PHP
- Click on ... to the right of Interpreter.
- Browser to the location of the php interpreter (ex: /opt/local/bin)
- Click on the + sign at the top left, then Specify other
- For Name, enter a freetext name for that version of the interpreter (you could just set it to the full path)
- For PHP home, enter the path of the directory that contains the php executable (ex: /opt/local/bin). Do not include php at the end of the path (it has to be a directory, not the path to the executable itself).
2. Include path
- Preferences > PHP
- Choose the interpreter for which you want to set the path, by clicking on the ... to the right of Interpreter
- Click on the + sign at the bottom right of the PHP window
- NOT SURE ABOUT THE REST
# Original instructions by Jonny
File → Settings → PHP (open)
1. PHP Interpreter
Interpreter > Add
Enter the following:
Name: "php on ubuntu" (free text)
PHP home: /usr/bin/
→ See appear the PHP version (here PHP version 5.3.... )
2. Include path
- Click at the plus sign
- add path to application source (real place without links)
- Name: localhost
- Host: localhost
- Port: 80
- Debugger: Xdebug
- (X) Use path mappings (select if the server is remote or symlinks are used)
2.5. Add a PHP Web Application
Run > Debug > Edit configurations > Click at the plus sign in the left column > PHP Web Application: "Run/Debug Configurations"
2.6. Configure Subversion (SVN)
VCS > Some option to set the project as being under subversion (we do notsee the option any more once it is selected once).
Since then, you have all the options for managing the subversion checkout.
To update from trunk svn, do:
VCS > Subversion > Update files
IF requested, select the branch that you are working with (ues HEAD for trunk).
One thing to watch out for is that you need to disable certain options in the commit dialog:
Basically, all the checkboxes in the Subversion and before commit section have to be unchecked.
To get to that box, you need to do a commit:
- Make sure you have at least one outgoing change.
- Click on the Changes tab at bottom of the screen.
- Right click on one of the changes in the Default section.
- Commit Changes
- You should now see the dialog depicted in the above screenshot.
3. Troubleshooting and Tips for Newbies
"Could not save project" error
If you get this error, it probably means that the permissions on your Tiki files are wrong. Typicall, when you run setup.sh, all the files in Tiki end up being owned by _www with _www as the group (unless you specify other choices). But on most platforms (at least on Mac), PhpStorm runs as your own regular user, which is not part of group _www.
Here is how to fix this issue on Mac. Details for other platforms may vary.
# First, add your user name to group _www sudo dseditgroup -o edit -a yourusername -t user _www # Next, rerun setup.sh, but this time, specify # yourusername as the user, but leave _www as # the group sudo sh setup.sh # Then make sure certain directories are writeable # by the _www group. sudo chmod -R g+w db dump img/wiki img/wiki_up img/trackers modules/cache templates_c templates styles whelp
'Cannot find PHPUnit in include path' error
When attempting to run project '9.x' on 'LocalApache' server, I see these messages:
Once phpunit is installed (& phpstorm restarted), the error message dissapears.
'Debug server doesn't exist' error
When attempting to go to "Run > Debug '9.x on LocalApache'", I see this message at the bottom:
Ok, after I added "localhost" as Debug Server, and run again "Run > Debug '9.x on LocalApache'", I did get these messages:
Can't commit a change
Sometimes, nothing happens when you click on the Commit button.
When that happens, make sure you uncheckall the boxes in the Subversion and before commit section have to be unchecked.
'Connection with 'xdebug' was not established' error
You typically get this error when running the debugger PHP Script run configuration.
The error usually means that the PHP interpreter you are using does not have the xdebug extension installed.
To find out which interpreter you are using
- Preferences > PHP
- Click on ... to the right of the Interpreter field
- The path of the interpreter is in the PHP Home field.
To see if xdebug is installed for that interpreter:
pathtoyourinterpreter/php -i | grep xdebug
If the phpinfo doesn't contain any line with xdebug, it means it's not installed.
To install xdebug for use with PhpStorm, see the Configuring the Debugger section above.
PhpStorm becomes sluggish
If you notice that PhpStorm occasionally gets in a rut and becomes very slow in responding to your actions, it probably means that you haven't allocated enough heap memory to it.
The way to fix it is to add the heap size in file idea.vmoptions. On the mac, this file is located under ~/Library/Preferences/WebIde60/.
For example, here is Alain's idea.vmoptions file:
-Xms128m -Xmx2048m -XX:MaxPermSize=350m -XX:ReservedCodeCacheSize=96m -XX:+UseCodeCacheFlushing -XX:+UseCompressedOops
Can't use svn from command line
Althogh the graphical svn UI in PhpStorm is pretty good, there may be time when you want to use the command line SVN.
If you do that, it could be that the command line SVN will complain that the current directory is in the wrong SVN format.
This is usually due to the fact that PhpStorm uses its own version of SVN (which is embedded as a java library), and that it uses a SVN data format that is more recent that the command line SVN you are using. For example, maybe your command line SVN uses the 1.6 format, while the PhpStorm svn uses 1.7.
There are two ways to deal with this
- Upgrade your command line SVN so it can deal with the data format version used by PhpStorm.
- Redo the checkout, but ask PhpStorm to store the data in the format that your command line uses.
As of this writing (Oct 29, 2013), the easiest option for Mac users seems to be to redo the checkout, because macport doesn't seem to have version 1.7 of the command line SVN (which is what PhpStorm uses by default).
4. Useful tips
Turn on Autoscroll from source option, so that the project browser repositions itself automatically to the page you are currently have in the editors. That way, if you want to do an operation on the file you are editing (ex: delete, rename), or see other files in the viscinity, you can just go from the editor to the project browser.
To set this option on:
- Click on the project
- Click on the gear icon (top right of the project browser)
- Check Autoscroll from source
Make use of the various navigation and search shortcuts. One really powerful thing about those is that you can search for things by specifying parts of its name, that might not be consecutve. So for example, searching for a file with "tiki permissions" will find "tiki-debug-permissions.tpl".
Below are some of the more useful search and navigation shortcuts:
- Command+Shift+O: search for a file.
- Ctrl+Shift+F: Search all files in the project
- Command+O: Search for a class.
- Ctrl+Command+O: Search for a symbol (class, method, variable, etc...)
4.2. How to merge
Useful tip provided by jonnyb in the devel list (27/02/15)
5. Useful links
Free video tutorial to help you setting (xdebug) and customising PhpStorm: https://laracasts.com/series/how-to-be-awesome-in-phpstorm/