Me too. Not the first time, but first I had time to grab a screen shot and report in with an image. Aarrggh. It gives me the same error on the Wagn.org site. Had to upload as a file as in the +example above. --bw

well, this is "fixed" in the same way that it was last time, in that I changed the permissions on the directory that was causing the problem. It now looks like something is resetting the permissions, presumably every time we deploy new code (which we did recently with some minor changes including that ampersand fix).

So I need to find a deeper fix to prevent this from happening, but until then I will make sure to change this by hand every time I deploy.

  --Ethan McCutchen.....Wed Nov 24 15:07:31 -0800 2010

I tweaked the deploy code and it appears to have fixed the permissions problem that was behind this error. Just did a new deploy and the directory has the correct permissions. With luck we won't be seeing this error again any time soon.

  --Ethan McCutchen.....Fri Dec 03 14:35:02 -0800 2010

MOST excellent.

  --Brandon WilliamsCraig.....Fri Dec 03 15:36:35 -0800 2010