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

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 7, 20262026-06-07T20:13:50+00:00 2026-06-07T20:13:50+00:00

I have devise set-up, and it works great when a new user is going

  • 0

I have devise set-up, and it works great when a new user is going through the registration process themselves but before implementing Devise, admin had the ability to create users and behavior related to that was in my old users controller. Now that I am using devise when I visit my old forms, new action triggers fine but when I actually submit the form, no matter what I do it goes to the Devise’s registration controller create action. I know that I can override the controller and copy the code that I had in my old users controller there but I was wondering if there was a way to prevent this behavior on certain calls?

I have tried specifying the controller and the action for the form specifically and it did nothing.

Here are the two relevant paths as defined in my routes:

                                         POST   /users(.:format)                                                           users#create
                       user_registration POST   /users(.:format)                                                           users/registrations#create

Am I going about this wrong?

  • 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-07T20:13:52+00:00Added an answer on June 7, 2026 at 8:13 pm

    Usually, I’ll create a separate controller for admin CRUD related to users when I’m using devise. Something like:

    # /app/controllers/admin
    class Admin::UsersController < ApplicationController
      # your controller actions
    end
    
    # config/routes
    namespace :admin do
      resources :users
    end
    

    I find separating it all makes it more maintainable and makes for less headaches.

    Update:
    Devise adds it own routes and route helpers, so your user_registration_path and POST /users are being superseded by the routes given in devise, which in this case is also a POST to /users. You can find the source for these routes on github: https://github.com/plataformatec/devise/blob/master/lib/devise/rails/routes.rb

    A side note: the two paths that you referenced in your question are the same thing, just the second one will be accessible through a route helper, ie user_registration_path or user_registration_url and the other most be referenced directly.

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

Sidebar

Related Questions

I have a sample Rails 3.1.1 application that I have set devise up to
I have two devise models: User and Member As such, I'm specifying authentication keys
I have a devise user model with pro boolean column.I want to build a
I'm working with Rails 3.2.2. And I have a devise model called user. In
I've set up Devise to manage the authentication to my app. I have a
I have a simple Ability.rb set up listed below: if user.role? :super_admin can :manage,
I am using devise but the User model is related to a legacy table
I have a users model with Devise, and I've set up roles so users
I have set up a test applications and have setup devise to take care
I have been using devise for authentication and cancan for authorization in my application.

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.