Furry stuff, oekaki stuff, and other stuff.
You are not logged in.
If the e-mails are not actually getting sent, then your server has a problem sending e-mails.
If the e-mails are being sent, but you are still getting this error message, then I'm afraid your installation of PHP has the infamous e-mailer bug, and only a PHP update will fix it.
I can write a wrapper to bypass the error messages in Wacintaki 1.3.8. This is a common and annoying problem often discussed on PHP forums.
One other quick thing, if you don't mind. When accepting new members, i keep getting the error 'new member was approved, but email could not be sent' and I seem to get that 'email could not be sent' message in a few areas of the oekaki. Any thoughts?
~Xean45
Wow! Thank you so much! That's why I like using your software. Completely thorough.
Thanks again ^_^
~Xean45
The first problem is a web server configuration error. By default, a folder containing qualifying indexes should serve the index rather than give a directory listing. If you're using Apache, you need to change your "httpd.conf" file to include the proper indexes. Apache does not support PHP indexes by default -- you have to add them.
The DirectoryIndex tag controls which indexes will be served, and is about 1/3 the way down in the file. Make sure "index.php" is in there somewhere. Here's an example:
DirectoryIndex index.html index.htm index.shtml index.html.var index.php
Migrating an oekaki can be tricky. First, you have to take the oekaki offline (delete the index.php file and replace it with a dummy index.html file). Then, make a complete backup of the database with a tool such as phpMyAdmin. Once you have your db backup, copy all the files from the old server to the new one. CHMOD all the files to their appropriate numbers (see below). Restore the database on the new server. You then have to update the config files on the new oekaki to reflect the changes -- in particular, the database information ("dbconn.php") and the URL to the oekaki ($cfg['op_url'] in the file "config.php"). You may have to edit the config files by hand rather than through the oekaki control panel, especially if the database information is different, which it usually will be.
*CHMOD numbers: When uploaded via FTP, files must have less restrictive permissions than if the server creates them automatically. A lot of files must be changed when moving a board between servers!
The config.php and dbconn.php files must be 664.
The working folders must be 775 (avatars, pictures, resource, tempaltes)
All the files in the avatars and pictures folders must be reset to 664. Failing to CHMOD all of them may result in future pictures being lost, and avatars becoming orphaned or irreplaceable.
In the resource folder, all the PHP and TXT files except "hacks.php" must be changed to 664.
In the templates folder, the PHP and CSS templates must be 664. Folders (such as the "Banana" folder) and the files within do not have to be changed.
When done, log in as the owner and check the diagnostics. That will tell you if any folders or critical files are not CHMOD correctly. Files with the wrong CHMOD number will show up as "Locked", which means they are not writable.
Hello, hello!
I've installed Wacintaki 1.3.6 onto my new server and plan on migrating my current Wacintaki 1.3.1 over.
So, two questions, I guess:
On my Wacintaki 1.3.6 installation, the "View" link in the top left of the header displays the Oekaki's directory. Is this a known bug, or did i just botch the installation?
The 1.3.6 installation can be found here: wwwpermanentreality.com/oekaki/index.php
Second question:
Is there an easy way of migrating the oekaki over to the new server? The new server's in house while the old server's farmed out.
Thanks for the awesome work! >.<
~Xean45