Use Xdebug profiler with PhpStorm

Today I played around a while trying to configure Xdebug profiler to work with PhpStorm.  The following config only apply to a local LAMP stack with Xdebug installed with homebrew.

Here is the xdebug.ini I used :

[xdebug]
zend_extension="PATH_TO_EXT"
xdebug.remote_enable=on
xdebug.remote_connect_back=1
xdebug.default_enable=1
xdebug.remote_autostart=1
xdebug.remote_host=localhost
xdebug.remote_handler=dbgp
xdebug.remote_port=9000
xdebug.cli_color=on
xdebug.profiler_output_dir=/PATH/TO/DIRECTORY
xdebug.profiler_enable_trigger = 1;

The folder you choose for the output must be writable by the server. You can also be lazy and do : chmod 777 /PATH/TO/DIRECTORY

Once this is set, you can use this nifty little chrome plugin to start profiling.

The output will be written to the folder you specified. You can use it and let PhpStorm interpret the result for you by choosing : Tools | Analyze XDebug Profiler Snapshot.

PhpStorm custom icons

I stumble upon an excellent icon alternative made by Bernard Kowalski to the boring standard PhpStorm icon. You can download it here 😉

Here are the steps to replace your PhpStorm icon so it shows within the application itself:

  1. Right-click on PhpStorm.app and Show Package Contents
  2. Navigate to Contents/Resources/
  3. Replace webide.icns with custom icon (making sure the name is exactly the same)

Enjoy!

 

Why is my site broken?

If you are a WordPress developer/freelancer, I’m pretty sure you’ve heard your client say this more than once. Unfortunately, there is no core user activity log in WordPress and no easy way to tell who broke the site by modifying that “pesky” blog settings. Of course, one could remove admin privileges on the site, but is that really a solution?

I’ve recently been contributing to a plugin called Stream to solve exactly that problem. Please try it out and give us feedback!

Read more on X-Team.com

Optimize your Vagrant workflow with WP-CLI SSH

Read the original article on X-Team.com


One pitfall I’ve recently encountered with Vagrant and WP-CLI was the lack of an easy way to use my local WP-CLI installation to send a command to my Vagrant box.

X-Team’s Weston Ruter first developed an incredible tool called vassh, which basically removes the pain of having to manually SSH into the Vagrant box and run the command from the project root. While vassh is really useful, it only works for Vagrant and not for remote servers.

After working closely with the WP-CLI team and refactoring multiple times, we finally came up with something called “WP-CLI SSH” which facilitates running WP-CLI commands on other servers, while invoking WP-CLI normally as if it was on your own system.

Continue reading “Optimize your Vagrant workflow with WP-CLI SSH”