http://wakaba.c3.cx/releases/wakaba_2.0.zip

First of all, you will notice that I have bowed to the demands of the people and added a version number to Wakaba. It has somewhat arbitarily been selected as 2.0 for this new release.

This new version brings some changes: wakaba_style.pl is no longer supported, because it was leading to rendering problems in several browsers, and didn't really add anything interesting. Furthermore, I've re-written futaba_style.pl to use the templating system from Kareha, so modifications and fixes should be easier and easier to handle (or so I hope). I've also ported over the stylesheet switcher from wakaba_style and Kareha, which now uses Futallaby-style stylesheets. I was meaning to create some stylesheets of my own, but in the end I didn't find the necessary creativity and just included some by other people: !DEEPjKeito's Gurochan style, and terra's Burichan style.

More stylesheets would be nice to have, and if you feel like making one, go right ahead.

Now then, some more detailed changes:

• A new option, IMAGE_REPLIES_PER_THREAD, lets you limit how many image replies are shown on the main page (there is still no limit to how many you can post, threads just get shortened on the main page until they show only a certain number of images).
• The email field should now support URLs.
• A German translation has been provided by lolocaust, and can be found in extras/strings_de.pl. The other language files have also been renamed to use two-letter language abbrevations (strings_en.pl and strings_jp.pl)
• Files in include/ can contain the templating functions. mid.html has been renamed rules.html, and contains the default rules. This, along with the header.html and footer.html files should help avoid having to modify futaba_style.pl for each board. S_HEAD, S_FOOT and S_RULES were also removed entirely from the strings file.
• oekaki_style.pl has been updated for the new system, and there have been some fixes for the oekaki files. You can also set ALLOW_IMAGES and ALLOW_IMAGE_REPLIES to 0 on oekaki boards to disable image uploading, should you feel like it. Oekaki posting will still work.
• The post abbrevation bug has been fixed.
• The No.1 links now link to reply page.

I'd like everyone to upgrade to this version as soon as possible, because it contains a number of features that make board usage and maintenance easier. But since there are some pretty serious changes, it might be best to just install it on a few boards to start with to weed out any bugs I missed.

One more things: futaba_style is now very strictly XHTML compliant, and can be sent to browsers as application/xhtml+xml. The included example.htaccess is set up to send it as such to browsers which report themselves as supporting it.

I have updated to this version on /g/ at GUROchan, and it is working fine. Unfortunately I will be away this weekend, so I don't have the time to update the other boards before I come home again.

Anyway, I have one question. Probably a stupid one too. How can I choose which style's set as default?
I've set use constant CSS_FILE => 'css/gurochan.css'; in the config, but Futaba is still default.

Thanks for your good work!

>>5

I have noticed that the vericodes don't update properly on /g/ now - I have to reload the reply page to get them to refresh.

>>5

CSS_FILE is outdated, and I just forgot to remove it. There's a DEFAULT_STYLE option that you can set to the name (proper name, not filename) of the style you want as default.

>>6

Bug confirmed and fixed.

http://wakaba.c3.cx/releases/wakaba_2.0.1.zip

Software error:

Can't locate strings_en.pl in @INC (@INC contains: . /etc/perl /usr/local/lib/perl/5.8.4 /usr/local/share/perl/5.8.4 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8 /usr/share/perl/5.8 /usr/local/lib/site_perl /usr/local/lib/perl/5.8.3 /usr/local/share/perl/5.8.3 /usr/local/lib/perl/5.8.2 /usr/local/share/perl/5.8.2 /usr/local/lib/perl/5.8.1 /usr/local/share/perl/5.8.1 /usr/local/lib/perl/5.8.0 /usr/local/share/perl/5.8.0) at /home/www/humblefool.hollosite.com/img/wakaba.pl line 18.
BEGIN failed--compilation aborted at /home/www/humblefool.hollosite.com/img/wakaba.pl line 18.

I just switched to 2.0.1, and this pops up when I attempt to axcess the manage panel on /art/. The I didn't want to replace config.pl, but does this mean I have to?

