Closed flynfish closed 8 years ago
I've also come across this issue with the following setup: Rails 4.2.0, Puma 2.8.2, Resque 1.25.0
This happened while we mounted resque-web in our application.
Its happening because all the controllers in resque-web are extending 'ApplicationController' instead of 'ResqueWeb::ApplicationController'.
Because of this, helpers are not being included and thats causing this issue.
I "fixed" this by putting ResqueWeb::Engine.eager_load!
in my routes.rb.
@mvlwn +1 for the eager_load! work around; I can vouch for it working locally and in heroku.
eager_load!
also worked for me
@mvlwn +1
Thanks @mvlwn !
Same here, will this get fixed or at least worked around if its Rails specific?
@hakunin : this is fixed in this PR: https://github.com/resque/resque-web/pull/79 (by @jdatti ) and a work around is to put ResqueWeb::Engine.eager_load!
into your routes.rb ( as mentioned by @mvlwn )
Once there is a new version of the Gem released, then the fix should come with it!
I released a new version of the Gem, which I believe should fix this issue. Please upgrade and feel free to reopen this issue if its still a problem.
I get this error very frequently just going to
localhost:3000/resque
and I have to restart the app. Once it is restarted, that webpage works again.