NineChime forum

Okay, what happened here is that the "standard" registration filters out quotes and other symbols from regular usernames, but the installer for the admin account doesn't.  That was a major oversight and it means it's possible for the admin account to have quotes in usernames and that messes things up.  I could've sworn the installer validated the admin username, but... it doesn't.  Oops.

The fact the board does not support quotes in names has been a longstanding problem that I've ignored for too long.  I've decided to fix the board to allow names and passwords to contain all visible characters.  I have an initial patch that I've been testing all day and things seem to be working, but do please let me know if you encounter any problems.  You should be able to log in to the board after installing this patch without needing to reinstall or create a new database.

1.6.9 to 1.6.10 alpha patch

If for some reason you don't feel comfortable using the alpha patch, you'll need to delete your database and reinstall the board with a username that only contains alphanumeric characters.

I'll do more testing this week with my own oekaki board to make sure everything is working and secure, and then update the official archive soon.

Huh... I thought for sure it was a quotes issue based on the error you showed in your first post.  I know exactly where the installer is having a problem, but there should be no issues trying to insert the board owner information, so I'm not sure what's going on here.

I did some significant rework of the database error reporting in the installer.  Try this new installer and let's see if we can get some more specific information.

1.6.10 update

I figured this out.  As it turns out, the word "rank" is a new reserved keyword in the latest version of MySQL.  The proper fix for this is to rewrite all the SQL queries so all fields are quoted.  According to the SQL documentation this shouldn't be necessary, but... people change their minds all the time.

I'll get on this now, but my server (and thus, my development system) still uses SQL 5, so testing this might take a day or two.

I also discovered another severe issue with PHP 8.2 and file uploads.  This is now working correctly, too.

Edit: Here's a new version of 1.6.10 alpha.  Lots of files have changed, but make sure to upload all of them.  I'm fairly certain this will fix your issue, but it will take at least a week or so for me to make sure it's stable before it can be officially released.  Thanks for your patience.

Last edited by Waccoon (07-11-2023 00:54:48)

Wow, really?  ShiPainter works but ChickenPaint doesn't?  It sounds like the server isn't accepting file uploads and this might be tricky to diagnose.

There's no way to get more info from PaintBBS due to limits with the old Java applets, but I've added some more error reporting to ChickenPaint.  Rather than just give a generic error, it will try to give a specific upload error and we can go from there.

1.6.10_nemi.zip

One thing that comes to mind is that you should try viewing your board using HTTPS rather than HTTP.  Some servers may not allow file uploads unless you're viewing the board using the secure version of the HTTP protocol.  Many servers do that automatically these days, but it's worth verifying.

Well, dangit... that's the problem.  Your host has file uploads disabled.  ShiPainter uses a streaming method for sending data to the server, but ChickenPaint uses multipart encoded HTTP, so that qualifies as a file upload.

This is an issue you'll have to resolve with your hosting service.  In the BBS, go to the "Diagnostics" menu, and then look in the Config section for PHP Information.  Click on "click for more details" to get to the PHP configuration panel.  From there, search for "file_uploads" and "upload_tmp_dir" for more information on how the server is configured.  It's okay for the default temp folder to have no value, but if file uploads are off, there's nothing that can be done by the BBS to get around this.