You didn't install all the files, if it can't find strings_en.pl. You'll have to install all of them (including the ones in include/ and css/), except config.pl, for it to work.

Did NUBChan update? When I try to reply to this thread, I get a "thread does not exist" error.
http://nub.wakachan.net/b/res/3216.html

New Wakaba reported as broken as a junk car. Nuff said.

I should have mentioned that if you use the .htaccess to make it send pages as application/xhtml+xml, you must make sure that your pages are well-formed XML or the browser will scream at you. The default code IS, but any modifications have to be too. That's what's NUBchan's problem right now.

Actually, the admin panel is ALWAYS sent as application/xhtml+xml, which means that if you fuck up the XHTML, the admin panel breaks. This is a good indicator that you should fix your XHTML.

>>13

I of course meant, "That's what's NUBchan's problem's right now."

http://wakaba.c3.cx/releases/wakaba_2.0.2.zip

I found a few small mistakes in futaba_style.pl and the include/* files, so I fixed those. I also fixed some old bugs I had forgetten about, such as the #-in-filename bug, and the bug when not renaming image files.

I also added a few default icons, for various chiptune formats, and for torrent and flash files. The default rules.html now correctly lists all the external format you have specified, too.

> I of course meant, "That's what's NUBchan's problem's right now."

That makes no sense.

>>17

Because IS JOKE.

Oh. haha

Sling found another bug... orz.

http://wakaba.c3.cx/releases/wakaba_2.0.3.zip

The only files that have changed since 2.0.2 are futaba_style.pl and oekaki_style.pl (and config_defaults.pl if you want to get the new version number).

If you have a hand-customized futaba_style.pl, the fix is this: Change

get_reply_link($num),$parent

to

get_reply_link($num,$parent)

ZMatt has made a new CSS style:

http://www.lvl99.com/photon.css

It's in the 2.0.3 archive too, now.

orz^2, yet another bug found, by cyril this time. Under certain unlikely circumstances, which of course nevertheless happened on his board, the post list panel can break. This version fixes this. The only files that have changed are futaba_style.pl and config_defaults.pl (just for the version number).

http://wakaba.c3.cx/releases/wakaba_2.0.4.zip

Go go go! Release hound!

http://dis.wakachan.net/err/kareha.pl/1108428098/

I forgot to mention this known bug: Old articles's email addresses will lack a mailto:. New articles will be fine, and since people so rarely use the email field for anything useful I didn't feel the need to code a workaround for the old articles. They will get deleted in time anyway.

http://wakaba.c3.cx/releases/wakaba_2.0.5.zip

Anonymous found a bug with the filetype handling - you had to turn on ALLOW_UNKNOWN before you could upload any of the defined external filetypes. This is wrong, and you shouldn't have to turn that option on for this to work. This is fixed, and I also included dmpk2k's icons for archive files.

Did you change anything with cookies? I upgraded and cookies refuse to work now, not sure if it's something I did or what.

Shouldn't be any changes to the cookie code... Did you try force-refreshing to make sure the latest .js file is loaded?

Yeah. No good.

You're right. Somewhere in the confusion I'd managed to mess up the Javascript linking in the template... orz

http://wakaba.c3.cx/releases/wakaba_2.0.6.zip

Damn, two in one day, I'm awesome.

problem with FILETYPES...

>syntax error at config.pl line 133, near "7z"

Ah shit. That has to be '7z' => icons/.... Worth an update, or should I just wait until the next bug?

I decided just to quietly update that without bumping the version.

let's go 1000 by http://wakaba.c3.cx/releases/wakaba_2.0.*.zip

See, this is why not having version numbers is a good idea. Nobody notices when you do long runs of bugfix releases like this.

I agree, the old date-based system was better.
Also, I think you should keep mentioning which files have been changed for easier updating.

I didn't mention it this time because I wasn't quite sure... There was some confusion, as indicated earlier.

The date-based system made it hard to tell how big the changes were. Also, since dates are bigger numbers it was harder to just quickly look and see if your version was latest.

use version+date, e.g. Wakaba v2.0_20050219, so you would only update the version number for massive changes.