I've supported bricolage for a while now and started out
using phpBB
as our article comment system.
We ended up creating a custom comment system using PHP. It
mimics blog comments.
Comments show up below article content + input form
Works well with Bricolage....! just include a little code
into your
article template and autohandler.
The comments are not "static", but can be cached
using memcache or a
file caching approach.
I've talked with my client and he's okay with me releasing
the code.
I've started on the process of cleaning it up and some
refactoring.
if interested let me know...
On Nov 12, 2007 11:01 AM, Phillip Smith <phillip communitybandwidth.ca> wrote:
>
> Just wanted to add some more options to this thread
about adding
> comments and/or forums to a Bricoalge-powered site.
>
> Two "Web 2.0" services recently reached their
public beta:
>
> For feature-rich threaded and ranked comments:
> http://intensedebate.com
>
> And for comments that are also a discussion forum:
> http://www.disqus.com
>
> Either of these would plug-in nicely to a
static-HTML-based site and
> provide sophisticated comment functionality. And I've
confirmed with
> the developers that both will continue to be free (as
in beer) for
> the baseline functionality.
>
> Now, of course, if there was a little free and
open-source
> application that did that ... that would be even
cooler. 
>
> However, the *really* interesting thing that is
(clearly) coming down
> the pipe is the idea of a commenter having a single
identity across
> many sites. Not a new idea, but one that appears
feasible now as
> standards like OpenID come into sight. I'm sure if we
wait long
> enough Google will figure it out for us...
>
> Best,
>
> Phillip.
>
> P.S. I should add that a number of high-volume sites
that use
> proprietary publishing systems that are similar to
Bricolage -- e.g.,
> static-page-based -- are going a similar route via a
commercial
> offering by Pluck: http://ww
w.pluck.com/products/sitelife.html
>
>
>
>
> On Oct 24, 2007, at 12:37 PM, Schults, Chris wrote:
>
> > <snip>
> > In the first version of http://thetyee.ca (March 2005)
the vBulletin
> > integration with bricolage generate story
templates was done very
> > hastily and on a tiny budget so there may have
been room for
> > improvement
> > that never got explored. How it worked was all
bricolage generated
> > stories were interpreted as php by the apache
server, and they
> > included
> > all the variables required by vBulletin to
dynamically call the proper
> > comment thread from vBulletin mysql database. One
of the hacks to the
> > vBulletin database we did was to map bricolage
story IDs to vBullletin
> > thread IDs. This mapping occurred dynamically the
first time a
> > story was
> > published.
> > </snip>
> >
> > When I was at Grist, and with the help of David
and Scoop's Colin
> > Hill,
> > we did something similar using Scoop <http://scoop.kuro5hin.
org/>,
> > which
> > Grist was already using for blogging. Stories had
a data element field
> > for the comment thread ID. At publish time,
Bricolage would
> > dynamically
> > create a dummy Scoop post by assigning a comment
ID, and inserting it
> > and other relevant information (title,
description, etc) into the
> > Scoop
> > comments table. That thread would then be included
in the Bricolage
> > story via Perl embedded in the story's HTML. (I
would have
> > preferred to
> > use a SSI, but Scoop is under a different document
root and is
> > dynamic.)
> > It was tricky accommodating user log-in and
redirection, but we
> > overcame
> > those challenges.
>
>
> --
> Phillip Smith,
> Simplifier of Technology
> Community Bandwidth
>
>
>
|