[eluser]CheekyGeek[/eluser]
The solution to this problem in an earlier thread was to make the system/logs file world-writable (777) Making folders in web space world-writable (777) is
never a good idea (unless you like redirect spammers coming along and installing potentially embarrassing stuff inside your web space). DAMKIKT
Not sure if Windows users have this problem, but the (more secure, I think) fix on a UNIX-based system is to change the GROUP ownership on the logs file to the web server user. If you are using Apache, you'll find it defined in the httpd.conf. On Macs, it is: www.
Code:
chgrp www /path/to/your/codeigniter/system/logs
If the logs folder is owned by root, you will need to instead:
Code:
sudo chgrp www /path/to/your/codeigniter/system/logs
(and authenticate). Next you need to modify the read/write/execute permissions on the logs folder so that the web server user has full access:
Code:
chmod 775 /path/to/your/codeigniter/system/logs
.
Now you can set your config.php file log_threshold to something other than zero and the application still works, but you haven't left it world-writable for spammers.
Hope someone finds this useful.
