This thread is for all your simple questions about installing and running Wakaba or Kareha, that just require quick answers. Please don't create new threads for issues like that, post them in here instead.

Before posting, check that the question has not already been answered in this thread, or in the previous thread: http://wakaba.c3.cx/sup/kareha.pl/1141929669/

Questions about "500 Internal Server Errors" go in this thread: http://wakaba.c3.cx/sup/kareha.pl/1109033191/

Is there any way to only permit registered users to post even though that is totally against the concept of imageboards?

>>118 in a way, using "approved" tripcodes.

>>117 It's in the wakautils.pl file. spam_checker(), spam_engine(), etc.

So, I've been trying to intall the latest kareha release on my webspace (perl version 5.8.7), and I'm getting stuck. When I go to http://www.ftmvariations.org/sg/kareha.pl I'm getting:

Software error:

syntax error at config.pl line 165, near "1;"
Compilation failed in require at kareha.pl line 12.
BEGIN failed--compilation aborted at kareha.pl line 12.

line 165 refers in my config.pl file to the very end, the last line with "1;"

---------
# Allowed HTML tags and attributes. Sort of undocumented for now, but feel free to
# learn by example.
# use constant ALLOWED_HTML => (
# 'a'=>{args=>{'href'=>'url'},forced=>{'rel'=>'nofollow'}},
# 'b'=>{},'i'=>{},'u'=>{},'sub'=>{},'sup'=>{},
# 'em'=>{},'strong'=>{},
# 'ul'=>{},'ol'=>{},'li'=>{},'dl'=>{},'dt'=>{},'dd'=>{},
# 'p'=>{},'br'=>{empty=>1},'blockquote'=>{},
#);

1;
---------

What I am doing wrong/missing?

>>121

You probably messed up the last uncommented line.

>>120
Provide a line number. It just doesn't happen.

I just traced the execution by hand, and unless I'm incredibly dense, it does no wget or locally implemented equivalent anywhere.
Full execution path is as follows:

