Hello!
I'm having issues with the Comments extensions. When adding the
snippet comment to my layout I get this error message:
undefined method `author_url’ for nil:NilClass
undefined method `author’ for nil:NilClass
undefined method `author_url’ for nil:NilClass
said on
undefined method
Hello all,
I'm currently using the comments extension and am looking at enabling the email
notifications.
When I add an email address through the settings extension for the
comments.notification_to setting I get an SMTP syntax error when submitting a
comment, yet when I hardcode the
This is unrelated to the comments extension.
If you have a snippet which is filtered with Markdown (or Textile or
some other) and it includes one that, for example, has some
non-Markdown text with spaces on a line before some HTML or text
begins, the parsing of the parent snippet (the one with
Hi Jim, that's what I figured and so in order to have Markdown filter
it as raw HTML I will have to create my own snippet as I thought. Per
http://daringfireball.net/projects/markdown/syntax#html it seems the
only why Markdown will utilize it as 'Inline HTML' is if there's a a
line between the
Wondering what to do to get comments extension to work. When I run the
./script/server -e [production|development] and go to the extensions
tab in Admin I see the comments extension and also, a “Comments” tab
showed up on the right of Admin. But I still got the following error
when I click on it:
Looks like you're missing the will_paginate gem. Try gem install
will_paginate, or grab it from http://github.com/mislav/will_paginate
Alex
On Mon, Nov 16, 2009 at 9:58 PM, Rob Levin roblevinten...@gmail.com wrote:
Wondering what to do to get comments extension to work. When I run the
I thought this was it:
mislav-will_paginate (2.3.11)
(as listed in my gem local listing). No?
On Mon, Nov 16, 2009 at 7:04 PM, Alexander Wallace
alexmlwall...@gmail.com wrote:
Looks like you're missing the will_paginate gem. Try gem install
will_paginate, or grab it from
Saw that a second after I click send, oops. Try installing it as a plugin,
or directly installing the will_paginate gem (as opposed to the github
version, mine is simply listed as will_paginate (2.2.2)...
Try out these steps on script/console as well- should let you know if the
gem is being
edit your config/environment.rb to have:
config.gem 'mislav-will_paginate', :lib = 'will_paginate'
I think that should do it.
On Mon, Nov 16, 2009 at 10:11 PM, Alexander Wallace
alexmlwall...@gmail.com wrote:
Saw that a second after I click send, oops. Try installing it as a plugin,
or
Hi,
We're about to start doing our own work on the comments extension, does anyone
have a good roadmap for what is being done and where it's going?
Bernard Yu
EnguinDesign.com
202.569.8116
___
Radiant mailing list
Post: Radiant@radiantcms.org
Hi Jim,
That worked - thanks! So I can't depend on the system gem?
On Mon, Nov 16, 2009 at 7:36 PM, Jim Gay j...@saturnflyer.com wrote:
edit your config/environment.rb to have:
config.gem 'mislav-will_paginate', :lib = 'will_paginate'
I think that should do it.
On Mon, Nov 16, 2009 at
On Mon, Nov 16, 2009 at 10:49 PM, Bernard Yu berna...@enguin.com wrote:
Hi,
We're about to start doing our own work on the comments extension, does
anyone have a good roadmap for what is being done and where it's going?
Bernard Yu
EnguinDesign.com
202.569.8116
I'm currently maintaining it
You can; that's what you are doing.
You have to tell Rails to load the mislav-will_paginate gem and
recognize it as will_paginate.
On Mon, Nov 16, 2009 at 10:58 PM, Rob Levin roblevinten...@gmail.com wrote:
Hi Jim,
That worked - thanks! So I can't depend on the system gem?
On Mon, Nov 16,
Got it Jim. Thanks.
One other question. If I have a Markdown filtered page and I want to
insert comment snippets like: r:snippet name=comment_form/ using
the default snippets, it shows up as preformatted text. Is there a
workaround that I can make it actually show a form within a Markdown
page or
Hi,
Firstly thanks to all those who developed this extension, it seems
like quite a roll call.
Is this feature supported? I can see in TODO a note about stating that
something similar is pending, but a quick glance through the code
suggests it is in place.
If it isn't implemented is it
you can set `Radiant::Config['comments.auto_approve'] = true` through
the console, your environment or the settings extension and it will
auto-approve comments.
On Thu, Aug 13, 2009 at 12:02 PM, subsor...@gmail.com wrote:
Hi,
Firstly thanks to all those who developed this extension, it seems
That seems to work great, thanks for the super quick reply. Is this
compatible with the aski/mollum spam filtering?
2009/8/13 john muhl johnm...@gmail.com
you can set `Radiant::Config['comments.auto_approve'] = true` through
the console, your environment or the settings extension and it will
Yes. Although I use neither.
I was working hard on cleaning up the code a while ago but had to put
it aside. I'll be doing more work on the codebase to make things
clearer, and word on the street is that Sean Cribbs may be updating
the Comments extension with some other stuff too.
If you have any
This is a bug in the extension.
It submits comments to the_page_url/comments and sets up routes to
catch that and send it to the comments controller.
We'll need to make an exception for the home page and perhaps create a
custom route for it.
Are you really accepting comments on your home
The home comments was only for test, the blog comments works fine now! =]
One more doubt, how can I turn the comments moderated? For show in page only
after approved?
Thanks Jim, helped me a lot!
On Thu, May 14, 2009 at 5:29 PM, Jim Gay j...@saturnflyer.com wrote:
This is a bug in the
I saw the code and I think that, to make the comments unapproved for
default, the way is to comment the line seven of comment.rb model:
#before_save :auto_approve
Can someone tells me if this is the best way?
Thanks,
Rafael Souza
On Thu, May 14, 2009 at 6:15 PM, Rafael Souza raf...@maisweb.org
There is no error and it does not show up in the comments tab waiting
for approval. When I clicked on save comment my browser pulls up me
http://localhost:3000/comments, however since I have not added any
content to that page it comes up blank. I'm guessing there is
something that needs to be
Bryce Klimoski wrote:
There is no error and it does not show up in the comments tab waiting
for approval. When I clicked on save comment my browser pulls up me
http://localhost:3000/comments, however since I have not added any
content to that page it comes up blank. I'm guessing there is
Thanks for the link I'll take a closer look at it when I get home from work.
On Mon, Mar 2, 2009 at 8:23 AM, Mohit Sindhwani t...@onghu.com wrote:
Bryce Klimoski wrote:
There is no error and it does not show up in the comments tab waiting
for approval. When I clicked on save comment my
Bryce Klimoski wrote:
I'm new to Radiant andlike what I see however I'm struggling with
getting the comments extension working. First things first here are
some version info.
Radian 0.7.1
Comments Extenstion URL - git://github.com/artofmission/radiant-comments.git
fastercsv 1.4.0
I ran both the update and migrate tasks..
rake radiant:extensions:comments:update
rake radiant:extensions:comments:migrate
I did not see an error occur with either one of them.
I also took a look at the url you sent earlier
http://wiki.radiantcms.org/Using_Radiant_as_a_Blog and the only thing I
I'm new to Radiant andlike what I see however I'm struggling with
getting the comments extension working. First things first here are
some version info.
Radian 0.7.1
Comments Extenstion URL - git://github.com/artofmission/radiant-comments.git
fastercsv 1.4.0
mislav-will_paginate 2.3.7
Getting
What did happen when you submitted the comment? Did you get an error?
Typical, it will show your comment and say that it's awaiting
approval. In the comments tab in the admin you can then see and
approve the comment. In your case it's a little unclear what you did
or what results you
Jim Gay wrote:
Have you run rake db:bootstrap yet?
The first error says 'relation config does not exist' meaning the
config table does not exist (which would be the case if you hadn't run
the bootstrap)
Dear Jim:
Thanks for your reply!
I didn't run rake db:bootstrap because I was
Try the version from my fork:
git://github.com/seancribbs/radiant-comments.git
It is updated to work with 0.7.
Sean
P.S. Extension developers - don't set Radiant::Config values without
checking for existence of the table! Your activate methods run on
initialization, whether the DB is
Sean Cribbs wrote:
Try the version from my fork:
git://github.com/seancribbs/radiant-comments.git
It is updated to work with 0.7.
Sean
Thanks for the fix, Sean. Do I still need to install the fork if almost
everything is now working properly?
Here's what's still failing: Clicking
One of my tasks for tomorrow is to introduce a module that will contain
all of the legacy routes and their new equivalents. This will be
automatically included in the application helper and controller so the
old routes will work.
Sean
James Lavin wrote:
Sean Cribbs wrote:
Try the
Hi:
New to blogging, I installed Radiant on Tuesday. I'm running 0.7.0-rc2
(http://radiantcms.org/blog/archives/2009/01/21/radiant-0-7-0-rc2-available/)
with Postgres on Ubuntu Hardy. The basic site is up and running without
a glitch.
But when I tried to install radiant-comments-extension, I got
. I'm running 0.7.0-rc2
(http://radiantcms.org/blog/archives/2009/01/21/radiant-0-7-0-rc2-available/
)
with Postgres on Ubuntu Hardy. The basic site is up and running
without
a glitch.
But when I tried to install radiant-comments-extension, I got the
error
below. Any thoughts would sure
Once a page has comments there is a link in the admin of that page to
view comments and if I click on it I get an application error. This
is what the production log says:
Parameters: {action=index, page_id=5, controller=admin/
comments}
Cookie set:
Comments may not have been updated for Radiant 0.7 (which did not
preserve named routes from earlier versions)
I believe it should be edit_admin_page_url now, assuming you are on
edge Radiant.
On Jan 30, 2009, at 8:06 PM, Steven Southard wrote:
Once a page has comments there is a link in
Thank you Jim. I bet you're right.
Steven
On Jan 30, 2009, at 8:07 PM, Jim Gay wrote:
Comments may not have been updated for Radiant 0.7 (which did not
preserve named routes from earlier versions)
I believe it should be edit_admin_page_url now, assuming you are on
edge Radiant.
On
Hi Everyone
Any ideas?
Cheers,
Mohit.
Mohit Sindhwani wrote:
I'm just starting to use the comments extension and I followed the
instructions that ere there in messages here and there and it works
fine. (I'm going to compile it for Summer Reboot soon).
There is just one thing that comes
Hi Sean
Sean Cribbs wrote:
Mohit,
My apologies for not responding sooner.
The apology is not needed at all :)
This is something I'd like to address sooner rather than later, and do
it in a way that is similar to what I did to the mailer extension --
supporting post-backs to the page
Hi,
I'm trying to use the comments extension found at:
http://github.com/artofmission/radiant-comments/tree/master
I'm following the README at:
http://github.com/artofmission/radiant-comments/tree/master/README.rdoc
and it seems everything works except one thing:
When posting a new comment
Gert,
That looks like a bug in the extension. They'll need to manually set
the request on the page to fix that issue. e.g.
@page.request = request
@page.render
Sean
Gert Jørgensen wrote:
Hi,
I'm trying to use the comments extension found at:
This is a bug in 0.6.7 that occurs when run in development mode. If
you run it in production mode it will go away, or if you freeze to the
edge that should also take care of it.
On Jul 14, 2008, at 7:00 AM, Josh Schairbaum wrote:
I've just installed the Comments Extension into a new Radiant
Embarrassing for me. I've subscribed to this mailing list for several
months now and seen people talk about this known bug, but never read
them since I didn't have an issue. Lesson learned by me, then.
Thanks Jim.
Regards,
Josh
On Jul 14, 2008, at 7:12 AM, Jim Gay wrote:
This is a bug
43 matches
Mail list logo
