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 9199397
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T22:31:40+00:00 2026-06-17T22:31:40+00:00

RESTful resource, default type routes. Creating an event is supposed to work as follows:

  • 0

RESTful resource, default type routes. Creating an event is supposed to work as follows:

def create
    @event = current_user.events.build(params[:event])
    if @event.save
        redirect_to @event, :flash => { :success => "Event created!" }
    else
        render :action => "new" # new_event_path
    end
end

When invalid data is entered, it does render the “new” view/form again, but it renders this view at the “localhost:3000/events” URL, where the “index” action/view should be on.

My event routes seem like they ought to be pretty predictable:

    resources :events

I just updated to Capybara 2, began using DatabaseCleaner, and set transactional_fixtures to false in preparation for testing some JS-enabled functionality but can’t think of any other way I might have stuffed this up.

Is there some simple thing I’m missing that could cause a weird routing muck up like this?

Ideas, anyone, on where to start troubleshooting it?

  • 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-06-17T22:31:41+00:00Added an answer on June 17, 2026 at 10:31 pm

    This is the correct behavior. What is happening is that it is using the POST method for that URL when issuing the create action. Using a GET at the URL would be the index action. Also note that rendering a different template does not change the URL (that would require a redirect).

    Check out section 2.2 in the Rails Routing documentation:
    http://guides.rubyonrails.org/routing.html

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

Sidebar

Related Questions

My controller is using the default RESTful routes for creating, adding, editing etc I
I was wondering why when you create restful routes in rails with map.resources it
I have a model 'User', it's a restful resource, and has the default methods
I'm designing a RESTful web service utilizing ROA(Resource oriented architecture). I'm trying to work
I have a resource called patient_admissions that has all the RESTful routes. It is
Some RESTful services use different resource URIs for update/get/delete and Create. Such as Create
I am building RESTful mobile app and I like the default behaviour when resource
Using a restful resource in Rails, I would like to be able to insert
I have a RESTful resource in my Rails app called Photo. I'm using Paperclip
I've got a RESTful resource (let's say posts ) that excludes the index action.

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.