It looks great in safari but kinda strange in ios simulator (i don’t have an iphone):
http://gyazo.com/8e157a1600728a4c7617e728f0112f50.png

I also tried this: request.env['firebug.logs'] = [[:info, "hello from rack!"]] within a controller.

I’m using rails 2.3.5

You are absolutely right! My mistake, fixed now.

I did that and it get back to normal, actually every rack middleware
I’ve enabled ran into the same problem, I also tried with a blank rails application.

I’m pretty sure that it’s a bug of rails and rack. I’m still using rails 2.3.5, so that I don’t know if it still happens at rails 3.

Rails 3 still autloads everything in the ‘lib’ directory, so that shouldn’t be the problem. You can confirm this by loading the console and typing:

firebug = ::Rack::FirebugLogger.new(”")

It looks like you can just call ‘use’ inside of the ApplicationController in Rails 3 instead of adding a config line to development.rb.

class ApplicationController < ActionController::Base
use Rack::FirebugLogger
end

However, I just tried it and I get an error the second time the middleware is used. Once Rails 3 comes out of beta I will update the middleware to work properly and update this post.

Try disabling the middleware piece (just comment out the line added to development.rb) and restart the application. If you still get an unknown action error then its not firebug_logger’s fault.

Let me know what happens, I’ll be glad to take a look at it otherwise.

I have followed you instructions but I cannot get the autoloading “xxx/lib/rack/firebug_logger.rb” after running this in my dev env

config.middleware.use ::Rack::FirebugLogger

I’m using rails 3 – is there some extra trick?

thanks! x

The middleware works fine, until you try to map a route from within a namespace just like the following:

map.namespace :admin do |admin|
admin.resources :subjects do |subjects|
subjects.resources :topics do |topics|

end
end

Whenever I try to access “admin/subjects/1/topics” URI, it throws an unknown action error.

I’ve tried to debug by putting a “return @app.call(env)” into call method, it keep throwing though, therefore I think it’s a Rack bug.