@BJ,
it works for me. The content tag is also described
here: http://radiantcms.org/blog/2006/05/11/tag-primer/
The example says:
---
r:content part=sidebar / → Content from the sidebar part of the page.
The part attribute (shown above) allows you to specify which part of the
page you would
Hi Dan, Ruben,
Actually I once build a commercial Enterprise CMS where a custom content
proxy would cache everything. It was flushed on time-out /and/ upon
changes in the content. The proxy allowed large companies to set up
caches wherever they pleased and still have a central repository. The
From looking at response_cache, there are only two features that it
implements that the default rails action caching didn't (easily):
- Expire Everything
- Expire After time
Am I missing something else? If I'm not, then I think I might have found
something that will give a big
The performance of find_by_url degrades because children don't
automatically get a reference to their parent, but they need to get that
parent reference to compute their url. With a structure of:
- home
- articles
- (600 articles here)
To find the nth article will take
I meant to post that to radiant-core... Sorry to the peoples that are
scared by such things.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Daniel Sheppard
Sent: Wednesday, 3 January 2007 4:08 PM
To: radiant@lists.radiantcms.org
Subject:
