[development] Content templating in Drupal?

Samuel Lampa (Beginner) samuel.lampa at rilnet.com
Wed Aug 16 19:23:29 UTC 2006


This is hot stuff, so I make this a new thread (Or trying to...)

With just some additional functionality this module could increase the 
usefulness of Drupal CMS by many factors. Namely the possibility to 
insert the content from one node into another, in combination with the 
possibility to pass parameters through the call, also for page content 
(i.e. using the called-for node as a template.). This exact feature is 
what makes MediaWiki beat Drupal for some needs (while it still lacks 
some other indispensable features...). You can read more in detail what 
I mean in the post by Rolf here: 
http://drupal.org/node/52816#comment-99961 
<http://sv.rilbible.org/wiki/index.php/1_Mos_1>

Would this be possible to implement into this module? I think including 
it into a module of this kind might be a more generic solution also, 
than packing it together with a wiki module pack. Actually it would be 
great to see something like this in the core some day?

Regards
Samuel Lampa, RIL Partner AB, www.rilnet.com


Mark Howell wrote:
> I wrote the Attached Node module a while back:
> http://drupal.org/node/11988
>
> It basically uses filters to substitute [node:123] with the contents 
> of the node.  It also has image-specific code (for Drupal 4.5) that 
> allows for manipulation of the rendering:
>
>      [node:123,res="640x480"]
>      [node:123,res="original",title="Original version of the picture"]
>
> A coworker wrote a custom UI in my project to insert the node tag 
> content from a select list, but others feel comfortable just typing 
> these tags in directly.
> This code has not been touched in 20 months.  Feel free to update it 
> to Drupal 4.6 or 4.7.
>
> -Mark
>
> Carl Mc Dade wrote:
>
>> Yes, I have decided to use an association table and nodeapi. I'm a 
>> bit hung though because I forgot to ask for a complete business 
>> model. I am unsure about "whom" is going to be the end user of such a 
>> capability, bloggers? admin? forum moderators? Or should it be open 
>> to all and subject to moderation. Once I get these out of the way 
>> then I will start in.
>>
>> I appreciate all the input and you can keep it coming. But the one 
>> thing that is missing in the responses is the main question. 
>> Frequently after someone tries to make a contribution they are 
>> stopped because their project is similar or the same as another 
>> ongoing project. To avoid this collision I thought to ask if anyone 
>> has a project that is even remotely like this?
>>
>>
>> */Suuch Solutions <drupal at suuch.com>/* wrote:
>>
>>     I've done something similar that essentially redirects all
>>     comments to a non-forum node to an assigned forum node. Yes, it's
>>     a matter of hook_nodeapi, a table to keep track of associations,
>>     and hook_link. Post count ( e.g. 1 comment, 2 comments) is already
>>     handled by the comment.module once you know the associated forum
>>     topic nid.
>>          I can send you code snippets if this description is not enough.
>>     paa.kwesi
>>          On 12/08/06, *Jeff Eaton* <jeff at viapositiva.net
>>     <mailto:jeff at viapositiva.net>> wrote:
>>
>>         A site I've been working on has almost *exactly* the same
>>         requirement. It's still in development, so the code doesn't
>>         exist yet (urgh), but our conclusion was:
>>                  Use nodeapi's insert $op to intercept new blog 
>> posts. When
>>         they're saved, programmatically create a forum post with the
>>         blog post's teaser and a link pointing to the 'full' blog
>>         entry. In nodapi's 'view' $op, add a link at the bottom of the
>>         blog post to 'discuss this post' that points to the forum
>>         topic in question. It would work best when blog posts have
>>         comments disabled; that way there's only one place to discuss
>>         a given blog post. The end result is that blog posts point to
>>         the forum for discussion. It would probably work best if there
>>         was a dedicated forum category for those types of posts.
>>                  I'm not sure if that's helpful, but it's the flow we 
>> came up
>>         with. There's some sample code for programmatically creating
>>         forum nodes in the 'devel' module's generate-content.php
>>         script. It handles the proper linking of taxonomies and
>>         updating of post counts, etc.
>>                  --Jeff
>>
>>             -----Original Message-----
>>             *From:* Carl Mc Dade [mailto: carl_mcdade at yahoo.com
>>             <mailto:carl_mcdade at yahoo.com>]
>>             *Sent:* Saturday, August 12, 2006 11:29 AM
>>             *To:* development at drupal.org <mailto:development at drupal.org>
>>             *Subject:* Re: [development] Nodes content within nodes
>>             solution developement?
>>
>>             That type of solution is a bit too complicated to set up
>>             and administrate.
>>
>>             What we are looking at is a integration of two types of
>>             community user. The blogger and the forum user. A blogger
>>             consistently writes on topics but may not do so in a way
>>             that it sparks a forum. They may be just blah blahing. But
>>             sometimes they may blog on a topic that fits in with a
>>             Forum category. In this case we would like the user to be
>>             able to take a blog and insert it inline into the first
>>             post. This is so that comments and replies land in the
>>             right venue. Also the blogger or site administrator does
>>             not have moderate blog comments and replies this is left
>>             up to the moderators of the Forum.
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>
>
>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20060816/17506e09/attachment-0001.htm


More information about the development mailing list