When a snippet returns a snippet call, weird things are happening with logging.

I’m trying to use getResources with an output tpl chunk that contains a snippet call:


I’ve discovered that if ’mySnippet’ contains any sort of logging statements, like

...the log data is getting output with the results of the snippet. Further, if ’mySnippet’ itself internally calls any other snippets, and those snippets contain logging statements, they are also returning results that are corrupted by the log data.

It appears that any snippet calls that are output *by* a snippet call (or at least by getResources- haven’t tried this with other snippets) are spewing the logging data into their output, and messing things up royally.

Is this a bug? (Or a feature?) Is there a different/preferred way to accomplish what I’m trying to do?

It seems you have a $modx->setLogTarget(’ECHO’) call somewhere, that’s causing your log messages to be ECHO’ed rather than output to core/cache/logs/error.log.

Quote from: splittingred at Oct 11, 2010, 10:26 AM

It seems you have a $modx->setLogTarget(’ECHO’) call somewhere, that’s causing your log messages to be ECHO’ed rather than output to core/cache/logs/error.log.

You wish you could get off that easy, buddy...

If that were the case, then ALL of my log messages would be getting ECHO’ed regardless of how I was calling the snippets, right? But it is only happening in cases where a snippet outputs a snippet call.

Here’s a simple way to reproduce this:

1. Create an output chunk for getResources that looks like this:


2. add a logging command somewhere in UltimateParent:


3. Create a resource that both 1) calls UltimateParent directly and 2) calls getResources with the output chunk that calls UltimateParent:


Now fire up the grill, view that resource and let me know what happens. I’ll wait

Quote from: splittingred at Oct 11, 2010, 10:26 AM

It seems you have a $modx->setLogTarget(’ECHO’) call somewhere, that’s causing your log messages to be ECHO’ed rather than output to core/cache/logs/error.log.

I’m getting the same. It seems that the current getResources snippet has a setLogTarget(’ECHO’) in it. Grrr.

You can remove this manually for now, and I’ll get the snippet updated today.

Good to know that its just getResources and not a core thing. Thanks for checking it.