Re: [Radiant] Which extension to use?
On Sun, 2008-06-15 at 17:45 +0100, Andrew Neil wrote: > > You are my frickin' hero! > > :-) > Andrea is the hero. I just took a hatchet to his code! Well the, he rocks, too. In hindsight if I had been able to figure out how the newsletter extension all works, I might have gone that route. As it is, I am using the subscriber lists extension. I am having a problem with it, though. The error is below: ### Showing vendor/extensions/subscriber_lists/app/views/subscribers/index.html.erb where line #15 raised: undefined method `count_active_subscribers' for # Extracted source (around line #15): 12: <% @lists.each do |list| %> 13: 14: <%= list.title %> 15: <%= Subscriber.count_active_subscribers(list) %> 16: <%= link_to "Edit page", page_edit_path(:id => list.id) %> 17: <%= link_to "Export", :action => "export", :id => list.id %> 18: ### I have huffed and I have puffed, but I cannot figure out how why it isn't working. Do you have any thoughts? Radiant 0.6.7, Rails 2.0.2 ~Nate ___ 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-Dev] [ANN] Styles 'n Scripts Extension
I just outlined the fix in a reply to Sean's post. It's a little more elaborate (though I think more elegant) than I'd post here. If you're trying to get it to "just work for now" you can simply comment out the following line from the styles_n_scripts_extension.rb file: include CustomSettings Run your "rake db:bootstrap" to create the database, then un-comment that line back in. -Chris Jim Gay wrote: What was the fix for SnS? I saw the same problem with RBAC Base on a clean install (which I must not have tried when we created it) and haven't had time to look into it. -Jim ___ 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 Digest, Vol 27, Issue 39
> >> When I use >> >> @radiant_layout = 'Main' >> >> it creates the page but displays it in the admin layout. ??? >> If I substitute a fake name for Main, it does the same thing so it >> appears to be defaulting to the admin layout. >> >> > >Do you actually have a layout created in Radiant called "Main"? Yes I have a layout called Main in Radiant. Thanks for any help, Will Emerson ___ 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-Dev] [ANN] Styles 'n Scripts Extension
I'm not opposed to your solution in anyway. I think it'd be helpful. I just think that the "right" solution for my extension would be to: * have my extension's default settings installed via the initial migrate task * offer a rake task to allow administrators (server admins) to change the css/js settings on the fly. This need only be run once manually (after bootstrap) and not at every init. I'd probably throw in a "restore_defaults" task too. I designed the StylesNScripts::Config bit with the future UI designs of Radiant in mind -- for the day when we'll have a settings/configuration admin panel where extensions can add into the Radiant UI (instead of sticking settings in some tab or hard coded and loaded at init). My problem is that I broke this rule and made the settings load during init "just for now" and shot myself in the foot. If I do what I've outlined above, it'll be trivial to hook into Radiant's shiny new settings UI when it arrives -Chris Sean Cribbs wrote: Chris, We might be able to make a rake task that loads the environment with no extensions installed. In fact, it should be as easy as something like this: task :minimal_environment do Radiant::Initializer.run do |config| config.extensions = [] end end Then we could make db:bootstrap and anything else that needs to prevent extensions from loading depend on that instead of the default :environment task. Sean Chris Parrish wrote: For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish <[EMAIL PROTECTED]> wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish <[EMAIL PROTECTED]> ___ 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 mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] share_layouts extension
Nate, I think most of the issues in upgrading to 0.6.7 with the rails_support extension were normal ones you face going to Rails 2. Here is what version control and my memory tells me I changed. -- I backed up the database, dropped all the tables, and ran the migrations for radiant and all extensions. Schema.rb was rewritten in the new 2.0 style. --the new 'protect_from_forgery' functions stopped me for awhile. In my controllers, I had to add the line protect_from_forgery :except => new --in environment.rb I had to add my customizations back in from environment.bak which the upgrade to radiant provided. Be sure to put your "requires" outside of and after the Initialize block. Be sure to set config.plugins = [:all] and config.extensions = [:all] unless you have special requirements. Be sure conf.action_controller.session is uncommented and set. --I had to do the migration for sessions (rake db:sessions:create) and comment out the line session :off at the top of site_controller.rb in ../gems/radiant-0.6.7/app/contollers. This may vary with your needs. I don't really understand how Radiant handles sessions but the forgery protection seems to need sessions. --In my controllers, find_all needs to be replaced by find(:all). --many plugins and gems need to be updated. will_paginate changed from a plugin to a gem so install the gem and remove the plugin and add gem 'mislav-will_paginate', '~> 2.3' require 'will_paginate' to environment.rb Since pagination has been dropped from Rails core, you have to use a gem or plugin. Be sure to get will_paginate from here: gem install mislav-will_paginate --source http://gems.github.com/ to get the latest version. My queries were getting messed up after page 1 until I got the latest gem and made sure I was referencing it. --If you use the Gallery extension, it needs to be updated to the latest version. --main.css in admin changed and any customization you have made needs to be merged. --Old scaffolding doesn't work. I just created views for the little-used admin controllers where I had been lazy and used scaffolding. So basically once I got past these hurdles, the rails_support extension worked just fine. Good luck upgrading! Will Emerson ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Which extension to use?
Nate, Glad you like it. You are my frickin' hero! :-) Andrea is the hero. I just took a hatchet to his code! can I add additional columns in extension migrations or will it somehow break the extension? Give it a go. I don't think it should break anything. If you want the extra fields to be added to the CSV export, then you should modify the export action in the SubscribersController as follows: def export @list = Page.find(params[:id]) subscribers = Subscriber.find_active_subscribers_by_subscriber_list(@list) stream_csv do |csv| csv << ["email","name","your additional column name] subscribers.each do |subscriber| csv << [subscriber.email,subscriber.name,subscriber.additional_column] end end end Cheers, Drew ___ 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-Dev] [ANN] Styles 'n Scripts Extension
Chris, We might be able to make a rake task that loads the environment with no extensions installed. In fact, it should be as easy as something like this: task :minimal_environment do Radiant::Initializer.run do |config| config.extensions = [] end end Then we could make db:bootstrap and anything else that needs to prevent extensions from loading depend on that instead of the default :environment task. Sean Chris Parrish wrote: For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish <[EMAIL PROTECTED]> wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish <[EMAIL PROTECTED]> ___ 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
Re: [Radiant] Which extension to use?
On Sun, 2008-06-15 at 16:04 +0100, Andrew Neil wrote: > Me too! I've had some time to develop something this weekend, and here > it is: > > > http://github.com/nelstrom/radiant-subscriber-lists-extension/tree/master > > I was very impressed by Andrea's Newsletter extension, but configuring > a Linux server to send mail is a big hole in my knowledge. I could not > make it work in production, so regretfully had to move on. > > I have basically simplified the Newsletter extension so that it > doesn't send any mail. That means an email address is added to the > list instantly upon form submission, rather than sending an email with > activation code. Likewise, the unsubscribe form removes a subscriber > instantly, without verification. This might not be the *best* way of > doing things, but I think some clients will actually prefer it. > > Everything is in place for this extension to work on the public facing > side of a site. The admin side, however, is unfinished at this stage. > Right now, there is no means to add or edit users in the admin. I have > created an Export action, which outputs all subscribers for a list as > a CSV file. > > If you want to try it out, I'd be pleased to hear any feedback. Drew, You are my frickin' hero! I was staring at the various parts of the newsletter extension last night trying to size up the task ahead. Then I check my email today and you've already done what I wanted to do, and you even added CSV export. I have already installed it. I do have one question though, and this may apply to all migrations of extensions: can I add additional columns in extension migrations or will it somehow break the extension? I was just wondering if they are somehow different from normal rails migrations. Thanks, Nate ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Which extension to use?
On 13 Jun 2008, at 05:22, Jim Gay wrote: On Jun 13, 2008, at 12:06 AM, [EMAIL PROTECTED] wrote: I am trying to figure out how to add a sign up page for a newsletter my client want to send out. Thats on my list of things to do as well. Me too! I've had some time to develop something this weekend, and here it is: http://github.com/nelstrom/radiant-subscriber-lists-extension/tree/master I was very impressed by Andrea's Newsletter extension, but configuring a Linux server to send mail is a big hole in my knowledge. I could not make it work in production, so regretfully had to move on. I have basically simplified the Newsletter extension so that it doesn't send any mail. That means an email address is added to the list instantly upon form submission, rather than sending an email with activation code. Likewise, the unsubscribe form removes a subscriber instantly, without verification. This might not be the *best* way of doing things, but I think some clients will actually prefer it. Everything is in place for this extension to work on the public facing side of a site. The admin side, however, is unfinished at this stage. Right now, there is no means to add or edit users in the admin. I have created an Export action, which outputs all subscribers for a list as a CSV file. If you want to try it out, I'd be pleased to hear any feedback. Cheers, Drew ___ 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-Dev] [ANN] Styles 'n Scripts Extension
What was the fix for SnS? I saw the same problem with RBAC Base on a clean install (which I must not have tried when we created it) and haven't had time to look into it. -Jim On Jun 15, 2008, at 9:19 AM, Chris Parrish wrote: For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish <[EMAIL PROTECTED] > wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish <[EMAIL PROTECTED] > ___ 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
Re: [Radiant] Re: Re: [Radiant-Dev] [ANN] Styles 'n Scripts Extension
For anyone (now or in the future) following this thread, I've identified the issue nurullah mentioned here. It is indeed a bug with the SnS extension and will be resolved in the upcoming 0.5 release. For those interested, it's caused by the interplay between the way SnS extension stores its settings, and the way Radiant rake tasks are performed. SnS creates its default settings and then overwrites those with any custom settings during initialize. Well, it turns out that extensions are initialized during any Rake task -- including 'rake db:bootstrap' So, if you're including SnS in a *brand new* installation of Radiant (not already bootstrapped), when you try to create the database, the SnS extension gets initialized and tries to store some settings in the not-yet-created config table. Doh! Those adding SnS to an existing Radiant install will never see this issue. -Chris nurullah wrote: although all installation steps fail it adds tabs on panels and some columns on config table 5|stylesheet_mime_type|text/css 6|response_cache_directory|text_asset_cache 7|javascript_mime_type|text/javascript 8|javascript_directory|js 9|stylesheet_directory|css but you are right production.log says it cannot find text_assets table and right there is no such table on db file On 5/19/08, Chris Parrish <[EMAIL PROTECTED]> wrote: The Styles 'n Scripts extension makes use of Radiant's built-in Radiant::Config settings (which get stored in the config table). So this sound like a Radiant setup issue. (The only table my extension adds is text_assets). Remove my extension (all extensions, really) and make sure that your plain-vanilla Radiant extension has this table created (should have been created when you ran: rake db:bootstrap (or rake production db:bootstrap if running in production mode). -Chris Arik Jones wrote: I think this is a fault of Radiant. Could be wrong. nurullah wrote: I could get it run on a clean install (0.6.7) tho, with sqlite3 and no other extension installed it gives Could not find table 'config' error On 5/18/08, Chris Parrish <[EMAIL PROTECTED]> ___ 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] Re: ruby 1.8.7
Hi all - No other experiences or other wisdom on this issue? I am guessing the solution for now is to go back to 1.8.6 - but it'll have to be addressed sooner or later, 1.8.7 is the new recommended stable version offered for tarball download at http://www.ruby-lang.org/en/downloads/ . thanks, Sho On 13/06/2008, at 3:10 AM, Sho Fukamachi wrote: Hi Radiant People, I've had a lot of trouble getting a radiant installation running properly on a new server which has been updated to Ruby 1.8.7. I've had to do a number of things to stop Enumerable and String errors, but I've been able to do that without all that much difficulty. What's really stopped me is the page_attachments plugin, which seems completely dysfunctional under 1.8.7. I'm using a copy I got from the radiant SVN repository. Is this the latest version? I can't access the repo named on the radiant website, svn.seancribbs.com. I'm wondering if anyone else has had these problems or whether I'm the first to try to run radiant on 1.8.7 - and what I should do to fix these problems ; ) thanks a lot Sho ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Image links to radiantcms.org in Radiant?
Sometimes, I'm on an Internet connection that is excruciatingly slow. That would seem like no problem when working with Radiant on my laptop alone. But, it seems that there's something in editing a page that accesses radiantcms.org. I'm sure it's not malicious, but it does sometimes prevent me from getting on and editing the page because my browser shows 'loading...' for quite a while. I've done some looking around and it seems that the offending part is: bq. Roses are red, violets are blue, Textile is nice, and so are you! http://radiantcms.org/button.png"; alt="" /> !http://radiantcms.org/button.png! Is there anyone willing to change it? It's a minor annoyance, not urgent at all :) Cheers, Mohit. 6/15/2008 | 4:24 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Slight confusion about other 'public' areas
Hi, so far, I've used Radiant only on sub-domains to manage a portion of the site. Now, for one of the companies that I'm attached with, I'm thinking of using Radiant to manage the main site. The problem/ confusion is this: we use shared hosting, so the site has a public_html folder that is supposed to be where all the public HTML content goes. According to the tutorials, I'm supposed to rename public_html to something else and then create a symbolic link from there to the public folder of my Radiant instance. So far so good. Currently, we create a number of directories under the main site such as clients/name and password protect that directory so that a client can access it for the files we want to pass to them, and so on. How do I make that model work under Radiant? Does everything need to be copied under the Radiant public? Do I create symbolic links? CPanel has a trivially simple way to password protect directories, but I'm not sure how I will deal with that under Radiant. Also, Radiant throws up a 'Page Not Found' if you try to 'browse' a directory under public (e.g. example.com/images) though access to a specific file does work of course. Thanks for any guidance. Cheers, Mohit. 6/15/2008 | 3:03 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
