Custom view violates strong parameters

[cmaxw]

Custom view violates strong parameters

[cmaxw]

Yeah, I pulled all that stuff out and changed everything back to match the engine except the look/feel. That fixed it.

Set up a UserProfile class to manage that other stuff.

[kobaltz]

ActionAuth::User isn't a great place to store additional attributes. However, if you wanted to do this, you would need to override the controller's user_params method found in app/controllers/action_auth/registrations_controller.rb.

It may be better to have a "wizard" style of sign up, where you can sign up the user then get the user's first_name, last_name, etc in a turbo_frame_tag. We may need a PR for a configurable option of redirect_after_signup to handle this without overriding the controllers.

[kobaltz]

Alternatively and a perhaps easier method is having an "Additional Attributes" model (like UserSetting) that will store the first_name, last_name, etc. In your application_controller, you could check if the User is signed in and if they have finished setting up their profile. If they have not, then redirect to their edit user settings page.

[cmaxw]

I tried overriding the controller in the main Rails application and only overriding the private method for user_params caused it to tell me that it couldn't find the method for the create action.

I'll back out the extra parameters, but I'm still getting the unpermitted params on :authenticity_token and :button. I'll post where I end up and see if there's something else we can do to make it work.

[kobaltz]

I put together a sample application which adds in Action Auth and then a model for User Settings. This should help you compare what's working with this branch and your code base. In this example, I also added a check in the ApplicationController to see if the user has updated their user settings already and if not then it takes them to this page.

https://github.com/kobaltz/action_auth_example