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

<p>Toggles human and machine language (aka ID-s) on admin pages.</p>
<h4>Only for development!</h4>
<p>This plugin shows you the ID-s of almost all form fields including selects, checkboxes and radio buttons like in <code>wp-admin/options.php</code>.</p>
<p>It works only on WordPress Settings API-like formatted — not necessarily API generated — admin pages. E.g. <code><input></code> elements cannot be wrapped in <code><span></code>.</p>
<h4>Activation</h4>
<p>You can find the plugin’s checkbox in standard Screen Options (upper right corner). This checkbox could be overwritten — thus hidden — by poorly written plugins. To restrict Machine Language to a certain admin page, copy this to your <code>wp-config.php</code>:</p>
<pre><code>define( 'MACHINE_LANGUAGE_HOOK', 'load-options-reading.php' ); </code></pre>
<p>For example this line causes to run only on Settings / Reading.</p>
<h4>Features</h4>
<ul>
<li>Basically all input ID-s are displayed in place of labels, actually <code>for</code> attributes of labels</li>
<li><code>select</code>-s get a title showing all option values comma separated (hover over <code>select</code>-s with your mouse)</li>
<li><code>option</code>-s get values appended in the form of “original option text|value”</li>
<li>Radio button labels will show: “name|value”</li>
<li>Descriptions (<code>p</code>-s and <code>span</code>-s with “description” class) will be hidden, this way Machine Language will clean up all admin pages, descriptions are hidden by CSS, so there’s no <a href="http://en.wikipedia.org/wiki/Flash_of_unstyled_content" rel="nofollow ugc">FOUC</a></li>
</ul>
<h4>Other notes</h4>
<ul>
<li>Radio buttons or checkboxes with empty value are displayed with the “Empty Set” Unicode character: “? ” (U+2205) ( e.g. Settings / Permalinks / Default )</li>
<li><code>select</code>-s with empty values are not</li>
<li>The plugin’s checkbox in Screen Options is effective immediately</li>
<li>The code is designed as a must use plugin, so there is no separated Javascript or CSS file</li>
<li>State of Machine Language is saved as a user option so it is a per user setting</li>
</ul>
<h4>Links</h4>
<p>Development goes on on <a href="https://github.com/szepeviktor/machine-language" rel="nofollow ugc">GitHub</a>.</p>


Ray vs Machine Language