issue_comments: 1379495504

A few options: - Ensure that the explicit template context overrides anything that plugins might do - so in this case the sql(...) function would not be available on that page. This would break people who have custom templates that use that function though. - Encourage naming conventions where functions and variables from plugins are less likely to interfere with existing functionality. - Completely change how templates work, so you never have a variable called {{ sql }} - it is always accessed via some parent object instead, such as {{ page.sql }}.

That last option actually fits quite well with my efforts to unify template rendering with JSON (and JSON extras) so it might be the best way to address this.