friendly_id | permalink plugins for ActiveRecord

Coupon.friendly.find(params[:id]) allows both code and id to be used to find the record. If you switch to Coupon.find_by!(code: params[:id]) only the code will be able to find the coupon.

In that case you don't need Friendly ID at all, you can just continue manually generating the code and finding the record with it.

That will require a bit more work when generating forms that use the coupon or routes including the coupon as these will always use the integer ID by default - you'll have to explicitly pass id: coupon.code as an argument to the url/path helpers and pass url: my_path(id: coupon.code) or similar when creating forms.

The normalize_friendly_id is only called when using the slugged module to use a slug column to store and find by this column:

Since you're adding venue attributes to the user registration form, you may need to add these attributes to the strong_parameters list so they can be passed to the RegistrationsController#create action.

Devise's documentation shows how to do this: https://github.com/heartcombo/devise#strong-parameters

You have a combination of two problems:

1. You are literally passing the symbol :title to your .convert_slug method, so 100% of the time it just converts that to the string 'title' and returns it.
2. The first parameter to the friendly_id thing is not the slug, it is the name (string or symbol) of a method that will be called to obtain the slug.

So, because of #1 the first parameter is always the string 'title', which friendly_id then dutifully calls as a method and the result is your original title value.

Wrapping your code in another method will get you what you want:

When you boil it down, Rails routes are relatively simple patterns that match URIs and dispatch requests to the proper controller/method.

If you had specified your nested routes in their basic form:

Since Rails 5, belongs_to requires the presence of the associated parent object or it will fail validation when you save. In your code, you are calling build_profile to initialize a new Profile, but you don't appear to create an associated State object at that point.

One option would be to fully configure the associated objects at creation time. Another option is to define the association as optional:

Hmm; if I try bundle install with your Gemfile I get

Most likely you have some strong constraints on some particular gems in your Gemfile that's it's blocking bundle from updating a dependency.