Home/ Questions/Q 6600321
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T18:36:26+00:00

I’ve upgraded an app to Rails 3.1, and everything is setup and working correctly

  • 0

I’ve upgraded an app to Rails 3.1, and everything is setup and working correctly except that an image_tag isn’t finding the image. I’ve moved all my images from public/images to app/assets/images. The browser requests an image at http://localhost:3000/assets/foobar.png but it just shows up as a broken image in Chrome. Opening it in a separate tab says “No route matches [GET] “/assets/foobar.png”.

I feel like I’m just missing some setting somewhere, but I haven’t been able to find out what it is yet. Any suggestions?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    One of the biggest things they don’t mention in the Assets Pipeline Guide is to remove the leading /images/ part of the path. So for example this:

    <%= image_tag "/images/about/header.png" %>

    Would have to be changed to this:

    <%= image_tag "about/header.png" %>

    Same goes for CSS files. So this:

    background-image: url("/images/alliance/header_background.png");

    Would change to:

    background-image: image-url("alliance/header_background.png");

    Note that when using the asset pipeline never include the leading slash. Also if you use the above line of code in your CSS file, be sure to add .scss to the file (so application.css would become application.css.scss).

    Hope this saves you some headache!

    • 0