slugged | Super simple slugs for ActiveRecord 3 , with slug history | Application Framework library

Try use replaceAll function instead of replace.

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:

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:

To pass arrays in Rails (and Rack in general) as formdata you want to use empty brackets in the keys:

The double URLs are not a problem at all. It is used whenever the program renders views and has an API (perhaps for a mobile app) as well. What I usually do is have the id field be in the URL of the 'web' pages too, it is simpler for me to keep track of. However if you want to have a 'nice' slug in the URL, try this:

It seems like the server can't access to the content of the credentials.yml. This file is encrypted and Rails use the master key store in the master.key file to read it. So given that the master.key is not checked into version control, you need to provide it manually on the server. Please check this article https://medium.com/cedarcode/rails-5-2-credentials-9b3324851336

This section :

Deploying master key

When you move your code to a server, you need to make sure that your config/credentials.yml.enc file can be decrypted. That means that somehow you’ll need to provide Rails with your master key, given that it is not checked into version control.

There are two ways of doing that:

Option 1: Place the config/master.key file in the server. You’ll normally want to symlink this file to a shared folder in the server filesystem. Again, do not version your config/master.key file.

Option 2: create a RAILS_MASTER_KEY ENV variable. Rails will detect it and use it as your master key, e.g. in heroku: heroku config:set RAILS_MASTER_KEY=.

You should be able to use any of those indistinctly.

If you are using RBENV as you ruby manager, you can store your env var doing this :

You will create .rbenv-vars in your project folder, not your rails project folder but the folder in which is your project folder, the parent folder if you want.

After that you put your env var inside the file like this:

DATABASE_PWD=*****

no quotes, no space too before ou after the "="

For more check this link on goRails : https://gorails.com/deploy/ubuntu/18.04#capistrano

Hope this can help

You could try to set slug_limit like this from the test example:

The @ character is a reserved character in URLs, meaning it has a special meaning. If you want to use it as a simple part of the URL without the special meaning, it must be percent encoded first. See https://www.ietf.org/rfc/rfc3986.txt sections 2.1 and 2.2