1. wakaba.pl:486: post_stuff passes spam_files=>[SPAM_FILES] to spam_engine
2. wakautils.pl:1046 spam_engine initializes local @spam_files array
3. wakautils.pl:1054 spam_engine passes @spam_files to compile_spam_checker
4. wakautils.pl:1034 compile_spam_checker maps read_array on its local arg list
5. wakautils.pl:962 read_array accepts one scalar, which can either be a filehandle or a filename; if it's a filename, it opens the file locally with open FILE,$file. Either way, it returns all the lines in the given file as an array.
6. wakautils.pl:1028 back to compile_spam_checker to munge the results from read_array into a form suitable for inserting into a regex
7. wakautils.pl:1023 ... which it then does a bit more munging on, saving the results in @re
8. wakautils.pl:1036 still in compile_spam_checker, take @re and build a block of code out of it
9. wakautils.pl:1054 back to spam_engine; results from compile_spam_checker are saved as $spam_checker and all the form fields are scrunched together into $fulltext
10. wakautils.pl:1060 spam_engine still. actually run the spam checker with the given text, and call spam_screen if it gets triggered
11. wakautils.pl:1063 spam_screen just prints out a page saying "anti-spam filters triggered". (On an unrelated note, this page doesn't use the templates at all.)
12. wakaba.pl:493 if the spam checker didn't find anything, control returns here.

>>122

Thanks! that was that.

>>123 Hell if I know. WAHa! Defend your code.

Durrr, I think it won't load anything over http. There is a caching http loader function in wakautils though so it would be pretty easy to add it if one was into that kind of thing.

So I've loaded up kareha and it's all nice and pretty, but I can't post anything. After I press the Create Thread button the page reloads, but there is no new thread. What's most likely wrong?

Linux, Kareha 3.1.3

>>127
Sounds like your caching is screwy. You can confirm this by clearing your browser cache and reloading the page; if it still doesn't show up you've got other problems, but if it does...

Assuming you're using Apache, make sure you have mod_headers enabled. Try adding a line like the following at the top of your .htaccess:

Header add X-Test "This is a test"

If you suddenly get an internal server error, you don't have it enabled, so you'll have to fiddle with your httpd.conf.

mod_headers is enabled, clearing cache doesn't help. Also, kareha isn't reloading from include/rules.html either. This happens on multiple clients.

How can I change the character coding?
Well, I partially know where, but when I'm executing wakaba.pl, some special language characters are changed to "?"..

>>127

Delete index.html, hit kareha.pl from the browser.

>>130

Explain in more detail what you want to do, and what you're actually doing.

>>131
I want to set the encoding from the default utf-8 to windows-1250 (so the board can display polish characters).
I'm editing the encoding in config.pl (I'm also uncommenting it, I'm not THAT stupid). I'm also changing the .htaccess file.
I change the board title in config.pl to "różne" (with the polish chars, I don't know if they'll work on this board, there may be problems).
Then all the stuff gets uploaded, chmodded and I run wakaba.pl. What I get then: the title changes to "ró?ne" or something like that. I want the title to stay in its original, polish form.. But it won't work.
So?

Okay, I solved my encoding problem (the post above) but there's another one now.
As I'm trying to post a message on the imageboard, I get an error:

Software error:

Wide character in subroutine entry at /usr/lib/perl5/5.8.8/i686-linux/Encode.pm line 162.

What now?

>>132

There's no need to change the charset to do that. UTF-8 will allow polish characters just fine, and anything else, too.

I've got a problem with my kareha forum, new threads show up fine in the "view all thread" page, but don't show on the front page, even though I think my config.pl file is fine:

"# Page look
use constant TITLE => 'Intersections';
use constant SHOWTITLETXT => 1; # Show TITLE at top (1: yes 0: no)
#use constant SHOWTITLEIMG => 0; # Show image at top (0: no, 1: single, 2: rotating)
#use constant TITLEIMG => 'title.jpg'; # Title image (point to a script file if rotating)
use constant THREADS_DISPLAYED => 10; # Number of threads on the front page
use constant THREADS_LISTED => 40; # Number of threads in the thread list
use constant REPLIES_PER_THREAD => 3; # Replies shown
use constant S_ANONAME => 'Anonyme'; # Defines what to print if there is no text entered in the name field
use constant DEFAULT_STYLE => 'Futaba'; # Default CSS style title
use constant FAVICON => 'kareha.ico'; # Path to the favicon for the board
"

I'm wondering what's up with that?
I've tried rebuild caches.
When I look at the raw html of the index file, the post is there.

Hey, Just set up kareha, did config file, i can run perl scripts, and i set all the permissions to 777. But when navigate to kareha.pl, it gives me a 403 forbidden error... What should i try next?

ok, i think i dont have apache set up right. I uncommented the Addhandler, added .pl to its line, and added Includes ExecCGI to the options line, is there anything i forgot?

>>135

huh weird, now it shows fine.

>>135

Note the lines examples.htaccess that disable browser caching of the front page.

>>136

Try 755 permissions on kareha.pl.

>>139
unfortunately that didnt work

>>140
Are you sure you can run Perl scripts? Try putting

#!/usr/bin/perl
print "Content-Type: text/plain\n";
print "it works";

in a file, chmod it, and run it.

Gah. That should've been print "Content-Type: text/plain\n\n"; (note the double \n). Need to read what I type before hitting the button.

(Why can't I use <code> or <tt> with the HTML format?)

>>141
Youre right, that also gave a 403 error. I have a mac, so it comes with apache and perl, i uncommented the addhandler line and added ExecCGI to the options line in the httpd.conf file, what else do i have to do to run perl scripts?

>>143 Make sure that perl actually is installed to /usr/bin/perl

try:

#!/bin/sh
echo "Content-Type: text/plain"
echo
which perl
perl -V

(You can still save it with the .pl extension if you don't feel like messing with your config)

If that doesn't work, CGI scripts are just broken, because /bin/sh should never fail.

>>144
Yes it is
>>145
It still tells me its forbidden when running it from the web browser. Running it locally from the terminal is no problem.

Does anyone have success using Google AdSense on Wakaba/Kareha?

I'm trying to put simple banner ads in rules.html and footer.html but it's not working... is there either

* A better place to put them?
* Need to modify the .pl scripts instead of the .html files?

Thanks for any help or advice.

>>148
More details.

When I save the parts of the site, it works offline. It also works online when using Safari (OS X) and Konqueror (Linux). However it doesn't work when using Firefox 2.x on OS X or Linux... Is it something to do with XHTML/HTML configuration?

The error console consistently says on both platforms:

uncaught exception: [Exception... "Object cannot be created in this context" code: "9" nsresult "0x80530009 (NS_ERROR_DOM_NOT_SUPPORTER_ERR)" location "http://pagead2.googlesyndication.com/pagead/show_ads.js Line: 19"

>>148

Set STRIP_NEWLINES to 0.

>>150
Is that variable different from KEEP_MAINPAGE_NEWLINES ?

>>151
I would say so. KEEP_MAINPAGE_NEWLINES will keep your newlines; there doesn't seem to be a STRIP_NEWLINES anywhere in the code though. :)

In any case that's what you want.

The thing that's really waxing me about this is that it totally works and looks exactly the way I want it to in

* Safari (OSX)
* Internet Explorer 6&7 (Windows)
* Konqueror (Linux)

But in Firefox 2.x on all platforms it doesn't work for some reason!! It's driving me bananas.... why would it work in some browsers and not in others?? Does it have to do with the handling of the onMouseOver method?

In Kareha, spaces in AA aren't replaced with &nbsp; or anything, messing up the rendering.

Since I don't know perl or regex the best i can get (with google's help) is:
$str=~s/????????/&nbsp;/g; #clean up spaces for AA

(in the clean_string sub)

>>154

No other board does either. In Shift-JIS AA, you use full-width spaces instead.

>>153
Yeah, I'd try turning off USE_XHTML, if it's enabled. I think Firefox is the only browser out of the list you gave that supports it.

>>155
Regardless, could you please give me something that'll let me use regular spaces?

>>157
Actually, nevermind.

I just replaced each double space with a full-width

>>154
Ah ok. That's a good place to start. I'll mess with it and report back.

use constant ADMIN_PASS => 'password'; # Admin password. For fucks's sake, change this.
use constant NUKE_PASS => 'password'; # Password to nuke a board. Change this too, NOW!
use constant SECRET => 'omgwtfidiedlol'; # Cryptographic secret. CHANGE THIS to something totally random, and long.
use constant SQL_DBI_SOURCE => 'DBI:mysql:database=umbrella_wakaba;host=localhost'; # DBI data source string (mysql version, put server and database name in here)
use constant SQL_USERNAME => 'umbrella_interne'; # MySQL login name
use constant SQL_PASSWORD => 'h8machine'; # MySQL password

still getting sql failure. can anyone see any n00b mistakes? Mysql names/pwords/locations have been double triple checked.

Check your error log, usually there's more information in there. In particular if mysql is complaining about /tmp/mysql.sock, try replacing the localhost with 127.0.0.1 and see if that helps.

I got Wakaba working with PostgreSQL. It took a little bit of fiddling with the table structure, but the changes are worthwhile on the whole, I believe:

• changed IP and mask fields to integers. (Why were they stored as TEXT in the first place?)
• moved static IP mask calculation from SQL into Perl
• all INSERT statements explicitly state their values

There's still a few more things that should be done, particularly rewriting the COUNT(*) queries as Postgres doesn't even try to optimize them, and modifying the table init check to convert the data from an older version. It's a start though, and everything seems to function.

Any ideas about why, when I make any change to wakaba.pl (even harmless stuff like declaring variables) I get a 500 server error?

I'm running wakaba on a linux webhost, PERL 5.008008, the error log says

Mon Feb 11 16:48:20 2008] [error] [client xxx.xxx.xxx.xxx] failed to open log file, referer: http://www.domain.com/cgi-bin/wakaba.pl?task=mpanel&admin=WXdiMCdCZ4HJ
[Mon Feb 11 16:48:20 2008] [error] [client xxx.xxx.xxx.xxx] fopen: Permission denied, referer: http://www.domain.com/cgi-bin/wakaba.pl?task=mpanel&admin=WXdiMCdCZ4HJ
[Mon Feb 11 16:48:20 2008] [error] [client xxx.xxx.xxx.xxx] Premature end of script headers: wakaba3.js, referer: http://www.domain.com/cgi-bin/wakaba.pl?task=mpanel&admin=WXdiMCdCZ4HJ

Ok nevermind, it was Dreamweaver's fault. Editing the files with notepad and uploading them with another ftp client works.

I'd like to ask what I need to look out for when making manager posts on Wakaba.

I can't find any errors coming up in logs, but I tried to make a manager post with a comment and it keeps returning Error: no comment entered.

Where might I find more information on this, please?

>>165 The fields are mis-named in the manager post screen; they need to be called "field 1", etc, like they are on the board proper. Waha forgot to change them.

So would anyone mind telling me please how to get around the problem? What would I need to change in order to get this working? :)

I can't make any manager posts at the moment :(

It's really straightforward, just change the first four form fields in the ADMIN_POST_TEMPLATE form to "field1", "field2", "field3", and "field4".

uh... I've made this change and now when I hit submit it just takes me back to the index page, logging me out of the management panel as if I'd not bothered logging in. When I refresh, there's nothing record of my having posted. This seems a little off, I reckon. It may be straightforward, but it's got me stumped. I doubt this is supposed to happen?

>>169
Did you fill in the "parent" field with the thread you're posting to?

If you want to make a new thread, put a zero there.

>>170

hmm... yeps, tried that. Same thing happens. I'm a bit baffled, to be honest.

>>171

Try looking at the source to see if the action attribute in the <form> is filled in right.

here's the source code from the manager post page, if this is any help?

<div class="postarea"> <form id="postform" action="/wakaba/wakaba.pl" method="post" enctype="multipart/form-data">
<input type="hidden" name="field1" value="post" /> <input type="hidden" name="field2" value="ZfL9BDt4YCBq" />
<input type="hidden" name="field3" value="1" /> <input type="hidden" name="field4" value="1" /> 
<table><tbody> <tr><td class="postblock">Name</td><td><input type="text" name="name" size="28" /></td></tr> <tr><td class="postblock">Link</td>
<td><input type="text" name="email" size="28" /></td></tr> <tr><td class="postblock">Subject</td><td><input type="text" name="subject" size="35" /> <input type="submit" value="Submit" /></td></tr> 
<tr><td class="postblock">Comment</td><td><textarea name="comment" cols="48" rows="4"></textarea></td></tr> <tr><td class="postblock">File</td>
<td><input type="file" name="file" size="35" /> [<label><input type="checkbox" name="nofile" value="on" />No File</label> </td></tr> 
<tr><td class="postblock">Parent</td><td><input type="text" name="parent" size="8" /></td></tr> 
<tr><td class="postblock">Password</td><td><input type="password" name="password" size="8" />(for post and file deletion)</td></tr> </tbody></table></form></div>

>>174

Oh, I see. >>168 meant the first four input fields of type "text". The "hidden" type fields should be left as is.

oh... duh. Cheers for that, I'll check 'em and change 'em :D

I want to know how to install Wakaba to my website?

>>177
Try thinking.

>>177 http://wiki.iiichan.net/Wakaba_and_Kareha_Setup_Guide

I have installed kareha on to my webserver. My hosting runs perl, I have CGI running and the code went in great. The only problem I'm having is when I post an image it doesn't show up. It show shows up as a hyperlink and when I click on it it takes me to the exact location the image is, "site.com/cgi/src/00000.jpg" Yet an internal server error pops up.

I'm hosting with godaddy which sucks, but they say that imagemagick does run on the hosting server but that it's not installed. (If that makes sense) Could this be the problem? Please, I need help from anon.

Please deliver.

Sound like a) imagemagick is not installed just like they say and b) they don't allow access to images in the cgi directory anyway. You'll need to fix both.

