>>57 It output's:
Can't locate Captcha/reCAPTCHA.pm in @INC...
Should I reinstall? I've searched Google, no helpful information.
>>58
How did you install it? I use Debian and installing it through the package manager always worked for me. Using CPAN left out a dependency or two.
I decided to reinstall it via the package manager, and I don't receive that error anymore, but now it's saying the verification code is wrong even when it's correct. I've tried it with 10+ different codes.
>>61
I can't help you with that one. Only thing I can think of is the public/private keys being incorrect, or your server being unable to connect to Google's servers.
Adding onto my previous post;
Before:
make_error(S_BADCAPTCHA) unless $result->{is_valid};
I added:
print $result->{is_valid};
and it printed the source code of the page.
I really need help with this. I've tried everything. All the keys are correct, I've even tried it on a clean install.
Anyone at all? I've tried literally hundreds of things.
>>68
Hi,
I've taken the time to trace the problem, and I think I have a fix (but as usual, I'm too lazy to test it until anyone whines about it):
Find:
my $challenge=$query->param("challenge");
my $response=$query->param("response");and replace it with:
my $challenge=$query->param("recaptcha_challenge_field");
my $response=$query->param("recaptcha_response_field");That should hopefully do the trick. Obviously it was a derp on my part, I'll create an updated patch soon to rectify this.
Also, why do you even need reCAPTCHA that desperately? The default CAPTCHA is fine, easy to fill out, hard for bots to break and can easily be tweaked if you need better anti-bot measures.
If you're trying to cope with spam, I think you'll find that many of those so-called bots are actually humans.
>Ok, now I don't get "Error: Wrong verification code entered.", but it doesn't post the message. I've rebuild the caches, but no avail.
That's weird. I just tested the fix myself, and it works perfectly for me. Did you try fixing this on a clean install?
>It's definitely bots. Unless the same human is posting 20+ messages a second.
Uh, okay.
>>53
this is what i'm trying to accomplish. where do you change the redirect call? i've tried changing it in every call to make_http_forward i can find, but it doesn't work for me unless I put it in the actual function...
sub make_http_forward($;$)
{
my ($location,$alternate_method)=@_;$location = "http://website/index.php?board=Main"; // <--- this is awful.
if($alternate_method)
{...
I've always wondered why people thought noko was pointless. If anything it makes navigation easier. Shit, nobody even knows if you use it or not. I already wrote a noko patch for wakaba (a bit different than the one in this thread) and I'm planning on adding noko to Kareha as well. Anyone interested in a patch?
> I've always wondered why people thought noko was pointless.
it's because pretty much all browsers have a back button.
> Shit, nobody even knows if you use it or not.
yes, they do, because you usually can't use noko and sage at the same time.
>>76
Pretty sure nokosage exists, at least in Yotsuba.
When you use the back button usually you don't see the latest posts.
>>82
everyone uses the web this way aside from /b/tards. if you think noko is so useful, just write a tiny bit of javascript to implement it in your browser.
>>84
I already implemented it in Wakaba, and most message boards and forums have the feature built in and enabled by default.
Hey, you made PHPerl, which I never got around to making. GJ.
Anyone running a Wakaba board ought to read this.
There's a serious vulnerability in Wakaba 3.0.8 and below which let's anyone inject whatever HTML they want to in posts. This can be fixed by removing a couple of lines in the get_decoded_hashref() and get_decoded_arrayref() subroutines in wakaba.pl, as shown in the included patch file. There should be no problem in making these changes.
Board moderators with no access to the board files may add /chr\([0-9]/ to spam.txt in order to fix the problem.
Looks like that is there to work around some absurdity in MySQL. I supposed MySQL has since changed and is now doing the wrong thing?
I'll put together a 3.0.9.
Pay no attention to the devs that tell you that you don't need something, such as noko. They seem to be into some weird sub/dom kink and want the world to bend their way. Just fork their code and make it better.
>>95
Or you know, they could just not feel obligated to bend to your every need.
> Just fork their code and make it better.
The sort of people who want things like noko aren't capable of that.
Just did these for a guy in another thread, but I might as well post them here to keep things organized
Hold back posts for moderation 1/2
Hold back posts for moderation 2/2
>>100
Just do ALTER TABLE comments ADD approved TINYINT; in the sql interface
>>101 Not for me, for others :p
I do get this error when I click an approve link within the admin panel:
DBD::mysql::st fetchrow_hashref failed: fetch() without execute() at wakaba.pl line 2066
Ignore the line number, my copy is modded.
sub get_decoded_arrayref($)
{
my ($sth)=@_;
my $row=$sth->fetchrow_arrayref();
That's the issue line.
>>102
No idea. Are you using SQLite or a regular mysql database? I've only tested this on SQLite. Also, did you try to run the actual patch on your modded wakaba.pl? That could very well be the issue.
The mod works, it just also throws that error into the error log. It's just MySQL.
What happended to this site? Everything I see here is so old :(
AND I have no clue about how to get kareha running.
>>105
Wakaba is mostly mature at this point. There really isn't too much to do to Wakaba to make it a futaba channel clone so therefore, there really isn't much to discuss. I suppose it would be nice to update Wakaba and Kareha to make it HTML5 semantic.