Furry stuff, oekaki stuff, and other stuff.
You are not logged in.
I feel really bad about this massive bug, so I made a recovery tool to help with recovering the orphaned pictures.
If you're an admin, go into picture recovery. If you see any pictures without usernames, then some of your board members have run into this bug, and you'll need this tool: 1.3.14_fix_orphans.zip
It looks for pictures with similar IP addresses and tries to make a username match. Just copy if to the root folder and run it. It will show a table of images and any matches it finds, and you just click the link to repair the image. Repeat the process until all images are fixed. If a match cannot be made, you'll have to ask your members who drew the picture, and then re-upload it under the correct username.
As usual, remove it when you're done, though it's not a security problem to leave it on the server.
Well, it looks like 1.3.14 was a pretty bad release. A major problem has been discovered with the applet code, and it prevents people from submitting pictures.
This problem affects PaintBBS and ShiPainter, but not OekakiBBS and Chibi Paint. PaintBBS and ShiPainter don't use URI encoding for their send headers, so verification codes that contain slashes and have been URL encoded will be broken. As a result, any members with verification codes that contain slashes will be unable to post pictures with these applets. Based on some quick stats, this appears to affect about one out of five members on any given oekaki, and depends on his/her password.
So, here is yet another hotfix for Wacintaki 1.3.14. It is required for all downloads of 1.3.14 before July 12th.
Images that have been submitted are not lost, but instead end up in the picture recovery section. They will not be attributed to any artist. Images may be recovered, but they will have to be uploaded as files by an admin for the images to be attributed to the correct artist.
I'm sorry for yet another round of problems. If anyone discovers odd behavior regarding 1.3.14, please let me know ASAP so I can determine if it is a fluke or an actual issue. A lot of code changed in 1.3.14.