[Radiant] Counting pages in an archived month - how?
Hey guys, Is there any way to count how many pages are archived per month for a given parent? What I have is this: Posts By Month ">format="%B %Y" /> I would like to show something like this, where "(50)" is the number of pages posted during February 2009: February 2009 (50) Any thoughts? Thanks, ~Nate ___ 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'
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
Re: [Radiant] RubyGems 1.3.1 and Radiant < 0.6.4
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] 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] [ANN] Radiant 0.7.1 - Engraving Release (bugfix)
Put it at the top of the file. RADIANT_GEM_VERSION = "0.6.9" Sean Mohit Sindhwani wrote: Sean Cribbs wrote: If you don't have it, it will automatically use the latest version. You're fine! Where do we add/ specify the RADIANT_GEM_VERSION? Start of the file, end of the file? I needed to do this for using an older version for a site that is built on 0.6.9 and the system tries to use 0.7.0 right now. I'm setting it at the command line before starting the server but was curious where exactly it should go. I'd like to also make a note of this on the wiki. Cheers, Mohit. 2/17/2009 | 12:33 AM. ___ 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] Comments -- order asc or desc
Has anyone added the option to comments:each for order? I've got comments working great so I thought they would also do a fine job of testimonials but the order needs to be reversed. Ordering comments by index or date would be very useful. Can anyone think of a way to do this with the available tags or does that option need to be added to comment_tags.rb? Steven Sorry to repost apparently the first post may have been poorly listed. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant 0.7.1 - Engraving Release (bugfix)
Sean Cribbs wrote: If you don't have it, it will automatically use the latest version. You're fine! Where do we add/ specify the RADIANT_GEM_VERSION? Start of the file, end of the file? I needed to do this for using an older version for a site that is built on 0.6.9 and the system tries to use 0.7.0 right now. I'm setting it at the command line before starting the server but was curious where exactly it should go. I'd like to also make a note of this on the wiki. Cheers, Mohit. 2/17/2009 | 12:33 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant 0.7.1 - Engraving Release (bugfix)
If you don't have it, it will automatically use the latest version. You're fine! Sean Erik van Oosten wrote: I am upgrading a recently created 0.7.0 site. In step 2 I can not find the RADIANT_GEM_VERSION constant. Am I missing something? Regards, Erik. Sean Cribbs wrote: UPGRADING FROM 0.7.x 1. Update the Radiant gem: % gem update radiant 2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to "0.7.1". 5. Restart the server ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant 0.7.1 - Engraving Release (bugfix)
I am upgrading a recently created 0.7.0 site. In step 2 I can not find the RADIANT_GEM_VERSION constant. Am I missing something? Regards, Erik. Sean Cribbs wrote: UPGRADING FROM 0.7.x 1. Update the Radiant gem: % gem update radiant 2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to "0.7.1". 5. Restart the server -- Erik van Oosten http://www.day-to-day-stuff.blogspot.com/ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Re: Multiple Sites with seperate users
Mr Magpie wrote: >> Could you keep us posted on this forum. >> >> I really would like to have this. I have installed 0.7.0 >> >> I am going to hold off using this until I can get multi-sites and users. >> >> thanks > > Hey, I wouldn't want anyone to be holding their breath for me to do > this. > I haven't even looked at the Radiant code base, and I'm quite pushed to > do anything non-essential at present. I could get by with one Radiant > install per customer for some time. I've got hungry mouths to feed. > Sorry if I gave the wrong impression. Magpie, No wrong impressions.. just hope. I absolutely understand the "shoes for Baby" problem. So I too will be using individual installs. Thanks for you input and good luck on feeding the kiddies... ...bartee... -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Re: Multiple Sites with seperate users
> Could you keep us posted on this forum. > > I really would like to have this. I have installed 0.7.0 > > I am going to hold off using this until I can get multi-sites and users. > > thanks Hey, I wouldn't want anyone to be holding their breath for me to do this. I haven't even looked at the Radiant code base, and I'm quite pushed to do anything non-essential at present. I could get by with one Radiant install per customer for some time. I've got hungry mouths to feed. Sorry if I gave the wrong impression. -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
