Re: [Radiant] Displaying a specific child's content
@Clark, --- r:find url=about !-- content of the 'about' page: -- r:content part=body / /r:find --- This includes the content of the page 'about' into your actual page. Alternative you could write 'r:content /', because per default the body page part is shown (or you could include self defined page parts). Best regards, Andreas Semt BJ Clark schrieb: Hello All, I'm trying to display the content of a specific child page. Is there anyway to do this via radius tags? I realize that I can do all children (or whatever) via r:children:each or :first but I need to do :specificpage and I'm not sure how that is done. Is there a way to do that? Thanks, BJ Clark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Displaying a specific child's content
I suppose I misunderstood his question. I thought he wanted to know how to access the content of a child page, but in retrospect, I realize that he just wanted to show the actual content of a child page somewhere else. I think the r:find tag definitely helps, but I don't know if it is able to bring specific parts of a child page or of it will retrieve the content of the whole page. I guess he could play with the DB and then do a r:find by=fieldName??? On 1/1/07, Andreas Semt [EMAIL PROTECTED] wrote: @Clark, --- r:find url=about !-- content of the 'about' page: -- r:content part=body / /r:find --- This includes the content of the page 'about' into your actual page. Alternative you could write 'r:content /', because per default the body page part is shown (or you could include self defined page parts). Best regards, Andreas Semt BJ Clark schrieb: Hello All, I'm trying to display the content of a specific child page. Is there anyway to do this via radius tags? I realize that I can do all children (or whatever) via r:children:each or :first but I need to do :specificpage and I'm not sure how that is done. Is there a way to do that? Thanks, BJ Clark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Displaying a specific child's content
@Ruben, perhaps it's necessary to code it this way: --- r:find url=about r:if_content part=special_part !-- should show the page part 'special_part' of page 'about': -- r:content part=special_part / /r:if_content /r:find --- Best regards, Andreas Semt Ruben D. Orduz schrieb: I suppose I misunderstood his question. I thought he wanted to know how to access the content of a child page, but in retrospect, I realize that he just wanted to show the actual content of a child page somewhere else. I think the r:find tag definitely helps, but I don't know if it is able to bring specific parts of a child page or of it will retrieve the content of the whole page. I guess he could play with the DB and then do a r:find by=fieldName??? On 1/1/07, Andreas Semt [EMAIL PROTECTED] wrote: @Clark, --- r:find url=about !-- content of the 'about' page: -- r:content part=body / /r:find --- This includes the content of the page 'about' into your actual page. Alternative you could write 'r:content /', because per default the body page part is shown (or you could include self defined page parts). Best regards, Andreas Semt BJ Clark schrieb: Hello All, I'm trying to display the content of a specific child page. Is there anyway to do this via radius tags? I realize that I can do all children (or whatever) via r:children:each or :first but I need to do :specificpage and I'm not sure how that is done. Is there a way to do that? Thanks, BJ Clark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] [ANN] New site launched
Colleagues and friends, I am happy to announce the new website for Kansas City Kansas Community College, www.kckcc.edu. The site is the culmination of countless hours of planning, testing, and toiling. I'm announcing here because the site is powered by RadiantCMS, of course! I intend to make a detailed post on my personal blog about the site and the process, but here's a few stats to hold you over: 300+ Pages ~12 snippets 3-4 layouts 6 extensions (yes, we're running mental!) And much more... We are extremely happy with the ease-of-use and performance that Radiant provides our team (along with a rock-solid server, Litespeed). As time goes on, I intend to polish and release some of the extensions which include LDAP integration and ports of the Mailer and Search behaviors -- I'm sure you're itching for them! I submitted a proposal to RailsConf 2007 about our work. Wish me luck on that! And not to toot my own horn too much, but my design was chosen from 3 alternatives by the students, and thus I was responsible for the majority of the CSS and Photoshop work. As you might be able to tell, I take a lot of my design inspiration from John's work ;). Here's to a happy New Year, using Radiant! Sean Cribbs seancribbs.com p.s. During the process of launching the website, the college also changed ISPs. There may be intermittent connectivity problems until the process is complete. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] New site launched
Very nice ... would be interested in hearing about (if any) snags you might have run into, and also what the backend setup is (using Capistrano?, etc) ... good luck w/ RC07 acceptance, nice case study! - Jon On Jan 1, 2007, at 3:41 PM, Sean Cribbs wrote: Colleagues and friends, I am happy to announce the new website for Kansas City Kansas Community College, www.kckcc.edu. The site is the culmination of countless hours of planning, testing, and toiling. I'm announcing here because the site is powered by RadiantCMS, of course! I intend to make a detailed post on my personal blog about the site and the process, but here's a few stats to hold you over: 300+ Pages ~12 snippets 3-4 layouts 6 extensions (yes, we're running mental!) And much more... We are extremely happy with the ease-of-use and performance that Radiant provides our team (along with a rock-solid server, Litespeed). As time goes on, I intend to polish and release some of the extensions which include LDAP integration and ports of the Mailer and Search behaviors -- I'm sure you're itching for them! I submitted a proposal to RailsConf 2007 about our work. Wish me luck on that! And not to toot my own horn too much, but my design was chosen from 3 alternatives by the students, and thus I was responsible for the majority of the CSS and Photoshop work. As you might be able to tell, I take a lot of my design inspiration from John's work ;). Here's to a happy New Year, using Radiant! Sean Cribbs seancribbs.com p.s. During the process of launching the website, the college also changed ISPs. There may be intermittent connectivity problems until the process is complete. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Displaying a specific child's content
@Ruben, I'm just trying to display the content of certain pages in other pages. @Andreas, Are you sure this works for you? It's not putting anything in my page. I don't get an error, but it doesn't do anything either. Thanks 2 everyone, BJ Clark On 1/1/07, Andreas Semt [EMAIL PROTECTED] wrote: @Ruben, perhaps it's necessary to code it this way: --- r:find url=about r:if_content part=special_part !-- should show the page part 'special_part' of page 'about': -- r:content part=special_part / /r:if_content /r:find --- Best regards, Andreas Semt Ruben D. Orduz schrieb: I suppose I misunderstood his question. I thought he wanted to know how to access the content of a child page, but in retrospect, I realize that he just wanted to show the actual content of a child page somewhere else. I think the r:find tag definitely helps, but I don't know if it is able to bring specific parts of a child page or of it will retrieve the content of the whole page. I guess he could play with the DB and then do a r:find by=fieldName??? On 1/1/07, Andreas Semt [EMAIL PROTECTED] wrote: @Clark, --- r:find url=about !-- content of the 'about' page: -- r:content part=body / /r:find --- This includes the content of the page 'about' into your actual page. Alternative you could write 'r:content /', because per default the body page part is shown (or you could include self defined page parts). Best regards, Andreas Semt BJ Clark schrieb: Hello All, I'm trying to display the content of a specific child page. Is there anyway to do this via radius tags? I realize that I can do all children (or whatever) via r:children:each or :first but I need to do :specificpage and I'm not sure how that is done. Is there a way to do that? Thanks, BJ Clark ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] New site launched
Define 'truly dynamic'? In some senses all the pages are because they use Radius code. However, I suspect you mean which ones are cached and which ones aren't. The only pages that are not cached are the Mailer pages. All other pages, whether they generate some content from an integrated extension or contain only static content, are cached. Now, I intend to get to this in more detail in my blog post and potential presentation to RC07, but here's a basic rundown. Any pages that have a list of staff/faculty names (with email links), title and phone number have LDAP generated content. The course descriptions/syllabi are two pages (one virtual) that is another mini-application. The 2006-2007 academic calendar (and soon to be other pages) is 'dynamically generated' from custom-built models. Obviously, the search page uses the ported search behavior (not the big acts_as_ferret one, but the simpler one). There are other little touches, like the HR jobs page uses time-expiring content to show open positions, of which there are none at this point. Almost every page that has an email address in it has it generated through a Javascript obfuscator; the generated Javascript code comes from a Radius tag. The news articles and videos use the Archive functionality. I called my boss, but is anyone else having trouble hitting it? Might be the new routing... ugh. Cheers, Sean Cribbs Sean, Very nice, very no-nonsense. one question: which pages are truly dynamic? By that I mean not just HTML content statically stored in the DB, just for curiosiy? It's a good job considering it's for a public insitution and all the baggage that comes with. Commitee meeting, anyone? :) On 1/1/07, Sean Cribbs [EMAIL PROTECTED] wrote: Colleagues and friends, I am happy to announce the new website for Kansas City Kansas Community College, www.kckcc.edu. The site is the culmination of countless hours of planning, testing, and toiling. I'm announcing here because the site is powered by RadiantCMS, of course! I intend to make a detailed post on my personal blog about the site and the process, but here's a few stats to hold you over: 300+ Pages ~12 snippets 3-4 layouts 6 extensions (yes, we're running mental!) And much more... We are extremely happy with the ease-of-use and performance that Radiant provides our team (along with a rock-solid server, Litespeed). As time goes on, I intend to polish and release some of the extensions which include LDAP integration and ports of the Mailer and Search behaviors -- I'm sure you're itching for them! I submitted a proposal to RailsConf 2007 about our work. Wish me luck on that! And not to toot my own horn too much, but my design was chosen from 3 alternatives by the students, and thus I was responsible for the majority of the CSS and Photoshop work. As you might be able to tell, I take a lot of my design inspiration from John's work ;). Here's to a happy New Year, using Radiant! Sean Cribbs seancribbs.com p.s. During the process of launching the website, the college also changed ISPs. There may be intermittent connectivity problems until the process is complete. ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ideas for reimplementation of radiant caching
Dan,
This sounds like a pretty good system.
I'm not sure if my suggestions/concerns are directly related caching,
but they kind of go with it.
The biggest hole in Radiant that I can see is that there is not proper
version management and publishing capabilities.
I work for a large state government organization and I have to use
Microsoft CMS 8 hours a day. It does lots of stuff completely
terribly, but one nice thing about it is it's version
management/publishing system.
Here's what I mean:
You have an existing page, you change some content, there is no way to
preview it or approval process for it other than publishing it and
viewing it live. Maybe this is by choice (I hope not), but I could see
how this is a major reason for lack of adoption on a larger scale.
What I'd like to see:
After a page is changed, a new version is saved and the status for the
new version is set to draft. There's a way to preview this page, and
then publish/approve the page and it would then be live. This is when
it would be cached.
This still allows for dynamic content and definitely takes Radiant to
the next level for me (dare I say, enterprise ready).
My $.02, I don't know if you've considered it in your caching scheme.
- BJ Clark
On 1/1/07, Ruben D. Orduz [EMAIL PROTECTED] wrote:
Dan,
It seems you have given this quite a bit of thought, and it could
work. I'm just worried about when will the ROI of performace hit make
it be worth.
Just as an anecdote, I've worked with paid enterprise-grade CMS's,
open-source CMS's and I've only seen two types of caching:
1) The classic: time expiry unless forced by hand.
2) Tag-level caching: You can choose which tags NOT to cache. So for
example, in a news site, pretty much the whole site could be cached,
except for content produced by %breaking-news%.
Maybe something like that could be adapted for Radiant (i.e. give the
choice which caching is desired).
On 1/1/07, Daniel Sheppard [EMAIL PROTECTED] wrote:
I want radiant to have a more robust caching mechanism than the current
'expire every x minutes' method of doing things - I'd like it to be able
to handle just removing things from the cache when things actually
change. I've roughed out a plan on how I think this should be done in a
safe manner.
It sounds like it should work, but this is mainly just what I thought of
on the way to work this morning - I'd like people to poke holes in it
and figure out any edge-cases I'm missing out on - if this process EVER
misses out on the clearing of a cached page, it's pretty much useless.
I see a bit off overhead being added to the rendering process (since
after_initialize hooks are a performance no-no), but since this should
reduce the need for rendering by a huge amount, I'm hoping it'll balance
out.
I will probably put off an implementation of this until after I finish
off my asset extension and get other things running, but I might pull
this forward for asset caching as well... not sure yet.
--
Example Site layout:
Pages:
+ Homepage ('main', 'sidebar')
+ Articles ('main', 'sidebar')
- Article1 ('full', 'extract')
- Article2 ('full', 'extract')
Snippets:
- Header
- Footer
Layouts
- Default
Homepage:
r:find url='articles'
r:children:each
r:title/
r:if_content part=extract/
r:content part=extract/
/r:if_content
/r:children
/r:find
'default' layout:
r:snippet name=header/
r:content/
r:snippet name=footer/
--
In this example, the homepage needs to be re-rendered when:
- homepage is modified
- new article child is created
- article1/2 is updated/removed
- article1/2 has extract added/removed
- default layout is modified
- header snippet is modified
- footer snippet is modified
- (please tell me if I'm missing cases here)
To know all those things, the following should be more than enough to
keep track of:
- any page which is read from db during the render
- any snippet which is read from db during the render
- any layout which is read from db during the render
New Table:
create_table 'cache_dependencies' do |t|
t.column :page_id, :integer
t.column :depends_on, :integer
t.column :cache_type, :string
end
Since this is just a scratch table, perhaps this should use something
like madeline or maybe just a tree of files that are locked on write
instead of being in the main database file.
Filesystem cache:
pages/
page.data
page.cacheinfo
An after_save is added to each snippet/layout:
CacheDependencies.find_all_by_cache_type_and_depends_on('snippet',
snippet.id) do |cd|
[Radiant] Asset Management Extension Progress
I've progressed on my asset management extension. Further updates will be available at: http://soxbox.no-ip.org/radiant I've now finished: - a way to upload asset for a page that hasn't been created yet. If you upload an asset and subsequently don't save the page, it's still left orphaned though (probably just have a rake task to clean. - Caching. Currently using the exact same mechanism as the rest of radiant (ie. 5 minute expiry and stored in yaml files). Not the best approach for either large assets or manipulated images. So that leaves: - a nice way to edit/delete images - validation - tests - confidence that you can use this without screwing up your data/life/mind. Original announcement: http://soxbox.no-ip.org/radiant/articles/2007/01/02/page-asset-managemen t/ ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
