freekmurze

<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>.
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.
Here some examples:
<pre><code>ray('Hello world');

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

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

ray()->showQueries();
</code></pre>
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.
<h3>Full Documentation</h3>
The extensive documentation can be found <a href="https://spatie.be/docs/ray" rel="nofollow ugc">here</a>.
It contains the <a href="https://spatie.be/docs/ray/v1/installation-in-your-project/wordpress" rel="nofollow ugc">installation instructions</a> for WordPress.
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>.

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>
Displays:
<ul>
<li>Header</li>
<li>Thumbnails</li>
<li>The Loop (content)</li>
<li>Footer</li>
<li>Included template parts</li>
<li>Highlight script, link and style elements</li>
</ul>
To remove all registered scripts and styles add <code>?remove-scripts</code> to the URL. All these scripts and styles will be listed at the bottom of the footer as HTML comment. This way it is possible to detect non-WordPress script printing.
If you are not an administrators add <code>?view-source</code> to the URL to activate Frontend Debugger.
Notice: This plugin uses regular expressions and <code>eval()</code> to get the current template apart.
TODO: sidebar, search-form.
The mini control panel contains:
<ul>
<li>Header, Thumbnails, The Loop, Footer, Included files anchors</li>
<li>Toogle button for line numbers</li>
<li>Toggle button for line wrapping</li>
<li>Toggle button for showing line ends</li>
<li>Button for script and style highlighting</li>
</ul>
From the second click on the <code>Highlight</code> button loops through (scrolls to) all scripts and styles.
The control panel’s state is kept in your browser’s <a href="https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage" rel="nofollow ugc">localStorage</a>.
Development of this plugin goes on on <a href="https://github.com/szepeviktor/frontend-debugger" rel="nofollow ugc">GitHub</a>. Please contribute by sending PR-s implementing my TODO-s.

Frontend Debugger

Display prettified page source on the frontend.

Ray vs Frontend Debugger