Any thoughts about XHTML2 or HTML 5?

How do i get futallaby working with images in replies?
sry for wrong board but there is no futallaby support anymore Oo

>>183
There's a reason for that. Use Wakaba, or if for some crazy reason you absolutely need to have PHP, find one of the Futallaby hacks with image replies... or you could just use Futaba and translate it to English.

Can someone post up a good rotating script? .pl or .php please.

>>185
lol @ .tk

>>185 google "php image rotator" and you'll find plenty.

>>188 Ty
>>187 Umm, ya...good for you.

hi. using kareha. installs fine, but now getting 405 error:

Method Not Allowed
The requested method POST is not allowed for the URL /kareha/index.html.

Apache/1.3.37 Server at mysite.net Port 80

any ideas?

Your webserver is set up to not allow POST requests.

>>191
that's not the only problem, for some reason his browser is trying to POST to index.html

>>190
Did you run kareha.pl from your browser? All sorts of things break if you try to run it from the command line.

Any reliable way to convert from mode_image to mode_message? I've converted my boards to display in mode_message now, but all of the old posts are still stored in the mode_image format, making readability very tough and producing a rather inconsistent look.

Take http://www.fatechan.net/moe/kareha.pl/1162824087/l50 for example, the mixed posting looks very odd. If I knew more perl I'd just code a conversion script myself, but I don't :<

