You're welcome.
Articles (and some other Extras) can be quite confusing.
Sometimes they do install the default templates in the backend where you can find them under the chunk node.
And sometimes they won't do that. They then just use the default template that is stored in the folder the extra is stored.
E.g. Articles combines different "stand-alone" extras as Quip (for comment functionality) and tagLister (for the tagging stuff).
Quip does install the default templates, tagLister doesn't.
When Articles (or in this case tagLister) is installed, this process creates a folder
core/components/tagLister/
and in there you'll find all the tagLister stuff.
In the subfolder "elements/chunks" there are the defaults chunks.
Have a look at the tagLister-Snippet (click on it in the backend in the Elements-tree). There you'll find
/* setup default properties */
$tpl = $modx->getOption('tpl',$scriptProperties,'tag');
This tells tagLister to use the default template "tag" if there is no Option in the tagLister-call that tells it to grab another chunk.
E.g.
[[tagLister &tpl=`myChunk`]]
calls tagLister with the Template-Chunk "myChunk".
calls the tagLister with the default template "tag".
Working with Articles makes it even more confusing 'cause it calls tagLister for you and you won't find the call in your code.
It just throws out the tags within the placeholder
.
Hope this helps to clarify a little bit.
f.
