<p>Validation errors will still get logged to <code>craft/storage/runtime/logs</code> with a <code>[warning]</code> label.</p>

<p>Other than that, you options are just like you'd debug anything else in PHP.  Preferably with <a href="http://xdebug.org/" rel="nofollow">xDebug</a>, but you can always manually <code>Craft::log()</code> and read the log files, too.</p>

CC BY-SA 3.0
2015-04-29T08:33:17.140Z
Ok great, what are the advantages of xDebug (not used it before). Also is there an easy way log arrays?
Sam Hibberd
CC BY-SA 3.0
2015-04-29T00:36:36.007Z
2015-04-29T00:36:36.007Z
Brad Bell
<p>I am having issues debugging craft tasks where the issue is caused by validation errors rather than php syntax / environment issues. </p>

<p>How do you debug validation errors in craft tasks?</p>

<plugin-development><tasks>
Task Validation Debugging
# Task Validation Debugging

(Asked by: username_0 on 2015-04-28)

I am having issues debugging craft tasks where the issue is caused by validation errors rather than php syntax / environment issues.

How do you debug validation errors in craft tasks?

**Tags:** plugin-development, tasks


---

## 1 answers

### Answer by username_1 on 2015-04-29. Score: 1

Validation errors will still get logged to `craft/storage/runtime/logs` with a `[warning]` label.

Other than that, you options are just like you'd debug anything else in PHP. Preferably with [xDebug](http://xdebug.org/), but you can always manually `Craft::log()` and read the log files, too.

> **Comments:**
> **username_0**: Ok great, what are the advantages of xDebug (not used it before). Also is there an easy way log arrays?  

---

