Forum: Radiant CMS Time-sensitive or expiring content

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Marshal L. (Guest)
on 2007-03-05 02:05
(Received via mailing list)
Hi. I'm new to Radiant (and Ruby, RoR) but eager to use Radiant for a
website I maintain. The site has an Events page where upcoming events,
workshops, etc. are listed.  The Home page of the site displays a
summary of the events; a list of links to the events with their start
dates. Nothing fancy. Look at http://octopusgardenyoga.com if you're
interested. It's maintained manually by editing the events.html and
index.html files whenever events are added and as they expire.

I was hoping to find a way to automate the updating of the events and
the summary list and Sean C.' weblog on time-sensitive content
(http://radiantcms.org/blog/2006/11/24/how-to-write...)
looked like it would do the job. So after much stumbling around, I
finally managed to get his tags working as extensions on my
development system (Ubuntu Linux with radiant-0.6.0rc1.gem installed).
In my Radiant-mental version, each event is a child page of /events/
and they are displayed with:

<r:children:each>
<div class="event">
<r:content />
</div>
</r:children:each>

This works as expected with expired content not displaying. However,
I've not been able to get it to work for the summary list on the home
page:

<h4>Upcoming Events</h4>
<ul>
<r:find url="/events/">
 <r:children:each>
   <r:if_content>
<== this makes no difference
     <li><r:link />: <r:content part="start" /></li>         <==
"start" has start date content
   </r:if_content>
 </r:children:each>
</r:find>
</ul>

Everything shows up whether it's expired or not. If anyone has any
ideas for making the summary list work, I would very much appreciate
hearing from you.

BTW, I've read most of the discussion on page ordering, and while I
don't pretend to understand the implementation issues, I think this
would be a very useful feature to have. It seems to me that two
additional page attributes,  "display_on" and "remove_after"  (or
something to that effect), might do the trick for both page ordering
and time-sensitive content. For example, <r:children:each
by="display_on"> would provide page ordering and something like
<r:if_date matches"regexpr"> would hide expired content. Just a
thought.

Thanks in advance.
This topic is locked and can not be replied to.