Comments on: Anatomy of a Movable Type Template http://www.devlounge.net/code/anatomy-of-a-movable-type-template Design, Develop, and Grow Wed, 08 Feb 2012 09:03:06 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: NETTUTS - Web development tutorials and links - Best of the Web - April http://www.devlounge.net/code/anatomy-of-a-movable-type-template/comment-page-1#comment-145121 NETTUTS - Web development tutorials and links - Best of the Web - April Thu, 01 May 2008 02:43:18 +0000 http://www.devlounge.net/articles/anatomy-of-a-movable-type-template#comment-145121 [...] DevLounge brought us not one but two useful MT tutorials with the introduction and also Anatomy of a Movable Type Template [...] [...] DevLounge brought us not one but two useful MT tutorials with the introduction and also Anatomy of a Movable Type Template [...]

]]> By: BillyMabray http://www.devlounge.net/code/anatomy-of-a-movable-type-template/comment-page-1#comment-144834 BillyMabray Fri, 25 Apr 2008 13:50:24 +0000 http://www.devlounge.net/articles/anatomy-of-a-movable-type-template#comment-144834 Ok, so I tried it. I created a second "rsd" template and rebuilt the main index. MTLink continued to link to the original rsd template. When I changed the original to a Custom Index Template, then it started linking to my new rsd template. My guess is when you use the template identifier, MTLink links to the first template of that type that it finds. Ok, so I tried it. I created a second “rsd” template and rebuilt the main index. MTLink continued to link to the original rsd template. When I changed the original to a Custom Index Template, then it started linking to my new rsd template. My guess is when you use the template identifier, MTLink links to the first template of that type that it finds.

]]> By: BillyMabray http://www.devlounge.net/code/anatomy-of-a-movable-type-template/comment-page-1#comment-144831 BillyMabray Fri, 25 Apr 2008 13:34:22 +0000 http://www.devlounge.net/articles/anatomy-of-a-movable-type-template#comment-144831 Thanks, Su, that's good to know. It's interesting that the default Main Index template uses a template identifier, but only the template name is mentioned in the official documentation. And since template identifier corresponds to the index template type, I wonder what MTLink would link to if you created a second "archive_template" template? I'll have to try that. Thanks, Su, that’s good to know. It’s interesting that the default Main Index template uses a template identifier, but only the template name is mentioned in the official documentation.

And since template identifier corresponds to the index template type, I wonder what MTLink would link to if you created a second “archive_template” template? I’ll have to try that.

]]> By: Su http://www.devlounge.net/code/anatomy-of-a-movable-type-template/comment-page-1#comment-144802 Su Fri, 25 Apr 2008 05:10:07 +0000 http://www.devlounge.net/articles/anatomy-of-a-movable-type-template#comment-144802 <i> will output the URL for any template [...] generated by your blog</i> This bears a little expansion. The Link tag's <code>template</code> argument will accept either a template identifer, or template name, and will attempt them in that order. Your code sample is linking to an index template with identifier of "archive_template", which in the defaults happens to have the <em>name</em> "Archive Index." Linking to the identifier is generally going to be preferable, since it will remain constant if the template is renamed. The caveat is that custom index templates created through the application don't currently allow you to specify an identifier, in which case your only option is to link via name. will output the URL for any template [...] generated by your blog

This bears a little expansion.
The Link tag’s template argument will accept either a template identifer, or template name, and will attempt them in that order. Your code sample is linking to an index template with identifier of “archive_template”, which in the defaults happens to have the name “Archive Index.”

Linking to the identifier is generally going to be preferable, since it will remain constant if the template is renamed. The caveat is that custom index templates created through the application don’t currently allow you to specify an identifier, in which case your only option is to link via name.

]]>