ActionController::RoutingError apparently triggered from asset pipeline images #3838

Alamoz opened this Issue Dec 3, 2011 · 6 comments


None yet

4 participants

Alamoz commented Dec 3, 2011

I'm experiencing a problem with Rails 3.1.x. It is occurring only for a particular JQuery-UI-Listbox png image, the other images in the directory are apparently loading. Here are the errors I get when rendering a page that includes JQuery-UI-Listbox:

Started GET "/assets/images/ui-bg_gloss-wave_16_808080_500x100.png" for at 2011-12-02 17:57:38 -0800 Served asset /images/ui-bg_gloss-wave_16_808080_500x100.png - 404 Not Found (4ms)

ActionController::RoutingError (No route matches [GET] "/assets/images/ui-bg_gloss-wave_16_808080_500x100.png"):

rake assets:precompile has been run and the file ui-bg_gloss-wave_16_808080_500x100.png is present in /app/assets/images/jQuery-UI-Listbox/ and /public/assets/jQuery-UI-Listbox/. Very strange bug.

This problem is also affecting routing in those pages. When the "Logout" link is clicked (which redirects to logout_path), the page re-renders. Sometimes if you click "Logout" twice you can logout, and sometimes you simply can't log out when a JQuery-UI-Listbox is on the page. I haven't testing this to see if any other JQuery-UI widgets are causing this problem.


@Alamoz Is there still an issue here, or has it been resolved?

vijaydev commented May 5, 2012

Closing this. Please reopen if you find this still being an issue.

@vijaydev vijaydev closed this May 5, 2012
Alamoz commented Jun 3, 2012

I'm now experiencing it with Rails 3.2.5, though the page is rendering. This also is preventing the JQuery-UI List Box from rendering at all when running the app in development mode.

Alamoz commented Jun 3, 2012

Here is the log output:

Started GET "/assets/images/ui-bg_gloss-wave_16_808080_500x100.png" for at 2012-06-03 03:20:58 +0000
Served asset /images/ui-bg_gloss-wave_16_808080_500x100.png - 404 Not Found (31ms)

ActionController::RoutingError (No route matches [GET] "/assets/images/ui-bg_gloss-wave_16_808080_500x100.png"):
actionpack (3.2.5) lib/action_dispatch/middleware/debug_exceptions.rb:21:in call' actionpack (3.2.5) lib/action_dispatch/middleware/show_exceptions.rb:56:incall'
railties (3.2.5) lib/rails/rack/logger.rb:26:in call_app' railties (3.2.5) lib/rails/rack/logger.rb:16:incall'
actionpack (3.2.5) lib/action_dispatch/middleware/request_id.rb:22:in call' rack (1.4.1) lib/rack/methodoverride.rb:21:incall'
rack (1.4.1) lib/rack/runtime.rb:17:in call' activesupport (3.2.5) lib/active_support/cache/strategy/local_cache.rb:72:incall'
rack (1.4.1) lib/rack/lock.rb:15:in call' actionpack (3.2.5) lib/action_dispatch/middleware/static.rb:62:incall'
rack-ssl (1.3.2) lib/rack/ssl.rb:27:in call' rack-cache (1.2) lib/rack/cache/context.rb:136:inforward'
rack-cache (1.2) lib/rack/cache/context.rb:245:in fetch' rack-cache (1.2) lib/rack/cache/context.rb:185:inlookup'
rack-cache (1.2) lib/rack/cache/context.rb:66:in call!' rack-cache (1.2) lib/rack/cache/context.rb:51:incall'
railties (3.2.5) lib/rails/engine.rb:479:in call' railties (3.2.5) lib/rails/application.rb:220:incall'
railties (3.2.5) lib/rails/railtie/configurable.rb:30:in method_missing' unicorn (4.3.1) lib/unicorn/http_server.rb:531:inprocess_client'
unicorn (4.3.1) lib/unicorn/http_server.rb:606:in worker_loop' unicorn (4.3.1) lib/unicorn/http_server.rb:487:inspawn_missing_workers'
unicorn (4.3.1) lib/unicorn/http_server.rb:137:in start' unicorn (4.3.1) bin/unicorn_rails:209:in<top (required)>'
/usr/local/bin/rubydir/bin/unicorn_rails:23:in load' /usr/local/bin/rubydir/bin/unicorn_rails:23:in


Rendered /usr/local/bin/ruby-1.9.3-p194/lib/ruby/gems/1.9.1/gems/actionpack-3.2.5/lib/action_dispatch/middleware/templates/rescues/routing_error.erb within rescues/layout (52.1ms)


@Alamoz I too am having many problems with the asset pipeline in Rails 3.2.5. as a workaround (let us know if this works, as it helps diagnose the problem) try adding to application.rb:
config.assets.paths << Rails.root.join("app", "assets", "images")

I'm still having asset pipeline problems, but with the workaround Rails is now finding the assets

Alamoz commented Jun 10, 2012

No, that didn't work, the problem still occurs for me. Thank you for sharing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment