Why Uncached DocLister Calls Return Nothing

If a cached call works but an uncached [ call returns nothing, the first assumption should not be that DocLister itself is broken. In most cases the problem is in the call syntax, parsing context, or the way surrounding markup is processed.

Example of the failing pattern

[[!DocLister?
    &debug=`2`
    &orderBy=`menuindex ASC`
    &parents=`4`
    &tvList=`img_cat1,img_cat2`
    &tpl=`home_catalog`
    &depth=`0`
    &noneTPL=`@CODE:<div class="col-12">No categories</div>`
]]

What to check

• whether the call is inside another parser layer that strips or delays uncached tags
• whether the template engine or Blade wrapper is escaping the tag instead of passing it to the Evolution parser
• whether the chunk or view around the snippet is cached independently
• whether debug output is hidden by the current response path

Practical troubleshooting order

1. test the uncached call in a minimal plain resource template
2. switch &tpl to a tiny inline template to rule out chunk issues
3. remove optional parameters and add them back one by one
4. check whether the page is rendered through an extra abstraction layer such as Blade or AJAX wrappers

Why cached and uncached can differ

A cached call may appear to work simply because the output was already generated successfully once and is now being served from cache. The uncached call forces the full parser path every time, which exposes template, parser, or integration problems immediately.

When debugging, reduce the call to the smallest possible working example and rebuild from there.