slug for fields that are localized about mongoid-slug HOT 10 CLOSED

+1

from mongoid-slug.

+1

from mongoid-slug.

The best practice for this is to create an embedded collection titles that holds the localized name:

class Album
  include Mongoid::Document
  embeds_many :titles
end

class Title
  include Mongoid::Document
  include Mongoid::Slug

  field :language, type: String

  field :name, type: String
  slug :name

  embedded_in :album
end

Please let us know if that works for you.

from mongoid-slug.

I've just crafted an modified version of the original mongoid_slug that fit our needs. If anyone can test it and send some feedback it will be very welcome: https://github.com/comenta-tv/mongoid_localized_slug

from mongoid-slug.

@jschwindt I would like to understand this problem better. How would you ideally like localized finds to work? Do you always store one slug and then do a lookup in a hash for translations when calling to_params?

from mongoid-slug.

@digitalplaywright: I converted the slug attribute from a String to an Array and for every translations I store the corresponding slug in that array. Then the find method looks for any occurrence of the slug you are looking for regardless of its language. For example:

I18n.locale = :en
book = Book.create title: 'English title'
I18n.locale = :es
book = Book.create title: 'Título en español'
book.save

# now book contains:
book.title_translations   # { en: 'English title', es: 'Título en español' }
book.slug                 # [ 'english-title', 'titulo-en-espanol' ]

# the to_param method will generate the slug according to the language
I18n.locale = :en
book.to_param   # 'english-title'
I18n.locale = :es
book.to_param   # 'titulo-en-espanol'

# and the following find will return the same Book object:
b1 = Book.find 'english-title'
b2 = Book.find 'titulo-en-espanol'

b1 == b2  # true

Does it make sense to you?

from mongoid-slug.

@jschwindt That makes sense. How does this work with slug history? Also, why did you choose to use an array instead of an embedded colleciton?

from mongoid-slug.

I had to remove the history feature because we didn't need it in our project and because the code started to get a bit messy.

Regarding not using an embedded collection, I thought an array was simple enough for what I needed, easy to build, to add an index and to search on.

from mongoid-slug.

You can index and search on embedded fields in Mongoid, like e.g:

class Author
include Mongoid::Document
index({:'books.name' => 1})

end

Author.where("books.name" => "sewid").all

So you could index on two attributes in an embedded document: a field for the language and a field for the slug. However, if a domain specific slug implementation works well for your use-case I don't see any problems with that.

from mongoid-slug.

I will close this issue for now since embedded documents can be used for this purpose, and @jschwindts method can not be merged with master since it conflicts with core functionality.

from mongoid-slug.