Forum: Ruby on Rails image_column and permissions

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
E37ca8b3eee534fa6781f7ba13743afb?d=identicon&s=25 Ryan Wood (Guest)
on 2005-12-13 22:28
(Received via mailing list)
I recently started using image_column which has been donig a great job
in development (on WinXP using WeBrick). However once published to my
host (running Red Hat Ent.) uploaded images would no longer display
properly. I figured out that when the directories/files were created
did not have read rights. After chmoding them, it worked fine.

Is there a way to make sure that directories and files created are
permissioned as 644 rather than 600 by default?

--Ryan
E37ca8b3eee534fa6781f7ba13743afb?d=identicon&s=25 Ryan Wood (Guest)
on 2005-12-13 22:37
(Received via mailing list)
Sorry, I meant file_column.
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2005-12-13 23:05
(Received via mailing list)
Is this patch (against the file_column trunk) useful?
E37ca8b3eee534fa6781f7ba13743afb?d=identicon&s=25 Ryan Wood (Guest)
on 2005-12-13 23:35
(Received via mailing list)
That did it. Thanks! Will this be added into the trunk?
4bd34a2216dc8bdbf1f017f64e4d59e8?d=identicon&s=25 Kyle Maxwell (Guest)
on 2005-12-14 21:01
(Received via mailing list)
I submitted the patch, but Sebastian makes final decisions.
This topic is locked and can not be replied to.