freekmurze

<p><a href="https://myray.app" rel="nofollow ugc">Ray</a> is a beautiful, lightweight desktop app that helps you debug your app. There’s a <a href="https://myray.app" rel="nofollow ugc">free demo</a> available that can be unlocked with a <a href="https://spatie.be/products/ray" rel="nofollow ugc">license</a>.</p>
<p>After installing this plugin, you can use the <code>ray()</code> function to quickly dump stuff. Any variable(s) that you pass to <code>ray()</code> will be displayed.</p>
<p>Here some examples:</p>
<pre><code>ray('Hello world');

ray(['a' => 1, 'b' => 2])->color('red');

ray('multiple', 'arguments', 'are', 'welcome');

ray()->showQueries();
</code></pre>
<p>There are many other helper functions available on Ray that allow you to display things that can help you debug such as <a href="https://spatie.be/docs/ray/v1/usage/framework-agnostic-php-project#measuring-performance-and-memory-usage" rel="nofollow ugc">runtime and memory usage</a>, <a href="https://spatie.be/docs/ray/v1/usage/wordpress#showing-queries" rel="nofollow ugc">queries that were executed</a>, and much more.</p>
<h3>Full Documentation</h3>
<p>The extensive documentation can be found <a href="https://spatie.be/docs/ray" rel="nofollow ugc">here</a>.</p>
<p>It contains the <a href="https://spatie.be/docs/ray/v1/installation-in-your-project/wordpress" rel="nofollow ugc">installation instructions</a> for WordPress.</p>
<p>After it is installed you can use any of the <a href="https://spatie.be/docs/ray/v1/usage/framework-agnostic-php-project" rel="nofollow ugc">framework agnostic</a> and <a href="https://spatie.be/docs/ray/v1/usage/wordpress" rel="nofollow ugc">WordPress specific functions</a>.</p>


Just start using it and it saves me a lot of time & mistakes.
It takes only a few minutes to configure and helps me a lot in my daily work.

A very good solution for a quick & effucient debugging

Easy to use, great tool

It's much easier to use Ray than do all the error_log() and var_dump() calls on a page. You do not interrupt the flow (but you can pause it!) although receive all the needed information.

It's less powerful than Xdebug (although they have different purposes and use cases), but more flexible than printing debug output on a page/debug-bar/error log.

I highly recommend it.

Awesome tool to help developers debug the code

I was having trouble debugging an issue in my WP Cron task. It's quite complex and calls out to an external database in multiple places, so trying to figure out where the issue was started driving me insane.

As there was a PHP error in my code (I was trying to call a method on null) my logger wasn't picking up any issues, nor was it even logging sometimes and no exceptions were being thrown.

After installing Ray it worked right away with no setup (other than installing it with Composer). I then managed to find the issue in about 5 minutes because of Ray's simplicity and speed in giving you the output.

The UI is minimal which is perfect as nothing gets in your way while trying to debug and having everything formatted beautifully is a massive win over basic debug logging.

I bought a licence right away and would have happily paid 2x the price I did.

Amazingly simple yet powerful 👌

Where logging fails, Ray prevails


I've been using Ray for quite a while now and I have to say, it's one of the most useful dev tools I use! Gone are the days of spewing vardump and print_r to the screen!


Extremely helpful tool!


I use this plugin everyday while doing WordPress dev work.  It's a great tool.  


Very Helpful Dev Tool

Viktor Szépe

<h4>Only for development!</h4>
<h4>Now with OPcache memory consumption support</h4>
<p>This plugin dumps the colorized filenames and memory consumptions or file sizes after the normal WordPress HTML output, after the closing html tag. This generates invalid HTML but gives you an overview of loaded plugins and the current theme.</p>
<p><em>What’s running</em> lists all files parsed and executed by the PHP engine. It can be used for plugin or theme refactoring.</p>
<h4>Now you can highlight your own plugin and theme</h4>
<p>Provide a part of its path in wp-config.php:</p>
<pre><code>define( 'WHATS_RUNNING_HIGHLIGHT', 'wp-content/plugins/my-plugin' ); </code></pre>
<h4>Color codes</h4>
<ul>
<li>your code is highlighted with YELLOW background</li>
<li>plugin files are in BLUE</li>
<li>themes files are in ORANGE</li>
<li>files in the wp-includes directory are in GREEN</li>
<li>files in the wp-admin directory are in GREY</li>
<li>all other files are in RED</li>
<li>VIOLET bar after the filename represents the file size ( 0.5 kB/px )</li>
<li>DARK MAGENTA bar after the filename represents the OPcache memory consumption ( 1 kB/px )</li>
</ul>
<h4>Links</h4>
<p>You can watch <a href="https://core.trac.wordpress.org/ticket/28364" rel="nofollow ugc">WP core bug #28364</a> to get more information about <a href="https://github.com/szepeviktor/WPHW/blob/master/wp-entry-points.md" rel="nofollow ugc">WordPress entry points</a>.</p>
<p>You can find some documentaion here what makes a WordPress plugin efficient: https://github.com/szepeviktor/WPHW</p>
<p>Development of this plugin goes on on <a href="https://github.com/szepeviktor/whats-running" rel="nofollow ugc">GitHub</a>.</p>


What's running

Lists WordPress require() calls mainly for plugin code refactoring.

Ray vs What's running