NineChime forum

I have no idea why some servers lose file extensions while most do not.  It might be a MySQL thing.  In the documentation folder of the distibution, there's a file called "fixtypes.php".  Copy that to your oekaki folder and run it.  Then, delete it.  That will rebuild all the filetypes on your board.

To make files writable in the resource folder, the files and the folder itself must be writable.  Use testinfo to check whether the all the required files are writable.  Note that you must be logged in to use this diagnostics file.  If the standard 664 and 775 don't work, try 660 and 760.  If you can't get it to work at all, I can fix it.  Some servers are just fussy.

The banner and rules will be created automatically if they do not exist.  However, the oekeki folder must have correct write permissions to do so.  Once the resource folder is writable, you'll be able to edit these files.

OK, here's what I can gather:

1) Your server requires execute bits on folders, so don't use 0 as the last CHMOD digit.  This is unusual for PHP scripts, but nothing to worry about.

2) Your folders may still have a CHOWN where PHP is the owner, but it conflicts with Apache (Apache has its own security layers that run in tandem with the OS).  You may not be able to set the CHMOD back to 755, and that may not be a good idea, anyway.

3) 777 isn't that big a deal, and there are some servers that require it if the CHOWN is set to PHP.  I'm not totally sure how it affects local shell access and shared FTP access on your account, but 777 isn't a security threat as far as the web server is concerned.  Originally, OekakiPoteto required all folders to be 777.  On most servers, 777 is not the default, is overkill, and in some cases is disabled entirely.  So, it's a good idea to stick with 755 or 775, but not required.

My recommendation is to set the pictures and resource folders to 777, and use the "reclaim.php" script in the documentation folder to unlock the ban list, notice, and so on.  The reclaim script works by copying the information in locked files to new files and deleting the old ones.  It almost always works, provided the oekaki folder itself is writable.

Once the resource folder is unlocked, the board should have no trouble making banner and rules files when you use each respective editor.  The banner is optional, but you should have a rules file.

Animations:
Some FTP clients don't know that Java files are binary.  FTP clients normally allow you to switch between ASCII and BINARY modes.  Make sure you are in binary mode, and re-upload all the files that end in ".zip" or ".jar".

Registration:
I just registered and didn't have any problems.  I was re-directed to the profile editor as normal.

Do you have any specific error messages you can give me?  People tell me about this every now and then, but I've never been able to reproduce the problem.

Rules:
Hmm... I thought the board would make a new file automatically.  Oh well.

I see your banner has a file size of zero.  Download a copy of that file to your computer, rename it to rules.php, upload it to the resource folder, and CHMOD it to 664.  You should then be able to edit the rules.  The file is supposed to be regular HTML, so use the <p> tag or <ul> bullets.

Sorry, I misread that as "class not initialized", instead of "class not found".  The first error is a lot more common.

I just tried to view the shipainter folder, and the server won't let me in.  That's the folder that has the animation viewer in it.  So, CHMOD that folder so it is no longer "forbidden" to the public, and web browsers will be able to download and run the animation viewer.

Note that the folder only needs to be readable.  Don't go bonkers trying to get that folder to be writable, because that's not required.