radiant-comments

22 views
Skip to first unread message

C. R. Oldham

unread,
Aug 14, 2009, 6:11:21 PM8/14/09
to radiant...@googlegroups.com
Greetings,

I'm having some trouble with seancribbs fork of radiant-comments. I'm
running 0.8.0, and I keep getting

TypeError in Admin/commentsController#unapprove
can't dup NilClass
Whenever I approve or unapprove a comment. I'm using (or trying to
use) Akismet for spam protection. Any idea what I'm doing wrong?

Thanks.
--cro

Jim Gay

unread,
Aug 14, 2009, 6:33:36 PM8/14/09
to radiant...@googlegroups.com
Sean is actively working on that fork, so it may be in flux.
Have you tried the artofmission repository?
git://github.com/artofmission/radiant-comments.git

cro

unread,
Aug 15, 2009, 6:36:25 PM8/15/09
to Radiant CMS: Dev


On Aug 14, 4:33 pm, Jim Gay <j...@saturnflyer.com> wrote:
> Sean is actively working on that fork, so it may be in flux.
> Have you tried the artofmission repository?
> git://github.com/artofmission/radiant-comments.git

Now I get

NameError in CommentsController#create
uninitialized constant Comment::Sanitize

even with the Sanitize gem installed.

--cro

cro

unread,
Aug 15, 2009, 6:40:32 PM8/15/09
to Radiant CMS: Dev


On Aug 15, 4:36 pm, cro <oldha...@gmail.com> wrote:
> NameError in CommentsController#create
> uninitialized constant Comment::Sanitize
>
> even with the Sanitize gem installed.


Adding

require 'sanitize'

to comments/app/models/comment.rb

fixed this. Was that the right thing to do?

--cro

Jim Gay

unread,
Aug 15, 2009, 10:22:42 PM8/15/09
to radiant...@googlegroups.com

I'm working on this right now, but you should put:

config.gem "sanitize"

in your environment.rb

The next version of Radiant (or edge right now) allows extensions to
add their own configuration options without requiring you to do this.

Reply all
Reply to author
Forward
0 new messages