Hi Dave! Yes, I've seen the permissions setup be a pain point for several people. That's why we've tried to document the options well, but I do know that certain people still have issues (especially if you're not on a mac).
The problem with having a task that 777's the cache directory is that this will only work temporarily. Symfony, by default, will continue to generate cache files that are *not* 777, so eventually you'll always end up with files in your cache directory that aren't 777. This is different from symfony1, which, I believe, created new files as 777. So, ultimately, you need to force 777 via umask or properly deal with the fact that your web server user and shell user both need to write to the same set of files that are not 777 (e.g. using same user for both, ACL, etc). Did you try the solutions covered in the documentation? And if so, what didn't work? Thanks! Ryan Weaver US Office Head & Trainer - KnpLabs - Nashville, TN http://www.knplabs.com <http://www.knplabs.com/en> http://www.thatsquality.com Twitter: @weaverryan On Sun, Jul 31, 2011 at 3:39 PM, dave08 <[email protected]> wrote: > I'm relatively new to symfony2 (after having developed a large app in > 1.4...). I must have spent hours trying to find the solution to this > problem until I found issue 1222 in github that was closed and this > thread. I think have I simple temporary solution that is the > contiuation of what everybody expects from symfony 1, which is to have > an app/console application:permissions task (or similar), for those > ready to be 777ed. This has always worked in symfony 1, and I find it > a terrible pity for those that don't care to make it 777ed, to have to > waste hours on this problem... Thanks! > > -- > If you want to report a vulnerability issue on symfony, please send it to > security at symfony-project.com > > You received this message because you are subscribed to the Google > Groups "symfony developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
