Re: [Radiant] undefined method `find' for Status:Class
Yesterday I decided to let it sleep. Today I unfroze, then froze radiant to the :edge, again. Oh, I also upgraded rubygems and rake gems. And now it works. I feel I'm beginning to understand what they mean when they say Rails is ful of magick. Go figure. :) On Dec 20, 2007 5:09 PM, nn [EMAIL PROTECTED] wrote: I'm trying to get radiant 0.6.4 to behave, but it keeps trowing this errror at me: ActionView::TemplateError (undefined method `find' for Status:Class) on line #15 of vendor/radiant/app/views/admin/page/_node.rhtml: 12: /span 13: /td 14: % unless simple -% 15: td class=status %= page.status.name.downcase %-status%= page.status.name %/td 16: td class=add-child%= link_to image('add-child', :alt = 'add child'), page_new_url(:parent_id = page) %/td 17: td class=remove%= link_to image('remove', :alt = 'remove page'), page_remove_url(:id = page) %/td 18: % end -% This behaviour is same, regardles of the frozen radiant version (tried with 0.6.4 tag, and with edge). I've also reinstalled radiant gem, but can't lose the error. Any ideas? ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] undefined method `find' for Status:Class
I'm trying to get radiant 0.6.4 to behave, but it keeps trowing this errror at me: ActionView::TemplateError (undefined method `find' for Status:Class) on line #15 of vendor/radiant/app/views/admin/page/_node.rhtml: 12: /span 13: /td 14: % unless simple -% 15: td class=status %= page.status.name.downcase %-status%= page.status.name %/td 16: td class=add-child%= link_to image('add-child', :alt = 'add child'), page_new_url(:parent_id = page) %/td 17: td class=remove%= link_to image('remove', :alt = 'remove page'), page_remove_url(:id = page) %/td 18: % end -% This behaviour is same, regardles of the frozen radiant version (tried with 0.6.4 tag, and with edge). I've also reinstalled radiant gem, but can't lose the error. Any ideas? ___ 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] undefined method `find' for Status:Class
Hi Loren, I have also had a similar problem since upgrading Locomotive over the weekend... I'm not sure what the exact problem is, but it seems to have something to do with the default server in Locomotive being changed to Mongrel instead of Lighttpd... I got around the problem by putting 'server: lighttpd' in the config/locomotive.yml (?) file, making it use Lighttpd instead of Mongrel... if anyone can shed some light on why the error is occurring in the first place, I would also be grateful... Cheers, Michael On 10/3/06, Loren Johnson [EMAIL PROTECTED] wrote: I'm getting a undefined method `find' for Status:Class whenever I install Radiant (either through the gem or an svn co) and then launch through Locomotive. This happens when loading the home page of the Simple Blog or the Empty website. If I launch the server directly without Locomotive running everything works as expected. Any ideas? I did see messages about this error in July but never saw a resolution nor did it appear at that time to be related to Locomotive (http://lists.radiantcms.org/pipermail/radiant/2006-July/000881.html) I've confirm the presence of models/status.rb, etc. It seems to be some sort of path issue related to the Radiant configuration and Locomotive settings... Help? Loren Johnson [EMAIL PROTECTED] ___ 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] undefined method `find' for Status:Class
Great tip, that fixes it for now and I too would like to know why it's not working under Mongrel. HmmmCheers to you,LorenOn Oct 2, 2006, at 9:12 PM, Michael Roper wrote:I have also had a similar problem since upgrading Locomotive over theweekend...I'm not sure what the exact problem is, but it seems to have somethingto do with the default server in Locomotive being changed to Mongrelinstead of Lighttpd...I got around the problem by putting 'server: lighttpd' in theconfig/locomotive.yml (?) file, making it use Lighttpd instead ofMongrel...if anyone can shed some light on why the error is occurring in thefirst place, I would also be grateful... Loren Johnson[EMAIL PROTECTED] ___ Radiant mailing list Post: Radiant@lists.radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant