Re: [Radiant] Help with artofmission comments extension
john wrote: Nevermind, a little patching and it's up and running, now just to figure out what To enable spam protection, you will need to set your Akismet key and url in the Radiant config. is supposed to mean... Hi John Can I urge you to please consider writing out the steps and a bit of information about the little patching that you did into the Summer Reboot Documentation Wiki? An example of an a page about an extension is at: http://wiki.radiantcms.org/Copy_and_Move - don't worry about screenshots. I need to use comments in the next couple of weeks, so I can create them for you when I get to it. The Summer Reboot wiki is at: http://wiki.radiantcms.org/Summer_Reboot As for the Akismet key, you can read more about akismet at their website: http://akismet.com/ - if I understand it correctly, it will help you scan the comments that have just been entered and give you back information about whether it is likely to be spam. You can get an Akismet key (free for personal use) by signing up for Wordpress - http://akismet.com/personal/ - a key comprises a key and the URL to which it applies. You'll get both of these when you sign up. You need to enter this key into the Radiant configuration so that the comments extension can use it to probe Akismet if comments are spam. For changing items in the Radiant config, there's an example here: http://wiki.radiantcms.org/Customizations_II in the first section. I looked at the source of the extension and found this: def akismet @akismet ||= Akismet.new(Radiant::Config['comments.akismet_key'], Radiant::Config['comments.akismet_url']) end I'm guessing you need to set: Radiant::Config['comments.akismet_key'] and Radiant::Config['comments.akismet_url'] Hope this helps. Also, hope that you'll seriously consider documenting the steps on Summer Reboot :) Cheers, Mohit. 9/2/2008 | 2:19 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Summer reboot Radius articles
Andrew Neil wrote: Hello all (and especially Mohit), Hello Drew (and everyone) A couple of weeks ago I started work on the article Using the built-in tags for the Summer Reboot. My intention was to go over a handful of Radius tags which carry out 'typical' functions, such as inserting content, changing scope, showing content on condition that... etc. I'm trying to illustrate how the various tags work by providing examples, often using a fake site map. I had thought of creating a simple sample DB that we could use for this purpose. If there's interest, I can hammer something out this weekend. I have recently learned how to extract out content from a Word document - splitting at every Heading 1, Heading 2, Heading 3, etc. to create a bunch of textile files that can be inserted into Radiant. I could use something like that if need be. Well, the article has grown rather large, and so I have decided that it is appropriate to branch it into a series of shorter articles: http://wiki.radiantcms.org/Introduction_to_Radius http://wiki.radiantcms.org/Tags_that_insert_content http://wiki.radiantcms.org/Tags_that_change_the_scope http://wiki.radiantcms.org/Conditional_tags *snip* I think the re-organization makes sense. I'm just thinking if it's better to consider posting this whole thing into a separate chapter. Let's see how much stuff goes into it. If there's a lot, we'll do that later. This is great. I had written up something on inserting dates - I'll find the correct section and post it in. Currently, it's at: http://notepad.onghu.com/2007/9/10/radiant-cms-showing-the-date-of-articles If anyone has time to proof my articles, I'd be glad to hear any feedback. Especially if you are new to Radiant, because you are the target audience for this set of articles. If you already have experience using Radius tags, perhaps you can read with a view to finding mistakes. If no one else gets to it first, I shall do so this weekend. Last weekend, I finally got back to using Radiant for a site that I've wanted to for a very long time, and was very happy to see that the Summer Reboot documentation really helps! I've also got code now that helps you insert pages automatically using Ruby into a Radiant install (thanks Saji!) but the actual code is a real mess. Once I clean it up a bit, I can publish that as reference for anyone who may need it - and also into the wiki under 'Advanced' uses. Cheers, Mohit. 9/2/2008 | 2:26 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Rradiant gem 0.6.9: undefined local variable or method `salt' for #User:0x25542e8
Hello, after upgrading to a newer gem (to 0.6.9 w/ rails 2.1.0 from 0.6.4 w/ rails 2.x), I get the following error, during login: --%-- undefined local variable or method `salt' for #User:0x25542e8 /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/ lib/active_record/attribute_methods.rb:205:in `method_missing' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/models/user.rb:32:in `sha1' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/models/user.rb:37:in `authenticate' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/ controllers/admin/welcome_controller.rb:13:in `login' --%-- I tried to disable any extensions and commented out the followine line in environment.rb: config.extensions = [ :shards, :page_attachments, :mailer, :all ] But the error was still there. BTW: I only got problems during login into /admin so far. The frontend is working. Any ideas and help? 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
Re: [Radiant] Rradiant gem 0.6.9: undefined local variable or method `salt' for #User:0x25542e8
Hi Rainer, Sounds like you haven't upgraded the database? Try with a: rake db:migrate RAILS_ENV=production Cheers, Casper Fabricius On 02/09/2008, at 11:08, rainer griess wrote: Hello, after upgrading to a newer gem (to 0.6.9 w/ rails 2.1.0 from 0.6.4 w/ rails 2.x), I get the following error, during login: --%-- undefined local variable or method `salt' for #User:0x25542e8 /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/ lib/active_record/attribute_methods.rb:205:in `method_missing' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/models/user.rb:32:in `sha1' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/models/user.rb:37:in `authenticate' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/ controllers/admin/welcome_controller.rb:13:in `login' --%-- I tried to disable any extensions and commented out the followine line in environment.rb: config.extensions = [ :shards, :page_attachments, :mailer, :all ] But the error was still there. BTW: I only got problems during login into /admin so far. The frontend is working. Any ideas and help? 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
Re: [Radiant] Rradiant gem 0.6.9: undefined local variable or method `salt' for #User:0x25542e8
Uh man, thank you! I did it a thousand times during my tryings but missed it this time. That solved the problem! Thank you very much, rainer On 02.09.2008, at 11:19, Casper Fabricius wrote: Hi Rainer, Sounds like you haven't upgraded the database? Try with a: rake db:migrate RAILS_ENV=production Cheers, Casper Fabricius On 02/09/2008, at 11:08, rainer griess wrote: Hello, after upgrading to a newer gem (to 0.6.9 w/ rails 2.1.0 from 0.6.4 w/ rails 2.x), I get the following error, during login: --%-- undefined local variable or method `salt' for #User:0x25542e8 /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/vendor/rails/activerecord/ lib/active_record/attribute_methods.rb:205:in `method_missing' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/models/user.rb:32:in `sha1' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/models/user.rb:37:in `authenticate' /Library/Ruby/Gems/1.8/gems/radiant-0.6.9/app/ controllers/admin/welcome_controller.rb:13:in `login' --%-- I tried to disable any extensions and commented out the followine line in environment.rb: config.extensions = [ :shards, :page_attachments, :mailer, :all ] But the error was still there. BTW: I only got problems during login into /admin so far. The frontend is working. Any ideas and help? 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Radiant Conference Survey Reminder
This is a friendly reminder that the survey for the Radiant Conference is up and open until 12:00AM EDT Saturday, September 13. Make sure to respond if you want to have a say in any aspect of the conference. Also remember that there are three pages to the survey, so make sure to fill out all three. If you don't have the link, you can find it here: http://www.surveymonkey.com/s.aspx?sm=Z6yHvoHLaL6CflqlkmkdCg_3d_3d Cheers, Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Which is the best forum app to use with/next to Radiant?
I have been scouring the net for some info on Beast, the only forum app/plugin/whatever that I know of that written with rails, and I cannot get beast.caboo.se to load to find out more info. After some searching I found out somebody had turned it into a plugin, called Savage Beast 2, that uses the new engines plugin. Having played with engines once before, I am not keen to mess with it again and need to find alternatives. Is there a forum extension for Radiant? What has anyone else used for running a forum along side a radiant app? I am tempted to just set up an instance of phpbb on a subdomain and be done with it unless someone has a better suggestion. I am all ears. 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] Failing (back_door) extension tests on Radiant
Part of my question is directed to Aitor, author of the back_door extension. More generally I'd like to know more about writing proper tests for a Radiant extension. More details are below. I'm starting some new projects with radiant 0.6.9 and want to get off on the right foot with building/using tests. I installed only the back_door extension. All the tests for the distribution extensions pass. (rake test) The back_door tests generate a stack trace: /usr/bin/ruby -Ilib:lib /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb test/unit/back_door_tags_test.rb test/functional/back_door_extension_test.rb /usr/lib/ruby/gems/1.8/gems/radiant-0.6.9/vendor/rails/railties/lib/test_help.rb:1: undefined method `require_dependency' for main:Object (NoMethodError) from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from /usr/lib/ruby/gems/1.8/gems/radiant-0.6.9/test/test_helper.rb:15 from /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in `require' from ./test/unit/../test_helper.rb:8 from ./test/unit/back_door_tags_test.rb:1 from /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb:5 from /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb:5 I tried fixing up the require_dependency problem by copying some code from the textile extension's test_helper.rb into that of back_door. This does get me past this particular problem. However the unit tests all fail with what is probably the same error. For example: /usr/bin/ruby -Ilib:lib /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader.rb test/unit/back_door_tags_test.rb test/functional/back_door_extension_test.rb Loaded suite /usr/lib/ruby/gems/1.8/gems/rake-0.8.1/lib/rake/rake_test_loader Started .EE Finished in 0.07769 seconds. 1) Error: test_attribute_expansion(BackDoorTagsTest): NoMethodError: You have a nil object when you didn't expect it! The error occurred while evaluating nil.request= /usr/lib/ruby/gems/1.8/gems/radiant-0.6.9/test/helpers/render_test_helper.rb:54:in `setup_page' /usr/lib/ruby/gems/1.8/gems/radiant-0.6.9/test/helpers/render_test_helper.rb:49:in `get_render_output' /usr/lib/ruby/gems/1.8/gems/radiant-0.6.9/test/helpers/render_test_helper.rb:11:in `assert_render_match' ./test/unit/back_door_tags_test.rb:120:in `test_attribute_expansion' I'll be happy to help by writing/fixing tests for the back_door extension. Is there a good example I can follow? (Looks like quite a few tests exist in the archive extension.) I appreciate any help or suggestions any of you have. Thanks, Bill -- Bill Barnard ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Looking for draft+history extension collaborators or contractors
I'm needing an extension that will show the history of pages/snippets/ layouts as well as allowing concurrent drafts of published pages/ snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Good ideas about what to name this extension? Jason Garber___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
On Sep 2, 2008, at 3:39 PM, Jason Garber wrote: I'm needing an extension that will show the history of pages/ snippets/layouts as well as allowing concurrent drafts of published pages/snippets/layouts. The basic structure is that there's a series of versions of the current page — some of which are drafts and some of which are published — and the dev site shows the latest draft and the live site shows the latest published version. I'm assuming that it's a misstatement, but did you really mean to say that there are some versions of a page that are published, meaning more than one published version of the same page? Features I'm anticipating: * History of who changed what (including titles and other meta info, page parts, snippets, layouts) for the whole site or an individual page, including a diff so you can see at a glance exactly what changed with a toggle to see only changes between published versions or all the drafts in between and a timeline to visualize the changes. * Ability to revert to a prior version (actually just copy the old version to a new draft). * Ability to work on a single draft version and save it while an older published version is still live (like concurrent_drafts extension but without the scheduling and all the fields are draftable, not just the page parts' content). Does this resonate with anyone else? Already working on a similar extension? Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/tree/master I began work on a drafts extension which plans to manage drafts on a page part basis (rather than the entire page) but I haven't been able to put a lot of time into it. I believe that in most regular use, authors will create draft content for page parts rather that entire pages so I'm creating it to do that. It is premature to suggest using it, but I'd love any help if you are interested http://github.com/saturnflyer/radiant-drafts-extension/tree/master I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. Perhaps the snapshot extension has some ideas in it for you: http://aitor.name/snapshot.tar.gz (not sure how up-to-date that is) Anyone wanting to collaborate on it? Any freelancers want to pick up the job? Sure. Are you planning for it to be open source? I'm sure there would be plenty of interest in the community. Good ideas about what to name this extension? How about chronicle? 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
Re: [Radiant] Looking for draft+history extension collaborators or contractors
Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/tree/master I began work on a drafts extension which plans to manage drafts on a page part basis (rather than the entire page) but I haven't been able to put a lot of time into it. I believe that in most regular use, authors will create draft content for page parts rather that entire pages so I'm creating it to do that. It is premature to suggest using it, but I'd love any help if you are interested http://github.com/saturnflyer/radiant-drafts-extension/tree/master I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. That is the strategy that concurrent_draft takes -- each part has 'content' and 'draft_content' fields. The nice thing about that is that we could treat parts, snippets and layouts almost identically, with some tweaks for pages (and propagating publishing to the parts). There's no historical versioning, though. Sean ___ 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: BIG problems after removing page_attachments
On Tue, 2008-09-02 at 22:08 +0200, Arik Jones wrote: I wasn't questioning your intelligence. Yeah, I know. It is the most obvious thing. Once I read your email I did recheck it, but I had removed all references to it. It's a shame to rebuid (well, halfway) the site. It's all good in the end. ~Nate ___ 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: Re: BIG problems after removing page_attachments
Yay web development! lol. -- 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] Looking for draft+history extension collaborators or contractors
On Sep 2, 2008, at 4:21 PM, Sean Cribbs wrote: Take a look at the concurrent_draft extension. It allows you to schedule a draft of a page, snippet or layout for publication. http://github.com/avonderluft/radiant-concurrent_draft-extension/tree/master I began work on a drafts extension which plans to manage drafts on a page part basis (rather than the entire page) but I haven't been able to put a lot of time into it. I believe that in most regular use, authors will create draft content for page parts rather that entire pages so I'm creating it to do that. It is premature to suggest using it, but I'd love any help if you are interested http://github.com/saturnflyer/radiant-drafts-extension/tree/master I have no immediate need for holding onto old versions so I have no current plans to add that, but if it were unobtrusive and intuitive I'd certainly be interested. That is the strategy that concurrent_draft takes -- each part has 'content' and 'draft_content' fields. The nice thing about that is that we could treat parts, snippets and layouts almost identically, with some tweaks for pages (and propagating publishing to the parts). There's no historical versioning, though. Thanks. I'll have to look more closely at it, perhaps my work is redundant. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Looking for draft+history extension collaborators or contractors
Sean, Is there any reason not to use technoweenie's Acts As Versioned plugin (http://github.com/technoweenie/acts_as_versioned/tree/master) for that? Strikes me a natural thing to do. Only that we didn't need versioning for the current application of concurrent_draft. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
