[consulting] to fix a major limitation of Drupal design

George Por George at Community-Intelligence.com
Sun Aug 26 23:12:55 UTC 2007


> Dear Greg and Sime, thanx to both of you for pointing to
> http://drupal.org/project/nodecomment module.
> 
> Dear Sami Khan and William, thank you too for the help you offered. If we run
> into trouble with the nodecomment module, I may still come back to you.
> 
> warm regards to all drupalistas on this great list!
> 
> george
>  
> -
>  
>  
> 
> 
> From: consulting-bounces at drupal.org [mailto:consulting-bounces at drupal.org] On
> Behalf Of William Smith
> Sent: Sunday, August 26, 2007 2:49 PM
> To: A list for Drupal consultants and Drupal service/hosting providers
> Subject: Re: [consulting] to fix a major limitation of Drupal design
>  
> The issue isn't so much that it can't be done, it is that it isn't likely to
> happen in core anytime soon.  This is one of the great never-ending debates in
> the Drupal community -- should comments be nodes, or not?  It gets heated, and
> it has played out many times.
> 
> If you want the ability to apply taxonomy terms to comments on your particular
> site, it can certainly be done, and money can certainly buy it.  If you need a
> developer, I may have some available time later this week as I wrap a couple
> of projects up. 
> 
> All the best,
> William
> 
> On 8/26/07, George Por <George at community-intelligence.com> wrote:
> 
> This is message is to those brave souls who think that something can be done
> to fix a major limitation of Drupal design.
> 
> I am talking about the fact that only nodes can have categories and tags but
> not comments. That means that a forum topic opener and blog can have them
> individual blog entries and topic replies not, makes those key modules largely
> useless from the perspective of growing the a group's capacity for
> collaborative meaning making.
> 
> I talked with many programmers and they all said that adding rags to comment
> cannot be done in Drupal because of its architecture. Is it really so? No
> amount of money could buy developer time to fix that? If any of you have a
> serious proposal, we would consider it.
> 
> When we used Drupal 4.6. And 4.7, we got that problem partially resolved by
> using flexinode to mimick a blog, and then we could add tags to the entries.
> However, we moved to 5.1 and, to my knowledge, flexinode doesn't work there.
> Can that be changed?
> 
> Another workaround would be to use Moveable Type or another dedicated blog
> software and link the MT blogs fom our Drupal-based home page. However, in
> that case we would loose the handiness of one search command working on all
> content types at once. Any work around that?
> 
> Best regards,
> 
> george 
> 
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting
>  
> 
> 
> _______________________________________________
> consulting mailing list
> consulting at drupal.org
> http://lists.drupal.org/mailman/listinfo/consulting


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/consulting/attachments/20070827/215f2cda/attachment.htm 


More information about the consulting mailing list