<p>If you look in the list of file paths in the stack trace there will be one or more files in the <code>storage/runtime/compiled_templates</code> directory. In this particular case there is <code>storage/runtime/compiled_templates/1a/1a584296a...ccfb9.php</code> under number 33 in the stack trace. (If you're using PhpStorm you can press <kbd>shift</kbd> twice and paste in the filename to find it quickly.)</p>

<p>This file contains a PHP class that Twig <a href="https://twig.symfony.com/doc/2.x/internals.html#the-compiler" rel="nofollow noreferrer">compiles</a> when the template is first accessed, so that it doesn't need to parse through all the twig code converting it into PHP every time the template is accessed.</p>

<p>At the top of this file is a comment that contains the path of the actual twig template. If needed, you might be able to work out a bit more context by looking at code at the line number in the stack trace (it's the <code>:43</code> for this one). There will be another comment above this line that will tell you the line number in the twig template.</p>

<p>There may also be some clues in the stack trace itself. For example, here (again number 33 in the stack trace) you have the line:</p>

<pre><code>twig_array_merge([], craft\elements\db\CategoryQuery)
</code></pre>

<p>This suggests to me that you're using the <code>|merge</code> filter, on a <code>craft.categories</code> query without calling <code>.all()</code> on it first, which also makes sense given the deprecation notice.</p>

CC BY-SA 4.0
2019-01-08T12:03:54.033Z
This is great! I was calling a category based on the category parameter in the URL but wasn't calling `.one()`.
Jay
CC BY-SA 4.0
2019-01-07T13:28:32.307Z
2019-01-07T19:00:54.680Z
2019-01-07T19:00:54.680Z
Mike Pepper
<p>I'm getting a deprecation error about looping through element queries, but in my markup all my loops are being setup with the <code>.all()</code> method, so I'm struggling to find this.</p>

<p>And it's one that is coming up every time I clear my errors, so the CMS clearly still thinks it's an issue.</p>

<p><a href="https://i.sstatic.net/POe6v.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/POe6v.png" alt="Deprecation error"></a></p>

CC BY-SA 4.0
2019-01-04T22:27:25.837Z
Can you share what you see when you click on that "Stack Trace" link?
Brad Bell
CC BY-SA 4.0
2019-01-06T17:02:30.563Z
Opening few lines: https://imgur.com/a/fB6Jpu5
Jay
<craft3><error-message><error>
Best way to find a deprecation error with no location hint?
# Best way to find a deprecation error with no location hint?

(Asked by: username_0 on 2019-01-04)

I'm getting a deprecation error about looping through element queries, but in my markup all my loops are being setup with the `.all()` method, so I'm struggling to find this.

And it's one that is coming up every time I clear my errors, so the CMS clearly still thinks it's an issue.

[![Deprecation error](https://i.sstatic.net/POe6v.png)](https://i.sstatic.net/POe6v.png)

**Tags:** craft3, error-message, error

> **Comments:**
> **username_1**: Can you share what you see when you click on that "Stack Trace" link?  
> **username_0**: Opening few lines: https://imgur.com/a/fB6Jpu5  

---

## 1 answers

### Answer by username_2 on 2019-01-07. Score: 4 | Accepted answer

If you look in the list of file paths in the stack trace there will be one or more files in the storage/runtime/compiled_templates directory. In this particular case there is storage/runtime/compiled_templates/1a/1a584296a...ccfb9.php under number 33 in the stack trace. (If you're using PhpStorm you can press shift twice and paste in the filename to find it quickly.)
This file contains a PHP class that Twig compiles when the template is first accessed, so that it doesn't need to parse through all the twig code converting it into PHP every time the template is accessed.
At the top of this file is a comment that contains the path of the actual twig template. If needed, you might be able to work out a bit more context by looking at code at the line number in the stack trace (it's the :43 for this one). There will be another comment above this line that will tell you the line number in the twig template.
There may also be some clues in the stack trace itself. For example, here (again number 33 in the stack trace) you have the line:
twig_array_merge([], craft\elements\db\CategoryQuery)

This suggests to me that you're using the |merge filter, on a craft.categories query without calling .all() on it first, which also makes sense given the deprecation notice.

> **Comments:**
> **username_0**: This is great! I was calling a category based on the category parameter in the URL but wasn't calling `.one()`.  

---

