search for: action_suffix

...bar?page=2 2.) If the above is true and I have an authentication system built into my app, if 2 separate users go to their own example.com/foo/bar?page=2, will it have the separate fragment caches for each user? or is that something I need to build into the auth system? Something like make each :action_suffix unique by adding in their id for example? But I do use say their unique id as the :action_suffix, what if I have multiple fragments per page and each needs a unique identifier in order for me to expire them or can I specify more than one :action_suffix? Thanks in advance. --~--~---------~--~---...

Hi, In my view I have the following cache: <%- cache(:controller => ''products'', :action => ''index'', :action_suffix => ''footer'') do -%> ... <%- end -%> And that''s the file generated: tmp/cache/views/www.mysite.com/products.action_suffix=footer.cache Why isn''t fragment caching picking up the :index option, and incorrectly making use of action_suffix? According to...

...but not for domain.com. I don''t want it to store two different cached fragments for www and non- www, as they''re exactly the same. I also want both the www and non-www page to expire. Should I do something like cache(:action => ''...'', :subdomain => false, :action_suffix => ''...'') and do the same for the expire_fragment part? Or is there a better solution? Thank you! -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA3...

Hello, I am trying to invalidate a cached fragment. My fragment looks like <% cache ( :controller=>''users'',:action=>''additem_to_cart'',:action_suffix=>@user.id) %> At this point,rails has created 2 cache files correctly and everything works fine becuase I dont see rails making calls to the SQL db to get items from DB.Instead it uses cache. Now in def add_item_to_cart expire_fragment ( :controller=>''users'',:action=&gt...

Hi Railers, I am trying to create a simple application like a guest book which has users and uses sessions to keep track of which users are logged on. The user''s page is constructed after doing some SQL queries and the user clicks on another link and hits the back button I dont want to regenerate the whole page (which is what happens now) .So I want to use some kind of caching mechanism.