[TxMt] bug in smarty module

[Allan Odgaard]

On 27. Oct 2006, at 00:22, Rick Gigger wrote:

>> [...]
>> Then change that last disabled to ‘= 0’ or remove it.
> Thanks!  That worked great!  Is there any reason it's disabled by  
> default?  Any plans to make that sort of thing more user friendly  
> in the future?

Yes, having { start embedding of smarty code gives a hell of a lot  
false positives for people who e.g. have code listings in their HTML.

As for the future: with scope injection this will just be installing/ 
enabling the Smarty bundle, and then it will magically work all the  
places where HTML is allowed -- though with some new attributes in  
the scope, it will be possible to limit it to only HTML files with a  
given extension, for certain projects, etc.

That said, changing ‘disabled = 0;’ to ‘disabled = 1;’ is not exactly  
rocket science, just requires to RTFM ;)