We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27106
    • 147 Posts
    Any resolution on this?
      David Walker
      Principal, Shorewalker DMS
      Phone: 03 8899 7790
      Mobile: 0407 133 020
      • 12512
      • 42 Posts
      I also stumbled over the fact that the template must contain [[*content]] if a template is used.

      The only reason for using templates with static resource is to attach additional data to the resource for example tags or keywords. In that case a lot of errors like described here could be avoided if the template content is ignored for static resources. Just a suggestion.
        • 9207 ☆ A M B ☆
        • 2,475 Posts
        If you use a template for a static resource (or for a weblink), the template isn’t used for formatting really, it’s used as a container for the custom fields (i.e. Template Variables). This is a bit awkward... it’s another area where being able to define "Resource Types" would make for a more sensible UX (see this post http://modxcms.com/forums/index.php/topic,61312.0/all.html).
          • 22303 MODX Staff
          • 10,725 Posts
          You can construct Static Resources with Template Variables and any other MODX Elements. This is different than allowing these so-called "Resource Types" (we already have the ability to extend the Resource class) which is more about being able to attach pre-defined "Sets" of Elements directly to a Resource. This is already on the Road Map for a future release, and was planned in the original prototype.