I'm not sure this is a Rails problem.  Most web apps have an 'images'
directory under the public web root.  If you send a request to a URL
that looks something like http://example.com/images/foo then your web
server is going to interpret that to mean you want it to serve the
static image file named 'foo' from the images directory.  The request
shouldn't even make it to your application.

I don't know if that's the problem you're having, but it seems like
enough of a reason to not have an 'images' resource.

On Aug 28, 4:17 am, Jarl Friis <[email protected]> wrote:
> Hi.
>
> I can't be the only one in the world having the wonderful idea to have
> a resource named "image".
>
> I have a controller named images_controller
> I have a route named "image", and therefore a helper called
> image_path(id).
>
> But using image_path in an action view erb file gives problems, there
> another helper named image_path[1] is defined, hence I can no longer
> use the named route url helper image_path
>
> For now I have changed my routes.rb from
> map.resources :images
> to
> map.resources :images, :singular => "my_image",
>
> Then I can use my_image_path in action views.
>
> But... Isn't image such a common word for a resource that [1] should
> have a different name, e.g. asset_path, image_asset_path, or something
> else. There is already an alias path_to_image[1]. How about just stick to
> that?
>
> What do you say?
>
> There are some others having this problem: [2]
>
> Jarl
>
> Footnotes:
> [1]  http://api.rubyonrails.org/classes/ActionView/Helpers/AssetTagHelper....
>
> [2]  http://forums.pragprog.com/forums/59/topics/2723
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" 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/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to