How do I expire a view cached fragment from console?

Question

Something like

Rails.cache.delete('site_search_form')

doesn't seem to work. Is this possible? Thanks.

What version of Rails are you running? The cache delete method was added in 2.1. — vrish88, Apr 16 '09 at 16:32

score 55 · Answer 1 · answered May 08 '09 at 05:12

55

ActionController::Base.new.expire_fragment(key)

answered May 08 '09 at 05:12

2

ruby-1.8.7-p334 :007 > ActionController::Base.new.expire_fragment(:controller => 'main', :action => 'index') NoMethodError: undefined method `host_with_port' for nil:NilClass – pixelearth Sep 05 '11 at 01:00
1

As of Rails 3, fragment caches have a hash at the end, which is based on the contents of the view in which they are generated. This is so the cache is automatically busted if the view changes, but it makes it difficult to expire by key. You can tell Rails not to add the hash with `skip_digest: true` in the cache call. More info: https://www.reinteractive.net/posts/197-if-you-explicitly-expire-cached-fragments-opt-out-of-cache-digests – stephen.hanson Dec 08 '16 at 19:35

score 6 · Accepted Answer · edited Jul 13 '19 at 03:52

6

Cache fragment entries are created with a slightly different key than what you access with Rails.cache.

Use expire_fragment instead (you can send it to a controller): http://api.rubyonrails.org/classes/ActionController/Caching/Fragments.html#M000438

edited Jul 13 '19 at 03:52

Dave Powers

2,051
2
30
34

answered Apr 16 '09 at 16:44

Terry

1,088
6
10

This doesn't work for me. If this doesn't work for you too try `Rails.cache.delete_matched 'views/site_search_form*'` – yivo Aug 15 '16 at 18:40
As of Rails 3, fragment caches have a hash at the end, which is based on the contents of the view in which they are generated. This is so the cache is automatically busted if the view changes, but it makes it difficult to expire by key. You can tell Rails not to add the hash with `skip_digest: true` in the cache call. More info: https://www.reinteractive.net/posts/197-if-you-explicitly-expire-cached-fragments-opt-out-of-cache-digests – stephen.hanson Dec 08 '16 at 19:34

score 2 · Answer 3 · answered Jun 14 '14 at 14:45

2

Rails.cache.delete "views/site_search_form"

answered Jun 14 '14 at 14:45

d0minikk

49
3

score 0 · Answer 4 · answered May 26 '17 at 17:24

In Rails 5 I took the following steps to bust the cache without resorting to skip_digest: true. Our problem was that changing the value of I18n strings does not reflect in the computed cache digest so the cache would not get busted automatically.

Here is the view where the cache block is defined:

/ views/layouts/_footer.html.slim
- cache :footer do
  span= t('shared.footer')

Then in rails console I run:

fragment = ActionController::Base.new.view_context.cache_fragment_name(:footer, virtual_path: 'layouts/_footer.html.slim')
ActionController::Base.new.expire_fragment(fragment)

cache_fragment_name will figure out the digest based on the virtual_path keyword argument.

This is now outdated. `virtual_path` is not a valid option in rails 6.1+. — Peter P., Jun 08 '23 at 17:04

score 0 · Answer 5 · answered Jun 08 '23 at 17:03

Another option, if you are using Redis as your cache store, is to search and delete from redis directly using the keys method.

# get direct Redis client from Rails cache store
redis = Rails.cache.redis

# search for your key
keys = redis.keys.grep(/site_search_form/)

# delete the keys
keys.each do |key|
  redis.del(key)
end

How do I expire a view cached fragment from console?

5 Answers5

Linked