Feedback Plugin Death

prothall81 wrote:
> I'm hosted on nearlyfreespeech.net and running Blosxom 2.0.1.
> Everything works nicely and I know that the overall setup is correct
> after having checked, successfully, with the "test" plugin. However,
> if I add the feedback plugin (the version just released), I get a
> http server 500 error (premature end of script headers).
<snip&gt;
> Can't locate Net/Akismet.pm in INC
<snip>
&gt; Looks like a perl module is missing.

Right, the new version of feedback relies upon the Net::Akismet module
having been installed, in order to support Akismet spam checking.

> I'm not interested in using Akismet, so if I can just hack that
> section out, that'd be great. In any case, what can I do to fix this
> error?

Make sure Askismet support is turned off (lines 35 and 36):

my $akismet_comments = 0;
my $akismet_trackbacks = 0;

delete or comment out the invocation of matches_askimet in the is_spam
subroutine (line 1010):

return 1 if $akismet && matches_akismet($params_ref, $is_comment);

and delete or comment out the entire matches_akismet subroutine (lines
1048-1083).

Frank

P.S. Anticipating this problem, initially I tried to include the
Net::Akismet package in-line within the feedback plugin, like Kevin
Scaldeferri did with his version of writebackplus. However I experienced
problems, which I thought might have to do with the presence of a
___DATA___ section in the feedback plugin. (Kevin doesn't have such a
section in his plugin.) So I reverted to just referencing the
Net::Akismet package and requiring that it be installed. I suppose I
could include the equivalent functionality as a set of internal
subroutines (i.e., not in the form of a package), and if more people
have this problem I may do just that.

--
Frank Hecker
heckerhecker.org

On Jul 23, 2006, at 10:06 PM, Frank Hecker wrote:
&gt;
> P.S. Anticipating this problem, initially I tried to include the
> Net::Akismet package in-line within the feedback plugin, like Kevin
>; Scaldeferri did with his version of writebackplus. However I
> experienced
> problems, which I thought might have to do with the presence of a
> ___DATA___ section in the feedback plugin. (Kevin doesn't have such a
> section in his plugin.) So I reverted to just referencing the
> Net::Akismet package and requiring that it be installed. I suppose I
> could include the equivalent functionality as a set of internal
> subroutines (i.e., not in the form of a package), and if more people
&gt; have this problem I may do just that.
>;

I included Net::Akismet in my writeback version mostly because the
package on CPAN wouldn't install on anything before Perl 5.8.5. The
new version (0.02) shouldn't have this problem, so it isn't necessary
any more.

-kevin

Idea: release feedback and feedback-a(kismet). Probably the simplest
solution, with the downside that it can become confusing. -POLM

On Mon, 24 Jul 2006 10:06:55 +0500, Frank Hecker <heckerhecker.org> wrote:

> prothall81 wrote:
&gt;> I'm hosted on nearlyfreespeech.net and running Blosxom 2.0.1.
&gt;> Everything works nicely and I know that the overall setup is correct
&gt;> after having checked, successfully, with the "test" plugin. However,
>> if I add the feedback plugin (the version just released), I get a
>>; http server 500 error (premature end of script headers).
> <snip&gt;
>>; Can't locate Net/Akismet.pm in INC
> <snip&gt;
>>; Looks like a perl module is missing.
>
> Right, the new version of feedback relies upon the Net::Akismet module
&gt; having been installed, in order to support Akismet spam checking.
>
>> I'm not interested in using Akismet, so if I can just hack that
>> section out, that'd be great. In any case, what can I do to fix this
>> error?
&gt;
> Make sure Askismet support is turned off (lines 35 and 36):
>
> my $akismet_comments = 0;
> my $akismet_trackbacks = 0;
>
> delete or comment out the invocation of matches_askimet in the is_spam
&gt; subroutine (line 1010):
&gt;
> return 1 if $akismet && matches_akismet($params_ref, $is_comment);
>
> and delete or comment out the entire matches_akismet subroutine (lines
&gt; 1048-1083).
>
&gt; Frank
>;
> P.S. Anticipating this problem, initially I tried to include the
> Net::Akismet package in-line within the feedback plugin, like Kevin
>; Scaldeferri did with his version of writebackplus. However I experienced
> problems, which I thought might have to do with the presence of a
> ___DATA___ section in the feedback plugin. (Kevin doesn't have such a
> section in his plugin.) So I reverted to just referencing the
> Net::Akismet package and requiring that it be installed. I suppose I
> could include the equivalent functionality as a set of internal
> subroutines (i.e., not in the form of a package), and if more people
&gt; have this problem I may do just that.
>;

--
Remember always the last words of Pancho Villa:
&quot;Don't let it end like this. Tell them I said something."

2 3 S K I D D O O

Paul O'Leary McCann wrote:
&gt; Idea: release feedback and feedback-a(kismet). Probably the simplest
> solution, with the downside that it can become confusing. -POLM

Actually, though my Perl skills are not that great, after looking into
this question I think I can just use "require Net::Akismet" instead of
"use Net::Akismet" to postpone loading of the Akismet module
until/unless it's actually needed.

Frank

--
Frank Hecker
heckerhecker.org

On Jul 25, 2006, at 2:07 AM, Frank Hecker wrote:

> Paul O'Leary McCann wrote:
&gt;> Idea: release feedback and feedback-a(kismet). Probably the simplest
>> solution, with the downside that it can become confusing. -POLM
>;
> Actually, though my Perl skills are not that great, after looking into
> this question I think I can just use "require Net::Akismet" instead of
> "use Net::Akismet" to postpone loading of the Akismet module
&gt; until/unless it's actually needed.
&gt;

Yeah, that's what I would recommend.

-kevin

Kevin Scaldeferri wrote:
&gt; On Jul 25, 2006, at 2:07 AM, Frank Hecker wrote:
&lt;snip>
> > Actually, though my Perl skills are not that great, after looking into
> > this question I think I can just use "require Net::Akismet" instead of
> > "use Net::Akismet" to postpone loading of the Akismet module
&gt; > until/unless it's actually needed.
&gt;
> Yeah, that's what I would recommend.

Thanks for confirming my hypothesis. That's exactly what I ended up
doing in the version 0.23 of the feedback plugin I published earlier today.

Frank

--
Frank Hecker
heckerhecker.org