Comments on: Skeletons! http://ken.therickards.com/2007/06/17/skeletons/ Ken Rickard's notes about what he's doing Wed, 20 Aug 2008 16:45:15 +0000 http://wordpress.org/?v=2.0.10 by: Ken Rickard http://ken.therickards.com/2007/06/17/skeletons/#comment-20491 Mon, 18 Jun 2007 14:57:11 +0000 http://ken.therickards.com/2007/06/17/skeletons/#comment-20491 @Wim: Wow. Never even saw Node Template. I even asked on the development list if such a module existed, and no one responded. [Sigh -- I will test that module after I get back from vacation.] A very brief look suggests slightly different use-cases and workflow. Node Template seems to work with previously published content. Skeleton lets you create template nodes that aren't published nodes -- they are just stored node data structures. I suspect the two modules might merge pretty well, as I already thought about adding a "make template" tab to other nodes. @Gunnar: I've used cck_field_perms (I like it) -- it sets the perms as Access Control rules, so its usage sits outside what Skeleton (and Node Template) does. It could indeed be used to create default data that can only be edited by certain roles. @Wim: Wow. Never even saw Node Template. I even asked on the development list if such a module existed, and no one responded. [Sigh — I will test that module after I get back from vacation.]

A very brief look suggests slightly different use-cases and workflow. Node Template seems to work with previously published content. Skeleton lets you create template nodes that aren’t published nodes — they are just stored node data structures. I suspect the two modules might merge pretty well, as I already thought about adding a “make template” tab to other nodes.

@Gunnar: I’ve used cck_field_perms (I like it) — it sets the perms as Access Control rules, so its usage sits outside what Skeleton (and Node Template) does. It could indeed be used to create default data that can only be edited by certain roles.

]]> by: Wim Mostrey http://ken.therickards.com/2007/06/17/skeletons/#comment-20479 Mon, 18 Jun 2007 11:19:48 +0000 http://ken.therickards.com/2007/06/17/skeletons/#comment-20479 Indeed, the cck_field_perms allows you to do this so user could use the template, and force them to keep certain default values. Indeed, the cck_field_perms allows you to do this so user could use the template, and force them to keep certain default values.

]]> by: Gunnar Langemark http://ken.therickards.com/2007/06/17/skeletons/#comment-20467 Mon, 18 Jun 2007 10:06:54 +0000 http://ken.therickards.com/2007/06/17/skeletons/#comment-20467 AFAIK there's a module controlling access rights to fields in CCK node types. Would that be useful? With node templates - I think it could be done with existing modules. AFAIK there’s a module controlling access rights to fields in CCK node types. Would that be useful? With node templates - I think it could be done with existing modules.

]]> by: Wim Mostrey http://ken.therickards.com/2007/06/17/skeletons/#comment-20466 Mon, 18 Jun 2007 09:42:37 +0000 http://ken.therickards.com/2007/06/17/skeletons/#comment-20466 You should check out the node_template module (http://drupal.org/project/node_template). It already provides the option to store a complete book (as well as any node by itself) as a template and the ability to re-use it. Isn't that exactly what Skeletons does as well? You should check out the node_template module (http://drupal.org/project/node_template). It already provides the option to store a complete book (as well as any node by itself) as a template and the ability to re-use it. Isn’t that exactly what Skeletons does as well?

]]>