[Radiant] 'Page Options' options / Caching
Hello all, I was just checking out the Page Options extension as I would like to set the cache timeout for my RSS feeds for just once a day. http://github.com/avonderluft/radiant-page_options-extension/tree/master However I'm getting an error and wondered if anyone knew the cause, or if there was an easy way to make this 0.8.1 compatible? It seems to work on 0.7.1... ActionView::TemplateError (uninitialized constant PageOptions::PageExtensions::ClassMethods::ResponseCache) on line #3 of vendor/extensions/page_options/app/views/admin/pages/_caching_header.html.haml: 1: #default_caching 2: ( Default Caching: 3: %em= Page.default_caching 4: ) 5: - content_for :page_css do 6: :sass Cheers, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] 'Page Options' options / Caching
Thanks for the note, I thought it would probably be an involved update - but I also thought I should just check incase... It looks great in 0.7.1 btw. Cheers, On 4 Dec 2009, at 16:44, Andrew vonderLuft wrote: Page Options needs to be rewritten for 0.8.1, since the caching in Radiant changed between 0.7 to 0.8 I hope to be getting to this relatively soon... Andrew On Dec 4, 2009, at 6:41 AM, subsor...@gmail.com wrote: Hello all, I was just checking out the Page Options extension as I would like to set the cache timeout for my RSS feeds for just once a day. http://github.com/avonderluft/radiant-page_options-extension/tree/master However I'm getting an error and wondered if anyone knew the cause, or if there was an easy way to make this 0.8.1 compatible? It seems to work on 0.7.1... ActionView::TemplateError (uninitialized constant PageOptions::PageExtensions::ClassMethods::ResponseCache) on line #3 of vendor/extensions/page_options/app/views/admin/pages/_caching_header.html.haml: 1: #default_caching 2: ( Default Caching: 3: %em= Page.default_caching 4: ) 5: - content_for :page_css do 6: :sass Cheers, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
On 24 Nov 2009, at 22:10, subsor...@gmail.com wrote:
It looks like it filters the events by date in the same manner as the blog
archive page type filters blog posts by date.
Just replying to myself incase this proves useful for anyone.
The Archive Events page does indeed work like the Standard Archive page types
and allow you to list events filtered by start_date, however the tags for the
Event Day page seem to return events for the entire month, instead of for a
single day, instead of what the archive title indicates.
Here are some amendments to the event_day_index_page.rb page that seem to
correct that and list events just for a single day.
class ArchiveFinder
def event_day_finder(finder, year, month, day)
new do |method, options|
start = Time.local(year, month, day)
finish = start.tomorrow
add_condition(options, event_datetime_start = ? and
event_datetime_start ?, start, finish)
finder.find(method, options)
end
end
end
tag archive:children do |tag|
year, month, day = $1, $2, $3 if request_uri =~
%r{/(\d{4})/(\d{2})/(\d{2})/?$}
tag.locals.children = ArchiveFinder.event_day_finder(parent.children, year,
month, day)
tag.expand
end
tag archive:unless_children do |tag|
year, month, day = $1, $2, $3 if request_uri =~
%r{/(\d{4})/(\d{2})/(\d{2})/?$}
if ArchiveFinder.event_day_finder(parent.children, year, month,
day).find(:all).empty?
tag.expand
end
end
The only trouble with this is that it limits all events pages to be the
children of the Events Archive page.
Another way to list all events for a single day in the future is to use the
route handlers extension and filter the events by url/date:
Route: route\/(\d{4})/(\d{2})/(\d{2})/?$
Fields: start_year, start_month, start_day
Although this means creating a page for each month of the year...
Does anyone know of a good trick to find all children of the root instead of
using parent.children?
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Comments Extension Notification CommentMailer Settings
Hello all,
I'm currently using the comments extension and am looking at enabling the email
notifications.
When I add an email address through the settings extension for the
comments.notification_to setting I get an SMTP syntax error when submitting a
comment, yet when I hardcode the recipient in the comment_mailer.rb
notification settings it sends successfully.
# recipients receivers.join(', ') --- produces syntax error (invalid
address)
recipients subsor...@gmail.com
Could anyone please be kind enough to show me the correct way to add the
address via the config settings?
Many thanks!
Dominic
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] aggreate archive
Is back door still available and working on 0.8? I had a look for it the other day but couldn't find it on github or the ext.radiant.org site. Do you have a link? On 24 Nov 2009, at 05:57, Steven Southard wrote: Not sure why if_first doesn't work here but using back_door I was able to create a simple inline work around. Thanks, Steven On Nov 23, 2009, at 1:33 PM, Steven Southard wrote: Do you know any reason this doesn't work: r:archive:children:each r:if_first div class=date style=text-align:right;r:date format=%A, %B %d, %Y //div /r:if_first ... The date works fine without the if_first yet it is repeated many times. If I add the if_first I just get no date at all. On Nov 23, 2009, at 12:18 PM, Jim Gay wrote: With your code: r:archive:children The current page scope for the r:date tag is the current page. You'd need: r:archive:children:each Or: r:archive:childrenHere are the children r:each...more code.../r:each/r:archive:children This would change the scope to each of the children and iterate through them. I'm sure you've just been staring at it too long ;-) On Mon, Nov 23, 2009 at 12:27 PM, Steven Southard ste...@stevensouthard.com wrote: Okay a little closer. I'm using this on a aggregated archive day: r:aggregate urls=/blog-archives/media; /blog-archives/art-scene; r:archive:children div class=date style=text-align:right;r:date format=%A, %B %d, %Y //div h1r:link //h1 r:content / /r:archive:children/r:aggregate So on http://localhost:3000/blog-archives/2009/11/12 I was expecting the articles written on a given day but I only get the archive page with the date I made the archive page. Also Recursion error: already rendering the `body' part. Thanks for all the help so far. Steven On Nov 23, 2009, at 7:00 AM, Jim Gay wrote: Pull the latest. I just fixed that. On Mon, Nov 23, 2009 at 1:31 AM, Steven Southard ste...@stevensouthard.com wrote: Yes, I was trying it with a normal page and also I re-installed the extension and I got a few more options which make it more possible. I think I understand it a bit better, yet I still don't have it working. now on a request like: http://localhost:3000/blog-archives/ 2009/11/16/ I get: undefined method `next_day' for Mon Nov 16 00:00:00 -0600 2009:Time Any ideas on this one? On Nov 22, 2009, at 5:52 PM, Jim Gay wrote: Are you using it on an archive page? aggregate:archive is undefined on just regular pages. On Sun, Nov 22, 2009 at 4:44 PM, Steven Southard ste...@stevensouthard.com wrote: Does this work for anyone else? r:aggregate urls=/blog-archives/media; /blog-archives/art- scene; r:archive:children:each /r:archive:children:each /r:aggregate All I get is: undefined tag `archive' -- Jim Gay http://www.saturnflyer.com ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Jim Gay Creative Director and Owner Saturn Flyer LLC j...@saturnflyer.com http://www.saturnflyer.com 571-403-0338 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Page Event Extension
Hello, I was just taking a look at the Page Event Extension and wondered if anyone knew what the day, month, season and year pages were and how they worked? Are they like archive pages in that the grab the url in order to display events for that date? What tags enable you to do this - the only ones I see look like they require the dates manually setting... Also does anyone know what the season page is and why it only looks like it has two seasons -presumably these are months? Looks like a really interesting extension, would love to hear from people about how it works. Thanks, Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
Hmm, How do you list the shows via the archives? I can see r:events:in_range:each but that requires start=/mm/dd manually specified in the tag. r:events:upcoming:each limit=10 just seems to list all upcoming events but is not scoped to the date in the archive... Is creating a simple list of events scoped by month/day possible? On 24 Nov 2009, at 15:31, Anton Aylward wrote: subsor...@gmail.com said the following on 11/24/2009 10:03 AM: Hello, I was just taking a look at the Page Event Extension and wondered if anyone knew what the day, month, season and year pages were and how they worked? Try installing it and you'll see that these are fields added to pages The 'calendar' is a dedicated page. Looks like a really interesting extension, would love to hear from people about how it works. it works real well. Just follow the instructions. -- Beware of bugs in the above code; I have only proved it correct, not tried it. -- Knuth ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
Sorry I should have been clearer, by shows I did mean events and by archives I meant the additional page types this extension adds: http://github.com/mghaught/radiant-page-event/tree/master/app/models/ e.g. event_archive_page.rb, event_month_index_page.rb, event_day_index_page.rb etc I understand I can list all future events, I also understand I can have a calendar but you can reveal more detailed event information in a list (a short description, content parts etc). I'd like to be able to have a *list* of all upcoming events but scoped to a certain month or a certain day. I saw that this could be done manually with the r:events:in_range:each start=/mm finish=/mm tag for each month but it would get impossible to manage on a more granular level for each day of the year. As I saw this extension added additional page types I simply wanted to know if anyone knew how they worked and what they added; they don't seem to alter the calendar behaviour and my first thought was that they would organise events by year/month/day just like the archive extension does for blog pages. I've just been poking around with it some more and it seems that the 'event month index page' does seem to have gained at least some of this functionality. r:archive:children:eachr:link /br //r:archive:children:each This seems to list events starting in the month (defined by url) but only events starting in that month and not events that carry over from the end of the previous month, those are only listed on the month they started - I'm not sure of its functionality I'm confused at to what these additional page types actually do...? Cheers, Dominic On 24 Nov 2009, at 17:43, Anton Aylward wrote: subsor...@gmail.com said the following on 11/24/2009 11:53 AM: Hmm, How do you list the shows via the archives? I can see r:events:in_range:each but that requires start=/mm/dd manually specified in the tag. r:events:upcoming:each limit=10 just seems to list all upcoming events but is not scoped to the date in the archive... Is creating a simple list of events scoped by month/day possible? We're talking at cross purposes, then. The Page Event archive is quite separate from the Archive. Its for events that appear in the calendar. Presentations, meetings, trade shows, things like that. Think C*A*L*E*N*D*A*R You have fields on those pages that say when the EVENT is to occur, and that has nothing to do with when the page was written, published or updated. I presume you don't mean shows in your sentence in that sense. Its about shows as a noun, trade SHOWS, theatrical SHOWS, not as the verb. The Archive ties in with when the page was published, as in a Blog. Its quite separate and nothing to do with this plugin. I'm using Page Event for a site that has no blogging. The upcoming Events section take the next 3 from the /events. Which is what its supposed to do. I think you have the wrong idea of what this is for. Think in terms of a CALENDAR of events. Now, instead of the matrix of the calendar, 28. 29, 30 or 31 days per page, think in terms of a linear list that may be over more than one page of the calendar, as might be the case with a once-a-month event. Think C*A*L*E*N*D*A*R -- It's not a good idea to believe anything about security when read in the mass media. by the time it gets there it is usually sensationalized to the point where it's more about hype and marketing than anything else. - Ryan Permeh [ta...@millcomm.com] on Vuln-Dev ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Page Event Extension
I'm referring to the the Page Events Extension that I linked to: http://github.com/mghaught/radiant-page-event As well as the event and calendar support it extends radiant by also adding several pages types, event_archive_page.rb, event_month_index_page.rb, event_day_index_page.rb etc. These look similar to the page types added by the Archive extensions but are added by the Page Event Extension - they are not added by the Archive extension. In the admin area on any particular page, for the page type you can choose Event Archive, Event Month Index, Event Day Index ... as well as the selections for the Blog extension; Archive, Archive Month Index, Archive Day Index. Two different things. It looks like it filters the events by date in the same manner as the blog archive page type filters blog posts by date. You can filter manually with the r:events:in_range:each tag. I'd like to know if you can filter based on the url like the page types suggest and what these page types do? On 24 Nov 2009, at 21:42, Anton Aylward wrote: subsor...@gmail.com said the following on 11/24/2009 03:04 PM: I'm confused at to what these additional page types actually do...? You've got me confused now. Which extensions are you talking about? you're refering to r:archive and r:events ... Those are two separate extensions. The first comes with the basic Radiant - check the gem if you haven't frozen it into your working tree. The second is a separate plugin that you download and install manually. The Radiant core archive code extracts the Archive pages from their original place in the Radiant distribution. Pages of page-type=archive are intended to provide behaviour similar to a blog archive or a news archive. Child page URLs are altered to be in %Y/%m/%d format (2004/05/06). Looking at the code of the archive extension I see that its based on date published, as you would expect or a blog. The Page Event code adds extra fields and its operation is based on those extra fields. The Archive is based on each page having one specific date. The Page Event is oriented around the idea of a calendar, so that means an event may have a start data and an end date, as would be the case for a conference, a trade show or a Broadway show. They are two completely different things with different objectives. Trying to use them together is going to tie you into knots. -- The art of progress is to preserve order amid change and to preserve change amid order. --Alfred North Whitehead ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] SQLite3::SQLException: no such table: extension_meta: SELECT schema_version FROM extension_meta WHERE name =
Hello all, I just decided to try out the the twitter extension, but then decided to remove it as it couldn't pull in multiple feeds. When I tried to roll back the migrations with this command: rake radiant:extensions:twitter:migrate VERSION=0 I got this error: SQLite3::SQLException: no such table: extension_meta: SELECT schema_version FROM extension_meta WHERE name = 'Twitter' Dropping columns in SQLite is a bit of a headache, so is there another command to use, or how can I fix this error in order to roll back easily? Thanks in advance, Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Unknown Mailer Issues (mailer help required again)
Hello all,
I'm in the process of updating a site from 0.6.x to 0.8.x and
everything so far has gone smoothly enough, however over time the
mailer extension has changed considerably and I cannot for the life of
me see what is going wrong where. The old v.1 just worked for me out
of the box.
As far as I am aware I have followed the available instructions and
have tried several of the branches without success.
I am seeing behaviour that is reported elsewhere, redirecting to /
pages/1/mail#mailer, I am not receiving any emails.
All that is in the production log is:
Parameters: {action=create, page_id=1, mailer=
{name=*, email=*...@***.com}, controller=mail}
environment.rb:
ActionMailer::Base.smtp_settings = {
:address = mail..co.uk,
:domain = .co.uk,
:user_name = ***,
:password = ,
:authentication = :login
}
Adding Radiant::Config['mailer.post_to_page?'] = true seems to have
no effect.
I don't know where to go from here as there is nothing in the
production log that helps.
Are there any known issues with mailer to look out for? Is there a
simple way to bypass smtp to force a delivery for testing?
Any help??
Cheers,
Dominic
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Tags Extension Bug?
Hi, I think I am seeing a bug in the Tags extension - whenever a tag is deleted from a page it appears that same tag cannot be re-applied even to different page. Has anyone else come across this? Any idea's on what might be causing it? Thanks, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Comments Extension and Notifications
Hi, Firstly thanks to all those who developed this extension, it seems like quite a roll call. Is this feature supported? I can see in TODO a note about stating that something similar is pending, but a quick glance through the code suggests it is in place. If it isn't implemented is it possible to auto approve comments that pass the simple spam test? Thanks , ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Search, 0.8.0 and Sqlite3
Thanks for the help, not sure how I missed that. Cheers, On 7 Aug 2009, at 15:56, Rafael Carvalho wrote: Use this: http://github.com/radiant/radiant-search-extension/tree/master and look this issue: http://github.com/radiant/radiant-search-extension/issues#issue/1 to know how to run with sqlite. And after all, please tell me if you are can run the exclude_pages attribute at r:search:form tag. ;-) 2009/8/7 subsor...@gmail.com Does anyone know if there is a search extension that is compatible with 0.8.0 and Sqlite3, I've had a go on a few and haven't come up with anything. Cheers, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant -- Rafael Carvalho ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Search, 0.8.0 and Sqlite3
Does anyone know if there is a search extension that is compatible with 0.8.0 and Sqlite3, I've had a go on a few and haven't come up with anything. Cheers, ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Problem with language_transliterate mailer extension
I'm not familiar with the extension you are having problems with but until someone else helps out have you tried specifying the extensions load order in environment.rb? On 7 Aug 2009, at 08:12, exitseven wrote: Good Morning, I have the language_transliterate extension (git://github.com/kranthi/language_transliterate_local.git) installed and it worked fine until I git cloned the mailer extension. Now everything I type gets somehow translated into arabic characters. And there is usually a dropdown called Type in provided by this extension, where you can choose the language you are typing in. But this dropdown is empty now. As soon as I move the mailer dir out of the extensions dir language_transliterate is working again. Any hint so solve this problem? Thank you, rainer ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] RubyGems 1.3.1 and Radiant 0.6.4
Hi, I have just updated to RubyGems 1.3.1 from an older version and now my old radiant gems are throwing a couple of errors due to some methods being depreciated: '#search support for String patterns is deprecated' and 'undefined method require_gem'. Is there a quick way to avoid having to update a number of Radiant sites to newer versions of radiant that would make them compatible with RubyGems 1.3.1, or is it a case of having to update all the sites and extensions? Presumably I could roll back rubygems and get them working again, any advise for this situation would be appreciated... Thanks Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] RubyGems 1.3.1 and Radiant 0.6.4
Thanks Sean, Do you mean updating using the instructions for 0.6.5, creating a new site and then migrating the db would have the new boot.rb wouldn't it? If only I could get 0.7.1 working I'd feel better about going forward ;) Does Radiant or it's version of RoR require any specific version of RubyGems (I might just roll back for now)... Cheers, On 16 Feb 2009, at 19:03, Sean Cribbs wrote: Dominic, Sorry, I don't know how you can get around that issue, except to update your sites to 0.7.x. The other day, I updated diopa.org to 0.7.0 and it is now significantly faster. I imagine you would encounter the same thing. One note about that conversion - I upgraded from 0.6.4 to 0.7.0 and I had to manually replace boot.rb to get it to upgrade. Sean subsor...@gmail.com wrote: Hi, I have just updated to RubyGems 1.3.1 from an older version and now my old radiant gems are throwing a couple of errors due to some methods being depreciated: '#search support for String patterns is deprecated' and 'undefined method require_gem'. Is there a quick way to avoid having to update a number of Radiant sites to newer versions of radiant that would make them compatible with RubyGems 1.3.1, or is it a case of having to update all the sites and extensions? Presumably I could roll back rubygems and get them working again, any advise for this situation would be appreciated... Thanks Dominic ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] undefined method `fdiv'
Hello again, I just updated my system in order to try out the latest version of Radiant and I am getting the following error in 0.7.1 NoMethodError (undefined method `fdiv' for 0:Fixnum): /usr/lib/ruby/1.8/yaml/rubytypes.rb:146:in `is_binary_data?' /usr/lib/ruby/1.8/yaml/rubytypes.rb:165:in `to_yaml' /usr/lib/ruby/1.8/yaml.rb:391:in `call' /usr/lib/ruby/1.8/yaml.rb:391:in `emit' /usr/lib/ruby/1.8/yaml.rb:391:in `quick_emit' /usr/lib/ruby/1.8/yaml/rubytypes.rb:164:in `to_yaml' /usr/lib/ruby/1.8/yaml/rubytypes.rb:41:in `node_export' /usr/lib/ruby/1.8/yaml/rubytypes.rb:41:in `add' /usr/lib/ruby/1.8/yaml/rubytypes.rb:41:in `to_yaml' /usr/lib/ruby/1.8/yaml/rubytypes.rb:40:in `each' /usr/lib/ruby/1.8/yaml/rubytypes.rb:40:in `to_yaml' /usr/lib/ruby/1.8/yaml/rubytypes.rb:39:in `map' /usr/lib/ruby/1.8/yaml/rubytypes.rb:39:in `to_yaml' /usr/lib/ruby/1.8/yaml.rb:391:in `call' /usr/lib/ruby/1.8/yaml.rb:391:in `emit' /usr/lib/ruby/1.8/yaml.rb:391:in `quick_emit' /usr/lib/ruby/1.8/yaml/rubytypes.rb:38:in `to_yaml' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/app/models/ response_cache.rb:148:in `write_response' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/app/models/ response_cache.rb:46:in `cache_response' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/app/controllers/ site_controller.rb:40:in `show_uncached_page' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/app/controllers/ site_controller.rb:21:in `show_page' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/base.rb:1166:in `send' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/base.rb:1166:in `perform_action_without_filters' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/filters.rb:579:in `call_filters' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/filters.rb:572:in `perform_action_without_benchmark' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/1.8/benchmark.rb:293:in `measure' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/rescue.rb:201:in `perform_action_without_caching' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/caching/sql_cache.rb:13:in `perform_action' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/ activerecord/lib/active_record/connection_adapters/abstract/ query_cache.rb:33:in `cache' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/ activerecord/lib/active_record/query_cache.rb:8:in `cache' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/caching/sql_cache.rb:12:in `perform_action' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/base.rb:529:in `send' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/base.rb:529:in `process_without_filters' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/filters.rb:568:in `process_without_session_management_support' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/session_management.rb:130:in `sass_old_process' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/plugins/haml/lib/ sass/plugin/rails.rb:19:in `process' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/base.rb:389:in `process' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/dispatcher.rb:149:in `handle_request' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/dispatcher.rb:107:in `dispatch' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/dispatcher.rb:104:in `synchronize' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/dispatcher.rb:104:in `dispatch' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/dispatcher.rb:120:in `dispatch_cgi' /usr/lib/ruby/gems/1.8/gems/radiant-0.7.1/vendor/rails/actionpack/ lib/action_controller/dispatcher.rb:35:in `dispatch' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/ rails.rb:76:in `process' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/ rails.rb:74:in `synchronize' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/bin/../lib/mongrel/ rails.rb:74:in `process' /usr/lib/ruby/gems/1.8/gems/mongrel-1.1.5/lib/mongrel.rb:159:in `process_client'
