refinery/refinerycms-settings

deleted settings are cached in the front end until another setting is created

gajeev opened this issue · 1 comments

  1. Through the admin backend I create a setting call s1 and set it to true
  2. I look at <%= debug ::Refinery::Setting.get(:s1) %> and I get ---true ...so far so good
  3. I then delete the setting through the admin back end and reload the view and I still get ---true - even though looking at the refinery_settings table the record is gone, i've even tried restarting the rails server process
  4. If I then create a new arbitrary setting called something else and then reload the <%= debug ::Refinery::Setting.get(:s1) %> view, I now get --- !!null - which I was expecting in step 3

fixed with c3207dd