Setting.save_default does not work when defaults[] is used in the model about rails-settings-cached HOT 2 CLOSED

I was baffled by the same issue but I believe I have found the cause and a (sort of less than ideal) solution.

It appears this problem is being caused by spring which keeps the Rails application loaded and therefore keeps the cache around. I had truncated the settings table at some point so I could reset it with new defaults. Afterwards my new settings weren't taking in the application or showing up in the database so I tried to mimic the behavior of #save_default but with some extra output by doing the following

if Setting.application_title.nil?
  puts 'Setting application_title.'
  Setting.application_title = 'My Application'
end

just to make sure something weird wasn't going on. Setting.application_title wasn't returning nil so the setting wasn't being set. I discovered that when I added Rails.cache.delete('settings:application_title') before the above that it worked just fine. So of course the normal call to #save_default worked just fine as well. So if you're using spring (which ships with Rails 4.1 by default) you might need to clear the cache for your settings before you use #save_default.

from rails-settings-cached.

@seaneshbaugh Thank you very much for this. I had the same problem and your explanation saved me.

from rails-settings-cached.