Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6756439
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T13:31:26+00:00 2026-05-26T13:31:26+00:00

I just upgraded to rails 3.1 and is getting a weird routing problem with

  • 0

I just upgraded to rails 3.1 and is getting a weird routing problem with resque-web

I’ve mounted resque-web on my routing.rb like this:

mount Resque::Server, :at => "/resque"

when my server is up going to 0.0.0.0:5000/resque works fine but declaring the path ‘resque_path’ in my erb.html files gives me

undefined local variable or method `resque_path' for #<#<Class:0x000001038e9eb0>:0x000001038a7650>

it’s even listed on my rake routes as:

resque_server        /resque                     {:to=>Resque::Server}

‘resque_path’ should be working! i hav no idea why it is now. anyone?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T13:31:27+00:00Added an answer on May 26, 2026 at 1:31 pm

    Have you tried resque_server_path? That could do it.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I just upgraded to Rails 2.3.2.1 running Litespeed web server 4.0.5 and get the
We just upgraded our app to Rails 3.2.2 and are now having a routing
I just upgraded an existing rails 3 app to rails 3.1 I get this
I just upgraded my rails to 2.3.4 and I noticed this with validations: Lets
I just upgraded to rails 3 and face a problem handing over a link
I just upgraded to VS2008 Sp1, and I have a weird issue going on.
I just upgraded my application from Rails 2.3 to 3 and I'm getting some
I just upgraded to Rails 3.2.0 and get this error after signing up to
I just upgraded from Rails 3.0.3 to 3.2.1. The upgrade went smoothly on my
I just upgraded my Leopard system to Snow. I had a Rails application with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.