> Don't make php scripts writable by webserver's user. Only scripts that > have to modified by webserver, have to writable. > I was just stating that I went so far as to try mode 777 on files and directories to resolve suggestion permissions issues. This change did not make any difference, so of course I put things back the way they belong.
> If you are using _any_ php cache/accelerator modules, restart apache if > you change something in your php scripts. > No cache/accelerator modules are installed. I've never had to restart apache in the past to add plugins. > 1. Make sure core SquirrelMail install is working. Yes, it's working. How do you think I got as far as I did? It works perfectly to read/send mail. It's just enhancing it with plugins and customization (one of SM's strongest features) that isn't working. > 2. Enable plugins one by one and check if they are working For now, I've disabled all plugins. I figure that once I resolve this timezone issue, I can then go back and turn them on one-by-one and see if things will work, debug as necessary, etc. > 3. Don't mix your squirrelmail installations Have not. This is a new install, not an upgrade. > 4. Enable php display_errors and error reporting = E_ALL while testing new > SM install. > I've done this. Now I just need to figure out where the error file is created...I will check archives and Google for any errors that I find. Something is definitely skewed. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click -- squirrelmail-users mailing list List Address: [EMAIL PROTECTED] List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
