friendly_id-mobility issues

History only for current locale

3

When using this nice gem with the history option I found that the translated slugs where not being saved. I checked the issues opened and found #10 is my problem,...

0urobor0s

query_field can be a symbol, but mobility_attributes are strings

Bug fixed.

mrbrdo

allow translated and non-translated slugs with history in the same project

2

Solves #27 by loosen the `locale` constraint and taking the :mobility plugin usage into account for each `sluggable`.

thedarkside

This gem prevents using friendly_id with non-translated slugs on some models of the same project

This gem adds a `locale` column to the `friendly_id_slugs` table with `null: :false`. This way it enforces slugs being translated project wide. If one wants a translated slug with history...

thedarkside

Make sure to always take slug_column as string

## Description Using friendly_id-mobility I came to this error: [FriendlyId] You need to translate the 'fieldA' field with Mobility (add 'translates :fieldA' in your model 'modelA') But translation for 'fieldA'...

adrianryt

Fix/should generate new friendly

2

adrianryt

Remove unsupported/explicit after: :scope in migration generator template

Closes #35

khalilgharbaoui

Error due to unsupported/explicit after: :scope in migration

This seems to be unsupported now and in any case its not strictly mandatory to explicitly define column position using `after:`. https://github.com/shioyama/friendly_id-mobility/blob/45392451cdafc5adb90bce5fad9385f03f505edb/lib/generators/templates/migration.rb#L3 Without specifying the position, the new column will...

khalilgharbaoui