No, you pretty much have to write a script that does the conversion yourself.

Here's a quick outline: Copy the first line verbatim, ignore the second line and write an empty line instead ("Rebuild caches" will fix it for you later), and ignore the last line in the same way. For every other line, use regexes to extract the various data fields, and then use the templating engine and templates.pl to create the new line.

You might want to fix the >> links too, they'll all be wrong.

>>196
Wait, no they won't, I suck cocks.

How to make the HTML code nicer so wakaba doesn't output everything in one line? ^_^

Is there any simple ''hack'' to do this?

I've tried with some prints and searched http://perldoc.perl.org/ for useful information but seems like I can't get it nicer.

Thanks for any replies. :b

>>198 there's an option in config.pl. STRIP_NEWLINES? If it's not there, and you've been upgrading from an older version, dl a new version, double-check what the setting's called, and add it to your config.pl.

>>199

Hello, I was unable to find it in Wakaba, but copied it from Kareha and added ".NORMAL_FOOT_INCLUDE,KEEP_MAINPAGE_NEWLINES);"

Thanks for the info!

Everything else works, image posts and replies.. so on. But when I put in my password at the [Manage] panel, it says it's wrong.

use constant ADMIN_PASS => 'password'

has been changed and everything... Dreamhost, permissions and everything else right/working

