…ther argument error if a block is supplied
…tiveRecord::Base.with_locale and make ActiveRecord::Base#attributes= accept a virtual :locale attribute.
…t have been duplicated in I18n. Only model translations related features will remain in Globalize2.
set to false. This is the case in development mode. The problem occurs,when the proxy class (e.g TagTranslation) exists already when gloablize wants to create it.
…ready. Due to rails lazy class loading using const_missing I try to load the proxy class, if that fails I create a new one. After that, append the globalize methods to the class. I did not find a way to reproduce this error with a unit test. So here is how you can reproduce this: 1. Have a model that needs translation (e.g Tag) 2. Create a TagTranslation model and add a custom method to it (e.g slugname) 3. ruby script/console 4. Tag.new (Tag class is loaded and proxy class is being created) 5. TagTranslation.new.respond_to?(:slugname) => false but should be true
* fix issue with active_support/dependencies class reloading * do not raise an exception on missing translations in static backend (dubious change) * add a clear_cache method, only clear the cache on reload (i.e. keep the stash) (dubious change) * add a translated_attributes method
…e_proxy.table_name instead of evaluating it.
… not pull because I rewrote the tests quite a bit so its more readable.
…e handed to create_translation_table!