Andrew Neil wrote:
A better solution would be to create a new model called StorePage,
inheriting from Radiant's Page model.
*snip*
This belongs in the wiki!!!
Cheers,
Mohit.
6/14/2009 | 12:07 AM.
___
Radiant mailing list
Post:
This is an old thread that I have been meaning to follow up. Sean suggested:
that one
should focus on the _why_ you need an uncached page in the first
place, and address that need first
I wanted to provide an example of why I needed to have a page not
cached and see if there was a better way
This is an old thread that I have been meaning to follow up. Sean
suggested:
that one
should focus on the _why_ you need an uncached page in the first
place, and address that need first
Indeed!
I created a route:
map.with_options(:controller = 'site') do |site|
site.connect
Sean Cribbs wrote:
Right. The only caveat of disabling the cache is the potential for
lower performance. However, my point in bringing that up is that one
should focus on the _why_ you need an uncached page in the first
place, and address that need first. For example, with comments (see
the
I'm doing some similar and would love to know how to achieve this!
--
Posted via http://www.ruby-forum.com/.
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:
The typical solution is to make a page subclass that adds this method:
def cache?
false
end
Then make the page that you want uncached to be of that type. Before
you do that, however, take into consideration why you need the page
uncached. It may be that the need for it to be uncached is
Hi Sean
Sean Cribbs wrote:
The typical solution is to make a page subclass that adds this method:
def cache?
false
end
I'm just thinking of putting this down as the starting point for one of
the pages in the 'Summer Reboot' but I have a couple of questions to
understand this slightly