>>203

Are there any special characters in the password?

>>25

I'm getting the same problem. I've tried changing the password, using only numbers... it won't let me access the management panel.

>>204

ha, I'm a retard, didn't even notice that first one posted. No special characters, only numbers

Oh weird, I changed the URL to have my password on the end and it suddenly started working... um, do I just have to keep doing this? Actually, I don't mind... but if anybody knows what's going on..

I was wondering how hard it would be to set up on a wakaba board a spoiler/censor system like some boards, noteably 4chan's /a/ and /co/, have to replace the thumbnail with a black box or something. Is this something that would take a lot of work? Has already done it and if so would the mind sharing how to set it up?

>>207 it's not hashing, then? That's very odd.

>>207

Sounds like something is very strange with your server, maybe?

I've discovered a denial of service flaw in Kareha, and I've been the victim of these attacks for the past few weeks. I dunno if it's intentional or just some sort of bizarre bug, but if you send a specially formed string in the call to kareha.pl, it will cause the process to hang, forcing lighttpd to spawn another one in a neverending race condition.

It's completely crashed my server twice, and just today I barely caught it in time by noticing the telltale studdering in my ssh connection and killing lighttpd before it got too far.

Sounds sort of like a lighttpd bug. I don't think a CGI process should ever be respawned under any circumstances.

>>212
FastCGI, maybe?

I'm using mode_message and:
use constant PAGE_GENERATION => 'paged';
on my board and I see that kareha is indeed generating cached thread pages (1.html, 2.html, etc) but it doesn't create a page list on any of them. Basically the only way to get at threads that fell off the front page is to view the All Threads page and pick one from there.
Did I miss an option to have it stick a page list somewhere?

>>214
paged and mode_message aren't so great together.

You can hack the template and add that stuff...

I'm not using fastcgi, just the standard cgi caller, and it's spawning multiple perl processes because the "attacker" will make multiple calls, and since the perl process is hung, the old ones will never die, eventually leading into an out of memory condition.

I guess I misworded it, lighttpd itself isn't spawning new perl processes, but the old ones won't expire so every call to kareha with that malformed string creates a new perl process that hangs.