NineChime forum
Furry stuff, oekaki stuff, and other stuff.
You are not logged in.
- Index
- » Wacintaki support
- » Sorry, the BBS e-mailer isn't working.
Post a reply
Topic review (newest first)
- China
- 12-09-2006 02:28:49
Ah, it works! Thanks so much, you're a life saver. 
- Waccoon
- 12-09-2006 01:51:03
OK, it should be working, now.
The security model is a bit weird. If the files are created by the server (CHOWN to PHP), the permissions should be 644, and you cannot change the file permissions from your FTP client. This is normal. However, if you upload files to the server via FTP, they must be CHMOD to 666 for them to be unlocked. This is because the public (not just security groups) need write permissions. So, if you upload any files in the future, make sure you use a CHMOD of 666.
Folders also need public write permissions, but they also need to have execute permissions, or else PHP won't work and people will be greeted with a 403 Forbidden error. So, CHMOD uploaded folders to 777.
- China
- 12-08-2006 14:46:16
1. Right.
2. Windows XP
3. Believe so. It's currently set to 755.
4. Tried changing config/dconn to 775 on FTP. Still locked. Tried changing them to 770. The oekaki pages turn white and "Cannot open database file." Changed them back to 775.
I'll e-mail you.
- Waccoon
- 12-08-2006 05:22:06
OK, I need to confirm a few things...
1) You copied the files to your computer, deleted the ones on the server, re-uploaded the files, and CHMOD them... and PHP still says they're locked, right?
2) You're not running UNIX/Linux. What OS is on your server? Windows? MacOS X?
3) Is the root folder ("oekaki/") writable? Don't change it! Just tell me if it is or not. I don't know if changing the CHMOD of the root will lockout your whole oekaki.
4) Have you tried permissions a bit less restrictive? What happnes if you use 775 on the config and dbconn files? What about 770?
To me, this sounds like a CHOWN issue, and deleting the files from the server (if you can actually do that) should solve the problem. If not, you may have no choice but to contact an admin and ask them to fix it so both your FTP account and PHP can write to them.
With an FTP login, I could take a look, too. Security resolution has a lot to do with how the server is set up. Some servers are really weird.
- China
- 12-07-2006 19:14:11
I'm not on Linux/Unix. 
So I tried deleting them on FTP, uploading them and changing permissions. Still "locked" as far as changing permissions on how approval goes. Tried deleting them and uploading them on the file server and changing permissions there. Ran reclaim:
Warning: rename(dbconn.php,dbconn_old.php) [function.rename]: Permission denied in /home/jinx/public_html/oekaki/reclaim.php on line 22
FAIL: Cannot delete temp file dbconn_old.php
Warning: rename(config.php,config_old.php) [function.rename]: Permission denied in /home/jinx/public_html/oekaki/reclaim.php on line 22
FAIL: Cannot delete temp file config_old.php
OK: resource/ips.txt
OK: resource/hosts.txt
OK: resource/banner.php
OK: resource/notice.php
OK: resource/rules.php
Error when I try to edit avatars:
Warning: fopen(avatars/77f43ba0149502a9052e39d95c6b9b4b.gif) [function.fopen]: failed to open stream: Permission denied in /home/jinx/public_html/oekaki/edit_avatar.php on line 90
Warning: Cannot modify header information - headers already sent by (output started at /home/jinx/public_html/oekaki/edit_avatar.php:90) in /home/jinx/public_html/oekaki/common.php on line 92
- Waccoon
- 12-05-2006 03:22:14
Ouch. If you can CHMOD the files in an FTP program, you might have to back them up on your computer, delete the files from the server, re-upload them, and CHMOD them to either 660 or 664. That will flush out any CHOWN permissions.
Note that the avatars folder should be CHMOD to 775, not 664. If you remove the avatars folder from the server and re-upload it, set the folder to 775, and then EVERY file in the folder must be CHMOD to 664. Otherwise, people will not be able to change avatars.
If you can't CHMOD the files, or if the files are still locked no matter what you do, you might have to ask your sysadmin to change them so they are writable to both PHP and your FTP account.
Sometime UNIX/Linux is a real pain in the butt.
- China
- 12-04-2006 09:38:46
I just realized that now my files are locking me out too (no idea why). I ran reclaim.php:
Warning: rename(dbconn.php,dbconn_old.php) [function.rename]: Permission denied in /home/jinx/public_html/oekaki/reclaim.php on line 22
FAIL: Cannot delete temp file dbconn_old.php
Warning: rename(config.php,config_old.php) [function.rename]: Permission denied in /home/jinx/public_html/oekaki/reclaim.php on line 22
FAIL: Cannot delete temp file config_old.php
RECLAIM: resource/ips.txt reclaimed. Should now be writable.
RECLAIM: resource/hosts.txt reclaimed. Should now be writable.
RECLAIM: resource/banner.php reclaimed. Should now be writable.
RECLAIM: resource/notice.php reclaimed. Should now be writable.
RECLAIM: resource/rules.php reclaimed. Should now be writable.
Failed! If you're using Windows, wait 15 seconds and run this file again.
If using UNIX/Linux, check that there are no temp files and the original config files are named properly.
Tried CHMODDING those two files and ran reclaim again. No dice. My diagnostics currently:
./ Locked
./pictures/ OK
./templates/ OK
./resource/ OK
./avatars/ Locked
./config.php Locked
./dbconn.php Locked
./resource/banner.php OK
./resource/hosts.txt OK
./resource/ips.txt OK
./resource/notice.php OK
./resource/rules.php OK
- Waccoon
- 12-03-2006 04:20:00
Your config files are not writable, so the config changes can't be saved.
Either CHMOD the "config.php" and "dbconn.php" files to 664 in your FTP program, or copy the "reclaim.php" file from the documentation folder of the Wacintaki distribution to your server and run it.
To make sure everything is writable, log into the board as the owner and then view "testinfo.php". This is a diagnostics page that will let you know if any other files are not writable.
- China
- 12-03-2006 00:51:24
We never had to e-mail them manually before.
Well I tried to enable "No(forced)" and got this error:
Warning: fopen(dbconn.php) [function.fopen]: failed to open stream: Permission denied in /home/jinx/public_html/oekaki/cpanel.php on line 169
Warning: Cannot modify header information - headers already sent by (output started at /home/jinx/public_html/oekaki/cpanel.php:169) in /home/jinx/public_html/oekaki/common.php on line 92
- Waccoon
- 11-30-2006 05:33:46
If you approve accounts manually and the server e-mailer isn't working, the board will let you know e-mails can't be sent, and will prompt you to notify people manually, as well.
If you have "No (forced)" selected in the control panel, people will have their accounts automatically enabled as soon as they register.
Registrations are just a pain if the server can't send e-mail.