At a recent conference, there’s mention that the new version of MT coming out will have dynamic templates – this is a good thing. However, will have to figure out if I’ll still be able to use MT-Amazon in entries – this may not be possible or prudent with the new version. Need to find out more, as I’m in the habit of doing Amazon tags on the fly, rather than in static content.
About breaking plugins, they’ve chosen this route because for some plugins it is ridiculous to expect them to work in dynamic templates. He gave me the example of MT-Amazon – a plugin that queries Amazon depending on variables passed in the template. If you put that into a dynamic template it would be the equivalent of performing a DoS attack on Amazon – it would be querying Amazon on a per-page basis ! So plugins like that would be used still in static publishing, which you can still use, again on a per-template basis. a separate template could build to physical, static files and then you could include that using a MTInclude tag in the dynamic template.
