NineChime forum

The upload problem is with Wacintaki?  This problem did exist in Wax Poteto, but I'm not aware of any issues for Wacintaki.

Wax Poteto:  in the functions.php file, look for $uploadaccess -- there should be two references.  Make sure there are two equals signs next to both references $uploadaccess == 'yes'

As for the lack of a header on the paint screens, I felt it took up too much room, and it interfered with the ability to resize the paint applets to fill the screen.  These are minor quibbles, though... there should be no harm in having the header present, though it would be wise to have a control variable to disable the banner, if you have one.  It keeps things less crowded.

The error is likely because the NoteBBS JavaScript is missing, and that causes the palette to stop working.  Open up the header.php file, and right under the part where it includes the Poteto JavaScript, add the NoteBBS script, so you end up with this:

<script language="JavaScript" type="text/javascript" src="Poteto.js">
</script>
<script language="JavaScript" type="text/javascript" src="noteBBS.js">
</script>

Oh, OK.  Now I see...

There's no such thing as a member group in Wacintaki, so flags are assigned individually.  I do have a tool to change flags en-masse.  Basically, it strips all upload flags from everyone, because admins always have upload access.  Upload "strip_upload.php" to the server and run it.  Then, remove it from the server.  It works for both Wacintaki and Wax Poteto.

Upload flag toggle

I have no plans to implement member groups into Wacintaki, but that's definitely one of my goals for a future board.

The header can be tricky, because the order in which files are processed is important.  It looks like the header is just being included in the wrong place.

The standard procedure for a stand-alone page is as follows:

1 - Define "BOOT", so the bootstrap will be processed.  This keeps people from running the bootstrap directly.

2 - Collect the cookies OekakiU and OekakiPass (boot.php will clean this automatcially).

3 - Include boot.php, which also includes common.php, the config files, and niftytoo.php, and also processes the ban list and online list.  When collecting data from the paint programs or running functions.php, boot.php has to be configured carefully.  If just displaying the header on a normal page, boot.php requires no configuration.

4 - Process GET/POST data and any initialization required.

5 - If doing something that would require the use of "all_done()" or "report_err()", it MUST be done before the header is included.  This is what causes the error "headers already sent by (output ... header.php:159) in ...common.php on line 96".  common.php contains the error-reporting functions.

6 - Include the header. 

7 - Process any SQL and leftover initialization.

8 - Page HTML goes here.

9 - At the end of the page, either include footer.php, or call "@mysql_close($dbconn);" to close the database connection.

Here's a sample "paintBBS.php" file for you to examine.  I checked it on my test board and it worked fine.  See if it works for you.

PaintBBS, with header

The following code will allow you to exclude something normally in the header from the paint applet screens.

<?
if (strpos ($_SERVER['PHP_SELF'], 'BBS') === FALSE) {
    include ('stuff.php');
}
?>

As for the issue over...

...posting pictures in their profiles.

Yeah, I had to change that.  There's a number of good reasons not to put HTML and links to images directly into the database, and most of them are related to security.  NiftyToo (the markup system used for links, smilies, and other stuff) needs to be updated to support the IMG tag.  That's low on my priorities, though.  I've got a big to-do list regarding Wax 5.6.