[MTOS-dev] MT 4.15 Beta now available

[Byrne Reese]

It can. That is what the key attribute it for so that you can define what
properties a module hinges on WRT caching.

I believe this is discussed in the documentation.

On 4/7/08 8:59 AM, "Reed A. Cartwright" <reed at scit.us> wrote:

> Byrne Reese wrote:
>> http://www.movabletype.org/2008/04/movable_type_415_beta_1_now_av.html
> 
> A new plugin that I'm working towards requires a lot of template module
> work, to provide maximum flexibility to endusers.  However, to avoid
> adding six templates, I was thinking of using one template that would
> use an argument to determine which sub template would get saved, e.g.
> 
> <mt:Include module="Xomment" xmode="quote"/>
> 
> <mt:Include module="Xomment" xmode="panel"/>
> 
> Then in the template I'd do something like so:
> 
> <mt:If name="xmode" eq="quote">
> Quote
> <mt:else name="xmode" eq "panel">
> Panel
> <mt:else>
> Unknown option
> </mt:if>
> 
> So will caching interfere with this or does module caching understand
> different variables passed to the include command?
> 
> If not, it should be an option.