Hello drone,

For if to work, an extension had to be installed, the parser one. It caused some bugs that had to be ironed out.

It should work now. There's just this potential problem:
If you find some template responses are being unexpectedly wrapped in <pre></pre>

I saw this problem in 1.6.10 using the workarounds here and worked around it by making sure all results from ParserFunction callbacks were trimmed. If a result had a leading space character, then that portion of the template would be wrapped in pre tags. Couldn't figure out what part of the parser was doing this. But force trimming might be a potential workaround based on your needs.


The #time function is disabled for now.

Feedback please?