If in a template with a {capture} block e.g. a TypError occurs within the content of the block, a misleading error message Not matching {capture}{/capture} in 'file:menuitem.tpl' is created with a backtrace like this:
It takes some time to realize what really happens and strip the {capture} to get the actual error.
I don't know if it is technically possible, but if yes, wouldn't it be far better to just pass the error (or at least the message) along so the real problem can be identified?
If in a template with a
{capture}
block e.g. a TypError occurs within the content of the block, a misleading error messageNot matching {capture}{/capture} in 'file:menuitem.tpl'
is created with a backtrace like this:It takes some time to realize what really happens and strip the
{capture}
to get the actual error. I don't know if it is technically possible, but if yes, wouldn't it be far better to just pass the error (or at least the message) along so the real problem can be identified?