[consulting] to fix a major limitation of Drupal design

[Mariano Barcia]

George,

We didn't conduct an evaluation in deep, but I'm afraid
nodecomment.moduledoesn't replace
comment.module to the full extent (at least, we couldn't get comment
notifications at that time). But to be honest, I have not looked at the
code, perhaps it does (!). I guess we need a more accurate information from
the module's maintainers here...

--mariano


On 8/27/07, George Por <George at community-intelligence.com> wrote:
>
>  >  nodecomment helps a lot, although IMO it should provide a wrapper to
> let other modules (like comment_notify) do their work seamlessly (like
> category does with taxonomy).
>
> Mariano, does it mean that if we install nodecomment, we would have
> problem with getting email alert on new comments?
> george
>
>
> 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
>
>
>
> _______________________________________________
> 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/69c8333e/attachment-0001.htm