Posted on: 05/22/02 08:27am
By: Anonymous (Mike)
I continue on getting these errors at the top of my story pages. I have read the FAQ and noticed that it usually has something to do with CHMODing certian directories to 775. I then did it and the errors continue on coming up. Should I delete my GeekLog files and do a new install?
Well...
Posted on: 05/22/02 08:50am
By: Tony
Remember, the key to all the chmod'ing is to allow your webserver user the ability to write to logs/, backups/, public_html/backend, public_html/images/articles and public_html/images/userphotos. If your files aren't owned by the webserver or don't belong to a group that the webserver user belongs to then chmod 775 will not work. If you are on a hosted environment you may have to chmod 777 if you can't chown -R <yourusername>:<webserveruser>.
Well...
Posted on: 05/22/02 08:56am
By: Anonymous (Mike)
I am running everything off of my own dedicated server. I have CHMODed everything to 777 as of now and I still get the errors. I have even gone through and CHMODed every GeekLog directory and everything leading into the GeekLog files. Nothing seems to make the errors go away.
Well...
Posted on: 05/22/02 09:19am
By: Tony
post the errors.
Well...
Posted on: 05/22/02 09:31am
By: Anonymous (Mike)
Warning: Supplied argument is not a valid File-Handle resource in /home/virtual/site9/fst/var/www/html/php/lib-common.php on line 741
Warning: Supplied argument is not a valid File-Handle resource in /home/virtual/site9/fst/var/www/html/php/lib-common.php on line 742
Warning: Supplied argument is not a valid File-Handle resource in /home/virtual/site9/fst/var/www/html/php/lib-common.php on line 743
Well...
Posted on: 05/23/02 07:04pm
By: Anonymous (Anonymous)
I am getting the same errors on one of my hosted websites. It was originally running the 1.3.5rc1 version fine and I installed the 1.3.5 stable version and the errors appeared. Maybe this info will help point to the problem.
Jim