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 two threads:
Also check the documentation: http://wakaba.c3.cx/docs/docs.html
There is also a setup guide by Anon: http://wiki.iiichan.net/index.php?title=Wakaba_and_Kareha_Setup_Guide
Questions about "500 Internal Server Errors" go in this thread: http://wakaba.c3.cx/sup/kareha.pl/1109033191/
It's working on my debian box with lighttpd.
>>100
I actually have it running perfectly on my Debian box as well.
I believe this problem have something to do with the used perl version for openwrt.
I only installed the "missing" packages, but maybe I missed a few.
It isn't possible to install all perl packages at all, because there is not enough space left on the device
>>106
Only the bare minimum ones needed to run and connect to the database.
Well, better check that again, then. Remember not to comment it out, either.
Trying to set up a Kareha board, however, I've noticed that unless I delete kareha.pl, re-upload it and run it no changes take effect. Is this normal, or am I missing out on something?
>>109
Rebuild the caches from the admin panel after you make changes.
Well I got it working.
Sort of.
http://chansoft.heliohost.org/demos/wakaba/wakaba.html
I'm guessing it depends on the host's control panel, but just how would I do that?
wAHA, what do you think of youtube embedding in the post? Some users want it but I find it annoying when they just start posting a lot of embedded videos instead of images, or text, or at least links.
Would anyone mind telling me if i should be using the same cryptographic secret key across all boards?
If you want secure tripcodes to be the same across all boards, yes.
I get a 404 when I try to Preview Post using Opera (11.51). Does anyone else have this problem?
Got the Page-Load Problem solved. It was missing .pm file.
CGI::Carp qw ( fatalstobrowser does not work correctly on lighttpd.
use the following lines instead:
-> kareha.pl
#use CGI::Carp qw(fatalsToBrowser);
BEGIN {
use CGI::Carp qw ( carpout);
open ( LOG, ">>/tmp/cgi.log" ) or die ("Unable to open cgi.log");
carpout (LOG);
}
So you'll find the perl errors in /tmp/cgi.log
Anyone an idea to solve the problem, that I only see the new posts with a "refresh" of the page .. with lighttpd ??
Hi,
I am using wakaba 3.0.8, apache/2.2.21 and mysql 5.1.56.
Although the site is accessible, I can't post anything. The site just loads for about a second when i use the Submitbutton. There are no errors in the Apache or mysql logs. Any help would be appreciated.
>Anyone an idea to solve the problem, that I only see the new posts with a "refresh" of the page .. with lighttpd ??
I'm having this same exact problem with Wakaba (and maybe Kareha; too early to tell). Any solutions?
>>121
Configure lighttpd to serve HTML files with an "Expires" header set to a date in the past.
Rebuild caches.
Has anyone here ever tried to port Kareha/Wakaba into php-based framework app?
sorry for my bad english
wakaba.pl: Can't locate config.pl in @INC (@INC contains: . /etc/perl /usr/local/lib/perl/5.12.4 /usr/local/share/perl/5.12.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.12 /usr/share/perl/5.12 /usr/local/lib/site_perl) at /var/www/waka/wakaba.pl line 16.
[Wed Oct 26 22:18:00 2011] wakaba.pl: BEGIN failed--compilation aborted at /var/www/waka/wakaba.pl line 16.
how do i fix this?
Hi, I'm trying use Kareha in image mode, but keeping the textboard look, basically what this board is doing. I've setup kareha in text mode and image mode before, but how I set it up in imageboard mode and make it keep the textboard mode look?
The same thing is done on this board: http://www.secchan.net/niche/
>>127
set it up in textboard mode, then enable image posting in config.pl.
So I setup Wakaba on my hosts server and everything was working except for thumbnail generation. In place of the thumbnail you would see a dotted borderlined square, and in it is simple the words "No thumbnail." You click in and it opens the image just fine, but there is never any thumbnail.
Now, I just setup Kareha on the server in image mode, and the very same thing is happening. A dotted boarderlined square with the words "No thumbnail" inside it. And clicking the words brings up the image just fine. But neither will create thumbnails.
Is there anything that could cause this very same problem with both Kareha and Wakaba? I've tried what I could and now I'm stumped.
Help please?
My host uses Apache 2.2.17, by the way.
>>129
Get your host to install Imagemagick (the command line version).
>>129
Kareha and Wakaba need an external program to work? Lame. Well it can't be helped.
But, if I am unable to get them to install it, is there a workaround?
A BIG Thanks :)
>>131
get an imagemagick binary that will run on your server, put it on the server, and set the location in config.pl.
Hey guys, I'm trying to add spoiler text support to wakaba, and I'm new to perl so this is a lot harder for me than it should be. Is there any reason why adding the following to `sub do_wakabamark($;$$)' is not working?
elsif(/^\[spoiler\]/) # spoilers{
if ($lines[0]=~/^\[spoiler\](.*)/){
while !($lines[0]=~/\[\/spoiler\]$/){
push @spoiler,$1; shift @lines;
}
}
$res.="<span class='spoiler'>".(join "<br />",@spoiler)."</span>";
}
Thanks in advance!!
>>135
Oh and if it matters, I'm getting a regex error in this section for some reason, and I don't understand what that has to do with my changes:
# do ^H
if($]>5.007)
{
my $regexp;
$regexp=qr/(?:&#?[0-9a-zA-Z]+;|[^&<>])(?<!\^H)(??{$regexp})?\^H/;
$line=~s{($regexp)}{"<del>".(substr $1,0,(length $1)/3)."</del>"}gex;
}
>>135
>>136
>>138
Made a bunch of changes and got it working for the most part, but now I can't make the spoilers work if post contains any other text before or after the tags. Here's what I have:
elsif(/.*\[spoiler\].*/) # spoilers
{
my @spoiler;
if ($lines[0]=~/.*\[spoiler\](.*)/){
shift @lines;
while ($lines[0]!~/\[\/spoiler\]$/){
push @spoiler,$lines[0]; shift @lines;
}
shift @lines;
if ($lines[0]=~/\[\/spoiler\]$/){
$lines[0]="";
}
}
$res.="<span class='spoiler'>".(join "<br />",@spoiler)."</span>";
}
Not sure what to do next...
Okay, so I moved it until after WakabaMark finishes messing with the text, and did my best to work around the strange placement of the tags it introduced. Here's my "final" solution (until I get rid of Wakabamark completely and start from scrath):
if($res=~/.*\[spoiler\].*/){
$res=~s/\[spoiler\]*/\<span class\=\'spoiler\'\>/g;
$res=~s/\[\/spoiler\]*/\<\/span\>/g;
$res=~s/\<p\>/ /g;
$res=~s/\<\/p\>/\<br \/\>\<br \/\>/g;
$res=~s/\<br \/>/ /;
$res=~s/\<\/span\>\<br \/\>\<br \/\>/\<\/span\>/g;
}
Protip: Don't do that. It seems like it's easy to write a simple text formatter using a bunch of chained regexes.
It is not.
Every single regex is going to interact with every other regex, in subtle ways you will not predict, and you will open yourself up to mis-formatting and HTML injections. Hunting these down will be painful, and once you are done (which you never really are) you will have an utterly unmaintainable monster.
If you want write a text formatter, you will need to use some kind or other of actual parser.
>>141
Interesting. Well, I'm going to take your advice and keep trying to get spoilers working in a Wakabamark like fashion. Any advice?
Anyone know why both Wakaba and Kareha's generated HTML looks like this? If it matters, it happens under both nginx and lighttpd.
>>143
That's intentional. If you want to read the HTML code, use Firebug or similar.
There is little need for people to read it, and adding linebreaks just makes the code and output bigger for no real benefit.
I can post and it shows that in my admin management menu, but I don't see the posts in wakaba.html
How come they won't show?
>>147
Tried to F5/clear browser cache? If that works, use the included example.htaccess file to avoid the problem.
Is there a way for 2 people from 2 computer locations to share control over a Wakaba board? By control I mean fixing config.pl, changing link on top of the site, adding template style, etc.
How do you add boards?
I'm having minor cache problem with wakaba: new posts won't appear unless the page is refreshed, happened in both Firefox and Chrome. Is there a way to fix this?
How do I get rid of the /wakaba.html part from the main URL, as well as .html extension from every page?
I'd tried to use .htaccess but it doesn't fix the problem permanently: after posting, /wakaba.html returned.
>>155
Sorry I don't know, I have a friend hosted+coded the site and he's away atm. The private test board I set up is on Apache.
Last time I mention about removing /wakaba.html, he only said it can't be done even though I've seen some sites did it. So now I'm searching around. Does the methods for each differ much? It might be a good idea to document them.
>>156
Set Apache's directory index to wakaba.html or change wakaba.html to index.html in the config, then either 1) add rewrite rules to redirect wakaba.html to the board's root directory or 2) modify wakaba.pl to always redirect to the board's root directory.
>>100 uh what? i was using lighttpd on chansluts/male general/tranchan/chanchan/intern3ts/etc for about two years.
Is there anyway to force re generation of thumbnails? My older thumbnails are sized differently than my newer ones due to a different configuration, and I was wondering what I could do to make it more uniform other than resizing them in the browser.
Nope, sorry. Unless you write your own script to do it and update the database.
>>160
Might not even have to update the database now that I think about it. Aren't the file names more or less the same in the thumbs folder and the image folder? I'm guessing I can just run some sort of script that will resize the originals and add "t" to the end.
You need to update the image sizes. I think those are in the database.
>>163
Yes it would. Every thumbnail gets displayed with width and height attributes taken from the database.
>>164
I already changed how thumbnails were displayed in futabastyle.pl. I didn't change the larger ones though, since upscaling looks ugly.
>>165
Did you remove the width and height attributes? That's kind of stupid, because the page is going to bounce around like crazy while loading it, especially on slow connections.
>remove
No, I just set the width of all the reply thumbnails to 127px (apparently the height is adjusted accordingly), and my plan is to have the OP thumbnails display at 250px, which kinda has to be the native res if I don't want them to look like shit.
Try posting a 1x1000 pixel image now.
>>168
That -would- be annoying. Well, either way thumbnails are still resized with a 250px max height using imagemagick by default, so it still won't be that much of a problem
Is it possible to start an online archive for Wakaba board similar to how 4chan did it?
Is anyone else having problems logging into Wakaba on Dreamhost? I noticed they seemed to have broken REMOTE_ADDR which made the login not work at all for me.
Anyone else?
>>171
Works fine for me. Sounds like that is a server-specific issue.
>>135-141
So I FINALLY got spoilers working properly. I don't remember who told me, but the only way to get this to work without completely rewriting wakabamark was to hold off on the spoiler function until AFTER all wakabamark related things were completed. Anyways, I went ahead and put my code right after:
# restore >>1 references hidden in code blocks
$comment=~s/>gt;/> >/g;
...which was on line 846 in my version of wakaba.pl. Next is the actual spoiler code:
# new spoiler code (can't put it in 'do_wakabamark' because of 'do_spans' messing with the order of tags
if($comment=~/.*\[spoiler\].*/){
$comment=~s/\[spoiler\]*/\<span class\=\'spoiler\'\>/g;
$comment=~s/\[\/spoiler\]*/\<\/span\>/g;
$comment=~s/\<span class\=\'spoiler\'\>\<br \/\>/\<span class\=\'spoiler\'\>/g;
$comment=~s/\<\/span\>\<br \/\>/\<\/span\>/g;
}
Hopefully this helped -someone- out.
does anyone know why my kareha isnt generating an rss and backlog? the files are there, theyre just blank. my kareha is installed in imageboard mode if it makes any diff
nevermind i just copied the templates from the non imageboard file
Is there any way make individual posts display SJIS art properly in Wakaba like they Kareha does? Or is this something I'll have to add in myself.
>>179
There's no built-in way to do that, but you achieve it with a few quick additions to the templates.
Find something like this in the templates (it should occur twice, IIRC):
<blockquote>
<var $comment>
Replace it with this:
<blockquote<if $email=~/^aa$/i> class="aa"</if>>
<var $comment>
Then add this to either the global stylesheet in the header template, or to each individual stylesheet:
.aa { font-family: 'MS PGothic', MS Pゴシック, IPAMonaPGothic, Mona; }
Finally, to post with SJIS art, just enter "aa" in the email field. Note that I haven't tested this.
Speaking of CSS, was there any significance to .reply blockquote, blockquote :last-child { margin-bottom: 0em }
in futaba_style.pl? Most seem to consider the way it looks odd, and both 4chan and 2chan are rendered the way Wakaba would be without it.
Probably something about emulating the exact look at Futaba at the time it was written.
>>183
It works you do /aa$/i
as well. I didn't think to add mailto:
.
Im running apache2 on ubuntu, and I am not able to access .pl files from my web browser for some reason I get 403 errors every time. Its my own server, what have i messed up?
I did configure it for .pl and .cgi files in apache2.conf
Ask on an Ubuntu forum. And when you do, actually tell them what you did. People can't read your mind over the internet.
After I was making changes to config.pl in Wakaba 3.0.8 and uploading the revisions, I noticed that I can't get into the management panel without getting a software error, nor can anyone make any posts on the board without getting the same error. It says ADMIN_PASS and NUKE_PASS aren't defined. I didn't make any changes to those passwords while making my revisions and I don't know how to fix it. This is not my imageboard either. I'm just helping a friend and I don't want him to know.
Is there a way to disable WakabaMark rendering when posting SJIS art on Wakaba 3.0.7? i.e. don't bold or italicize asterisk and underscore pairs.
Quick question:
Is there a way to get the management panel to link to actual posts or show its thread? Currently it shows post numbers, name, subject, comment, IP, etc.
No ADMIN_PASS or NUKE_PASS defined in the configuration at /usr/lib/perl5/5.8.8/CGI/Carp.pm line 314.
BEGIN failed--compilation aborted at config_defaults.pl line 125.
Compilation failed in require at wakaba.pl line 17.
BEGIN failed--compilation aborted at wakaba.pl line 17.
Line 17 says
BEGIN { require "config_defaults.pl"; }
Kareha: When I move my board, including all scripts and files to another directory, nothing works right because it doesn't reflect the new path. Everything works fine in admin.pl and elsewhere if I add my /path/ to the address. I've tried rebuilding caches in admin.pl as well as deleting all of the html files and running kareha.pl in a browser to recreate them. I've tried recopying default config and all of the pl files. Is there something I am missing?
How would one go about disabling code formatting in Wakaba? Deleting this
elsif(/^(?: |\t)/) # code sections
{
my @code;
while($lines[0]=~/^(?: |\t)(.*)/) { push @code,$1; shift @lines; }
$res.="".(join "<br />",@code)."";
}
Doesn't seem to do anything but cause wakaba.pl to get stuck in and endless loop and consume 100% of my CPU.
>>193
You shouldn't really touch the parser unless you know what you're doing. That being said, you can probably fix the problem if you also change while($lines[0]!~/^(?:\s*$|1\. |[\*\+\-] |>| |\t)/) { push @text,shift @lines; }
to while($lines[0]!~/^(?:\s*$|1\. |[\*\+\-] |>)/) { push @text,shift @lines; }
.
>>194
That seemed to do it. I can't seem to figure out why though...
Running Kareha, 2ch mode. Every post (regardless of poster) got the same ID, which made me curious. When I saw the IP attached to the posts in admin.pl, it turned out that all posts were made by 127.0.0.1, somehow.
That seems pretty impossible and I have no idea what’s going wrong.
Are you infected with some kind of PHP malware that rewrites links? Check your .htaccess files for mysterious junk.
Yes, the parser is a terrible regex monster, and is not really understandable by anyone, including me. Lesson learned: Don't do parsers as a series of regex transformations, this never turns out well.