[Radiant] WebDav extension refactored
I just want to inform you that the WebDav extension has been refactored and the missing features like authentication and a proper page tree have been implemented. The extension is now also aware of the SnS and LanguageRedirect extensions and will handle those content properly. So if you ever wanted to edit your pages, page parts, snippets, layouts, javascripts and stylesheets remotely with your favorite editor, you should give http://github.com/willcodeforfoo/radiant-dav-extension/tree/master a try... Michael ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] WebDav extension refactored
I just want to inform you that the WebDav extension has been refactored and the missing features like authentication and a proper page tree have been implemented. The extension is now also aware of the SnS and LanguageRedirect extensions and will handle those content properly. So if you ever wanted to edit your pages, page parts, snippets, layouts, javascripts and stylesheets remotely with your favorite editor, you should givehttp://github.com/willcodeforfoo/radiant-dav-extension/tree/master a try... Michael ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: radiant-comments-extension install glitch
Jim Gay wrote: Have you run rake db:bootstrap yet? The first error says 'relation config does not exist' meaning the config table does not exist (which would be the case if you hadn't run the bootstrap) Dear Jim: Thanks for your reply! I didn't run rake db:bootstrap because I was following the (sparse) directions at http://github.com/artofmission/radiant-comments/tree/master, which make no mention of this. But your comment prompted me to realize that I hadn't specified the PRODUCTION database. I ran rake production radiant:extensions:comments:update --trace, which gave no error message. (I also then re-ran rake production radiant:extensions:comments:migrate, which also gave no error message.) Unfortunately, the Comments tab still links to http://www.jameslavin.com/admin/comments/unapproved, which still generates an Application error page. (Perhaps this is because I have now installed but not yet configured the extension, but I suspect there's still something wrong.) mail ~/public_html/jameslavin.com: rake production radiant:extensions:comments:update --trace (in /home/jkl/public_html/jameslavin.com) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment ** Invoke radiant:extensions:comments:update (first_time) ** Invoke environment ** Execute radiant:extensions:comments:update Again, Thanks. --James -- 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
Re: [Radiant] Re: radiant-comments-extension install glitch
Try the version from my fork: git://github.com/seancribbs/radiant-comments.git It is updated to work with 0.7. Sean P.S. Extension developers - don't set Radiant::Config values without checking for existence of the table! Your activate methods run on initialization, whether the DB is bootstrapped or not. James Lavin wrote: Jim Gay wrote: Have you run rake db:bootstrap yet? The first error says 'relation config does not exist' meaning the config table does not exist (which would be the case if you hadn't run the bootstrap) Dear Jim: Thanks for your reply! I didn't run rake db:bootstrap because I was following the (sparse) directions at http://github.com/artofmission/radiant-comments/tree/master, which make no mention of this. But your comment prompted me to realize that I hadn't specified the PRODUCTION database. I ran rake production radiant:extensions:comments:update --trace, which gave no error message. (I also then re-ran rake production radiant:extensions:comments:migrate, which also gave no error message.) Unfortunately, the Comments tab still links to http://www.jameslavin.com/admin/comments/unapproved, which still generates an Application error page. (Perhaps this is because I have now installed but not yet configured the extension, but I suspect there's still something wrong.) mail ~/public_html/jameslavin.com: rake production radiant:extensions:comments:update --trace (in /home/jkl/public_html/jameslavin.com) ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment ** Invoke radiant:extensions:comments:update (first_time) ** Invoke environment ** Execute radiant:extensions:comments:update Again, Thanks. --James ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Update: Comments now half working
Update: Comments are now half working. In /admin/pages, there's a comments column, but when I click to Enable an article, it generates an application error page. When I refresh /admin/pages, the Enable button has changed to 0 comments. And the enable_comments column in database table pages was correctly set to TRUE. I then manually set all the enable_comments values to TRUE for all my blog posts. After refreshing /admin/pages, the Enable buttons were all replaced by 0 comments. The comment forms appear correctly. And I was able to post a test comment. I saw it. But then it disappeared. It see the comment in the comments table of the database, but the approved_at and approved_by fields are blank. I have no idea how to approve it because the comments-related admin pages (including the Contents tab in /admin/pages, which points to /admin/comments/unapproved) all generate application errors. --James -- 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] Update: It's a pagination problem
I have the will_paginate gem (version 2.2.2) installed, but when I click
on the Comments tab, it can't find method paginate:
Processing Admin::CommentsController#index (for 69.120.41.109 at
2009-02-06 10:53:03) [GET]
...
Parameters: {status=unapproved, action=index,
controller=admin/comments}
...
NoMethodError (undefined method `paginate' for #Class:0x7f8e9c6c7b18):
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/activerecord/lib/active_record/base.rb:1672:in
`method_missing'
--
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] Seems to be working now
James Lavin wrote: I have the will_paginate gem (version 2.2.2) installed, but when I click on the Comments tab, it can't find method paginate: After adding config.gem will_paginate to environment.rb, it seems to be running! -- 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: radiant-comments-extension install glitch
Sean Cribbs wrote:
Try the version from my fork:
git://github.com/seancribbs/radiant-comments.git
It is updated to work with 0.7.
Sean
Thanks for the fix, Sean. Do I still need to install the fork if almost
everything is now working properly?
Here's what's still failing: Clicking Enable to enable comments for an
article correctly changes the info in the database but then throws this
error:
Processing Admin::CommentsController#enable (for XX.XX.XX.XX at
2009-02-06 16:21:49) [GET]
Session ID: XXX
Parameters: {action=enable, page_id=23,
controller=admin/comments}
Cookie set: session_token=; path=/; expires=Fri, 20 Feb 2009
21:21:49 GMT
NameError (undefined local variable or method `page_index_path' for
#Admin::CommentsController:0x7f0e4b013410):
/vendor/extensions/comments/app/controllers/admin/comments_controller.rb:66:in
`enable'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/base.rb:1166:in
`send'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/base.rb:1166:in
`perform_action_without_filters'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/filters.rb:579:in
`call_filters'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/filters.rb:572:in
`perform_action_without_benchmark'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/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.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in
`perform_action_without_rescue'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in
`perform_action_without_caching'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in
`passenger_orig_perform_action'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in
`cache'
...
--
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
Re: [Radiant] Re: Re: radiant-comments-extension install glitch
One of my tasks for tomorrow is to introduce a module that will contain
all of the legacy routes and their new equivalents. This will be
automatically included in the application helper and controller so the
old routes will work.
Sean
James Lavin wrote:
Sean Cribbs wrote:
Try the version from my fork:
git://github.com/seancribbs/radiant-comments.git
It is updated to work with 0.7.
Sean
Thanks for the fix, Sean. Do I still need to install the fork if almost
everything is now working properly?
Here's what's still failing: Clicking Enable to enable comments for an
article correctly changes the info in the database but then throws this
error:
Processing Admin::CommentsController#enable (for XX.XX.XX.XX at
2009-02-06 16:21:49) [GET]
Session ID: XXX
Parameters: {action=enable, page_id=23,
controller=admin/comments}
Cookie set: session_token=; path=/; expires=Fri, 20 Feb 2009
21:21:49 GMT
NameError (undefined local variable or method `page_index_path' for
#Admin::CommentsController:0x7f0e4b013410):
/vendor/extensions/comments/app/controllers/admin/comments_controller.rb:66:in
`enable'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/base.rb:1166:in
`send'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/base.rb:1166:in
`perform_action_without_filters'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/filters.rb:579:in
`call_filters'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/filters.rb:572:in
`perform_action_without_benchmark'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/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.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in
`perform_action_without_rescue'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in
`perform_action_without_caching'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in
`passenger_orig_perform_action'
/usr/lib/ruby/gems/1.8/gems/radiant-0.7.0/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in
`cache'
...
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Templates extension explosion solved, Now I want to reinstall cleanly
Jim Gay wrote: Take a look at what your log says cd log tail -900 producton.log - that will show the last 900 lines. If you need more or less, change the number. Or you can do tail -f production.log - that will display the log as the requests come in, so do that and then hit the admin page in a browser and you'll see the log populated I am curious, does radiant keep track of the schema anywhere in the file system that it would see that I have already migrated the extension before, albeit on my dev machine? Radiant should update the schema.rb file Jim, thanks for you help. That tip for viewing the production log as it's happening is awesome. The really strange thing is that the admin area of the site miraculously started working on its own. Strange. But since I can never leave well enough alone, I am going to try and install the templates extension again. I like the way it works for some of the site parts that I use. So a few more questions related to extensions in general: 1) I have migrated to VERSION=0 the templates extension, removed it from my file system and removed it from my git repo, but I noticed that there is still an entry for the templates extension in the extension_meta table. Will I be creating a problem if I delete that record (the last in the table)? Are there any other hidden db tables where I might find some vestigial parts of that now removed extension? 2) Where in the Radiant space-time continuum is the schema info that would normally be in the schema.rb file kept? The schema.rb file is essentially empty and I cannot find the schema info in the db so I am wondering, where is it? I want to make absolutely sure that my db is free of templates info. BTW, I am using the gem of 0.6.9. Thanks, //Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
