4 Commits (5c3c69b4a5dfb8c9428b61f67347db0fc1b935de)

Author	SHA1	Message	Date
Felix Schäfer	b0cfd3b952	Correctly deserialize current data in custom field translation migration	12 years ago
Jens Ulferts	4e07a913c9	possible_values of custom_fields are now localizable	13 years ago
Jens Ulferts	74c9bc2896	enabling default_value of custom_fields to be localized by admins ... * tabular_form_builder also accepts :single_locale option which will cause the builder to generate a field based on the english localization. There will be no option to add or delete localizations for this field. Doing this means that the field will be equal accross all languages as en is always the default fallback	13 years ago
Jens Ulferts	7178c1b3b7	enabling name attribute of custom_fields to be localized by admins ... * using globalize2 for backend * overriding some AR methods in CustomField in order for them to work * with globalize ** validates_uniqueness_of works on translations table now. Should not be necessary any more when switching to globalize3 ** translations_attributes setter method as globalize2 does not work with nested_attributes by default * extending the tabular_form_builder to generate localizable attributes * as soon as :multi_locale => true is passed on a field	13 years ago