[Radiant] /admin problems

[Ruben D. Orduz]

Yup. I usually use the recursive flag because I'm sure with all
metaprogramming Rails does it probably uses tmp directories a lot. Not
to mention session storage and management. So even though this time
was easy to isolate to /tmp/sesh it's just better to chmod the whole
folder and its children.



On 11/29/06, Sean Cribbs <seancribbs at gmail.com> wrote:
>
>  I usually get that problem with new Rails applications when the tmp/
> directory doesn't exist (especially if I checked them out of an SVN repo).
> Go to the root of your Radiant installation and run `rake tmp:create` .  If
> it's already there, you may have to chmod -R.
>
>  Sean Cribbs
>  seancribbs.com
>
>
>  Daniel Sheppard wrote:
>  Actually, it needs read/write access to tmp/sessions (actually, all of
> tmp)
>
>
>
>  -----Original Message-----
> From: radiant-bounces at lists.radiantcms.org
> [mailto:radiant-bounces at lists.radiantcms.org] On Behalf Of
> Ruben D. Orduz
> Sent: Wednesday, 29 November 2006 2:23 PM
> To: radiant at lists.radiantcms.org
> Subject: Re: [Radiant] /admin problems
>
> It seems that you need to give Apache read/write access to the script
> folder. sudo chmod -R 755 ./script should help.
>
> On 11/28/06, John Furfey <jfurfey at mbl.edu> wrote:
>
>
>  Here it is:
>
> Permission denied -
> script/../config/../tmp/sessions//ruby_sess.b794dd418e29357b
>
>  _______________________________________________
> Radiant mailing list
> Post: Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
>
>
>
>
> _______________________________________________
> Radiant mailing list
> Post:   Radiant at lists.radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site:
> http://lists.radiantcms.org/mailman/listinfo/radiant
>
>