Re: [Radiant] Radiant 0.8.0 Asterism Release
Sean Cribbs wrote: Michael Kessler Kunal Shah Brett McHargue Jim Gay Jason GarberKunal Shah Matt HenryRick DeNatale Pat Allan Josh French Brent Kroeker Sean Cribbs Thanks guys! If you'd like to hop on the development Kunal must have done an awful lot of development to get mentioned twice :P but seriously, all you guys - Thanks!! Cheers, Mohit. 6/15/2009 | 2:11 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] multi_site extension and mysql error
Hi Daniel, I've fixed these problems in a fork: http://github.com/p8/radiant-multi-site-extension/tree/master Your probably want to comment out the following line since a previously failed migration already created the column. Line 3 in vendor/extensions/multi_site/db/ 003_add_base_domain_to_sites.rb: add_column :sites, :base_domain, :string Petrik ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Creating a UL/IMG based Navigation Bar
Hi Jeff, Sorry, but that snippet looks like a recipe for disaster.. Here's some feedback; 1/ You use r:url / as part of the image name. This means that, when you have deeper-nested pages, you would get image names like products/cats.gif, which is not going to work. You could use r:slug / instead, which would only produce cats.gif. 2/ You don't seem to understand the use of the r:navigation tag; r:navigation urls=Title: /news | Title: /about | Title: /contact It's supposed to be something like urls=Blog: /news | About us: /about | Contact us: /contact 3/ You use only images as content for your links. The fallback (alt attribute) is just the url, which makes for a very poor navigation for clients that cannot see images (think people surfing through WAP, people with a visual handicap, and probably foremost; spider bots like google and the like). What you need to do is provide a text entry that makes more sense as linktext, and then replace that text with the image you want through CSS. You will need a unique id attribute on your li and/or a tags. 4/ Perhaps you should look into the navigation_tags extension. The r:nav / tag could make your life much easier. Since you want to use images, you would want to use ids_for_links=true or ids_for_lis=true. Check the (somewhat outdated) README at http://github.com/jomz/navigation_tags/tree/master I can not provide too much details about the CSS implementation, since that is my colleague's part of the job, but you can see a live implementation at http://www.indewulf.be. Also notice the plethora of handy css hooks r:nav provides. Regards, Benny Hi All, Today is my first day building my site with Radiant -- I'm loving it! Once I got the basic layout, snippets, and pages implemented, I had to figure out my navigation bar. It took me some tinkering, so I thought I'd post the results on the wiki: http://wiki.github.com/radiant/radiant/creating-a-ul-img-based-navigation-bar I'd appreciate any feedback or redirection if I did something ugly. I wrestled with the wiki for a few minutes trying to figure out why those extra grey spaces were showing up under each code block, but I didn't crack the problem. - Jeff ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant 0.8.0 Asterism Release
Sorry, I also mistakenly left out David Cato. Sean Mohit Sindhwani wrote: Sean Cribbs wrote: Michael Kessler Kunal Shah Brett McHargue Jim Gay Jason GarberKunal Shah Matt HenryRick DeNatale Pat Allan Josh French Brent Kroeker Sean Cribbs Thanks guys! If you'd like to hop on the development Kunal must have done an awful lot of development to get mentioned twice :P but seriously, all you guys - Thanks!! Cheers, Mohit. 6/15/2009 | 2:11 PM. ___ 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: multi_site extension and mysql error
Upon migrating getting mysql error: == 3 AddBaseDomainToSites: migrating == -- add_column(:sites, :base_domain, :string) rake aborted! Mysql::Error: Duplicate column name 'base_domain': ALTER TABLE `sites` ADD `base_domain` varchar(255) Hi Daniel, Looks like one of your earlier install attempts failed halfway through the extension migration. You have the full multisite schema, but this is not recorded in the schema_migrations table. Possible solutions: * Drop the sites table and remigrate the multisite extension. This is destructive, and if your schema_migrations is stuck at an intermediate version you'll have further problems. * Alter schema_migrations so that it contains all 3 multisite migrations. This is the quicker/easier fix. j On Jun 14, 2009, at 12:54 PM, radiant-requ...@radiantcms.org wrote: Send Radiant mailing list submissions to radiant@radiantcms.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.radiantcms.org/mailman/listinfo/radiant or, via email, send a message with subject or body 'help' to radiant-requ...@radiantcms.org You can reach the person managing the list at radiant-ow...@radiantcms.org When replying, please edit your Subject line so it is more specific than Re: Contents of Radiant digest... Today's Topics: 1. Creating a UL/IMG based Navigation Bar (Jeff Casimir) 2. multi_site extension and mysql error (Daniel O'Connell) 3. Re: Back Door conditionals iffy? (Steven Southard) 4. Re: Re: Possible to disable cache for a single page? (Nicholas Henry) -- Message: 1 Date: Sat, 13 Jun 2009 13:25:07 -0400 From: Jeff Casimir j...@casimircreative.com Subject: [Radiant] Creating a UL/IMG based Navigation Bar To: radiant@radiantcms.org Message-ID: 70dad9df0906131025m6d3b4894ue9f4882459f5d...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 Hi All, Today is my first day building my site with Radiant -- I'm loving it! Once I got the basic layout, snippets, and pages implemented, I had to figure out my navigation bar. It took me some tinkering, so I thought I'd post the results on the wiki: http://wiki.github.com/radiant/radiant/creating-a-ul-img-based-navigation-bar I'd appreciate any feedback or redirection if I did something ugly. I wrestled with the wiki for a few minutes trying to figure out why those extra grey spaces were showing up under each code block, but I didn't crack the problem. - Jeff -- Message: 2 Date: Sat, 13 Jun 2009 14:15:35 -0600 From: Daniel O'Connell d...@mac.com Subject: [Radiant] multi_site extension and mysql error To: radiant@radiantcms.org Message-ID: be0a9d26-49db-4d96-a1b6-0baa61220...@mac.com Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Hello to all, My first post to any list. I am new to radiant and rails and head long into my first project, a client website. I'm trying to install multi_site on Radiant 0.7.1. Using script/ extension install leads to a version that seems to be for radiant 0.8.0 (see multi_site_extension.rb) and will not correctly migrate. The very kind Josh French gave me instruction to check out the 0.7.1 tagged version, but I am still having problems Upon migrating getting mysql error: == 3 AddBaseDomainToSites: migrating == -- add_column(:sites, :base_domain, :string) rake aborted! Mysql::Error: Duplicate column name 'base_domain': ALTER TABLE `sites` ADD `base_domain` varchar(255) Restarted server hoping for the best, but Radiant crashes with an Application Error and I cannot login to admin and public site doesn't function. Using ray I disabled the extension and site is back online, but I really need this extension to work properly. Any ideas? Always Victory! -Daniel -- Message: 3 Date: Sat, 13 Jun 2009 15:16:17 -0500 From: Steven Southard ste...@stevensouthard.com Subject: Re: [Radiant] Back Door conditionals iffy? To: radiant@radiantcms.org Message-ID: 37a56ee1-1eb1-4b1d-a63b-a1e61c441...@stevensouthard.com Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Of course, that is much better. I sure like the idea of Back Door but giving up caching seems a high cost. On Jun 13, 2009, at 5:05 AM, Jim Gay wrote: It would appear that caching is not a good idea with that extension. I think you would be better served using Microsoft's conditional comments. Jim On Jun 13, 2009, at 2:26, Steven Southard ste...@stevensouthard.com wrote: Sure seem to be, which makes me wonder how this example shown at http://backdoor.rubyforge.org/ could ever be reliable. r:if cond=request.env[ 'HTTP_USER_AGENT'] =~ /MSIE/ !-- Internet Explorer needs some ugly hacks to render PNG images with transparency -- div id=logo
[Radiant] Rails 2.3 Templates WAS: Radiant 0.8.0 Asterism Release
Now that Radiant is on Rail 2.3, has anyone investigated (or planning to investigate) using application templates to simplify things? For example, its often been asked if there were an easy way to share template sites and/or themes. This has always been hard to do but it occurs to me that with templates, this will be MUCH easier. Similarly, we have a problem of how to ensure dependencies are met for installing extensions. I'm wondering if: 1. anyone else sees value in pursuing templates as a generalized mechanism to more easily bootstrap radiant sites (ala radiant -t http://www.example.com/my_cool_theme.rad NewSite) or installing and uninstalling extensions 2. anyone is already working on it... I'm rather busy on other fronts these days, so if someone is already thinking about it, I'd rather collaborate than start from scratch. Adam On Sun, Jun 14, 2009 at 12:40 PM, Sean Cribbs seancri...@gmail.com wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.8.0 Asterism features a brand new and more compliant caching mechanism based on Rack::Cache, and numerous bugfixes and small enhancements. Also included are: * An extensive integration suite using Cucumber and Webrat * Rails 2.3.2 (previously 2.1.2) * Highline 1.5.1 * Haml 2.0.9 Many thanks to our contributors and committers for their contributions. WHAT IS RADIANT CMS? Radiant is a no-fluff content management system made for designers and programmers and is ideal for use on small teams. It is similar to Movable Type or Textpattern, but is much more than a blogging engine. Radiant features: * An elegant user interface * The ability to arrange pages in a hierarchy * Flexible templating with layouts, snippets, page parts, and a custom tagging language (Radius: http://radius.rubyforge.org) * A dynamic extension system * A simple user management/permissions system * Support for Markdown and Textile as well as traditional HTML (it's easy to create other filters) * Operates in two modes: dev and production depending on the URL * A caching system which expires pages every 5 minutes * Built using Ruby on Rails (which means that extending Radiant is as easy as any other Rails application) * Licensed under the MIT-License * And much more... There's even a live demo over on the project Web site: http://radiantcms.org/demo/ WHAT'S NEW IN THIS RELEASE? * Warn about using the RedCloth 3 fallback. [Sean Cribbs, Jason Garber] * Prevent stty errors on JRuby while running bootstrap. [Sean Cribbs] * Moved template_name to ApplicationController [Jim Gay, Michael Kessler] * Remove vizres plugin. [Sean Cribbs] * Update instance config/environments to remove ResponseCache [Jim Gay] * Remove :order option from r:children:count /, which causes errors on postgresql. [Sean Cribbs] * Prevent recursion via the r:content / tag. [Sean Cribbs] * Update Highline. [Sean Cribbs] * Update Cucumber and RSpec, clean up some features and fix specs. [Sean Cribbs] * Set the protected attributes for users in User.protected_attributes [Jim Gay] * Don't allow a nil ETag in SiteController. [David Cato] * Prevent failed login message from sticking around. [Kunal Shah] * Fix failing test regarding extension order. [Brett McHargue] * Catch ActiveRecord::RecordNotFound in Admin::ResourceController [Jim Gay] * Catch missing template errors for show routes [Jim Gay] * Fix with_error in render_matcher not causing the spec to fail when no exception raised. [Jason Garber] * Make features task run in instance mode. [Sean Cribbs] * Remove Admin::AbstractModelController. [Sean Cribbs] * Cleanup deprecated Gem::manage_gems. [Sean Cribbs] * Add begin...rescue blocks to rspec.rake [Sean Cribbs] * Add begin...rescue blocks for requiring cucumber. [Matt Henry] * Deprecate ResponseCache, add Radiant::Cache based on Rack::Cache. [Sean Cribbs] * Use app name for session cookie. [Josh French] * Upgrade to Rails 2.3.2. [Sean Cribbs, Rick DeNatale, Josh French, Kunal Shah] * Populate config.extensions so extensions can be disabled easily. [Jason Garber] * Convert integration specs to Cucumber stories and update RSpec. [Sean Cribbs] * Use ActionView::PathSet instead of normal arrays for view paths. [Pat Allan] * Don't raise exception on unauthenticated request to /admin/logout. [Josh French] * Reverse view paths order in extension loader. [Sean Cribbs, Brent Kroeker] * Remove obviated Ruby 1.8.7 compatibility patch. [Sean Cribbs] * Adjust StandardTags#relative_url_for for case when relative_url_root is nil. [Sean Cribbs] * Correct rendering error in extensions controller. [Sean Cribbs] * Correct typo in config/boot.rb. [Sean Cribbs] * Major refactoring and simplification of LoginSystem. [Sean Cribbs] * Update Haml to 2.0.7. [Sean Cribbs] * Upgrade to Rails 2.2.2. [Sean Cribbs] * Cleanup the config class a little, add some more
Re: [Radiant] Rails 2.3 Templates WAS: Radiant 0.8.0 Asterism Release
Adam van den hoven wrote: I'm wondering if: 1. anyone else sees value in pursuing templates as a generalized mechanism to more easily bootstrap radiant sites (ala radiant -t http://www.example.com/my_cool_theme.rad NewSite) or installing and uninstalling extensions I think that would be awesome. It would be nice to set up a site template with all the extensions I use on a regular basis. 2. anyone is already working on it... I'm rather busy on other fronts these days, so if someone is already thinking about it, I'd rather collaborate than start from scratch. Likewise, I have little time to breathe, let alone start another project. But if it was started, I would certainly do what I can to help further it along. ~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] Rails 2.3 Templates WAS: Radiant 0.8.0 Asterism Release
Adam, I've used Rails templates to bootstrap some apps, and it's really just a hook into the existing Rails generators, plus some extra tools. That said, some kind of template distribution mechanism would be awesome. When it's ready, we can integrate it into the instance generator. PDI Sean Adam van den hoven wrote: Now that Radiant is on Rail 2.3, has anyone investigated (or planning to investigate) using application templates to simplify things? For example, its often been asked if there were an easy way to share template sites and/or themes. This has always been hard to do but it occurs to me that with templates, this will be MUCH easier. Similarly, we have a problem of how to ensure dependencies are met for installing extensions. I'm wondering if: 1. anyone else sees value in pursuing templates as a generalized mechanism to more easily bootstrap radiant sites (ala radiant -t http://www.example.com/my_cool_theme.rad NewSite) or installing and uninstalling extensions 2. anyone is already working on it... I'm rather busy on other fronts these days, so if someone is already thinking about it, I'd rather collaborate than start from scratch. Adam ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] NYC Radiant Meetup 2
All, It's that time of the month again. We had a good turn-out at the last meetup. So if you're in the NYC area and you want to meet up and chat about Radiant (and whatever might be on your mind) come through: NYC Radiant Meetup 2 Wednesday, June 24 at 6:00 PM Location: TBD http://anyvite.com/events/home/ymepaqnrbe The venue that I picked last time was a bit more crowded than I had expected, so I'm leaving the venue TBD for now. I'm open to any and all suggestions for location. Please RSVP if you're going to come. Trying to make this a monthly happening, so if you can't make it out this time, there's always the next one. Charlie ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Forcing Production
Hi All, Well, my first contribution was apparently flawed, but I'm working on it. :) Now that my site is up and running I wanted to install a few extensions to add functionality. I have really been fighting with the install process trying to force it to work with the PRODUCTION environment, but it just wouldn't listen. I tried many iterations of command line parameters, explicitly set the RAILS_ENV in environment.rb, and was getting pretty frustrated. The installs were still erroring out when trying to fork off rake tasks. I read through some old discussions that Google found, but never saw an applicable solution. I looked through the Rakefile and finally had an idea. Rake wasn't looking at environment.rb, it was going for boot.rb. So I opened up my config/boot.rb, casually ignored the warnings at the top of the file, and put the following on the first line: ENV['RAILS_ENV'] = 'production' Now everything is golden. Installs are no problem. Is this dumb or bad practice for some reason? - Jeff ___ 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: Creating a UL/IMG based Navigation Bar
Benny, Thanks for the feedback. I agree with you for the most part, but my testing didn't show the results I expected. When I used r:slug within the r:navigation tags, instead of getting the slug for that element I got the slug for the current page. Thus each element of the navigation would end up with the same data, same results, all pointing to the current page. I assumed I was misunderstanding, but maybe it's a bug? I'm using 0.8. And, actually, using the r:url works better than expected. In the situation of... http://site.com/branch/leaf/ The r:url is correctly pulling branch. So I guess what I'm saying, is that I agree it should be wrong, but it works? Do you see different results? As far as the CSS image substitution, you're probably right that it would be a better setup, but this is ok for me right now. - Jeff On Mon, Jun 15, 2009 at 4:13 AM, Benny Degezellebe...@gorilla-webdesign.be wrote: Hi Jeff, Sorry, but that snippet looks like a recipe for disaster.. Here's some feedback; 1/ You use r:url / as part of the image name. This means that, when you have deeper-nested pages, you would get image names like products/cats.gif, which is not going to work. You could use r:slug / instead, which would only produce cats.gif. 2/ You don't seem to understand the use of the r:navigation tag; r:navigation urls=Title: /news | Title: /about | Title: /contact It's supposed to be something like urls=Blog: /news | About us: /about | Contact us: /contact 3/ You use only images as content for your links. The fallback (alt attribute) is just the url, which makes for a very poor navigation for clients that cannot see images (think people surfing through WAP, people with a visual handicap, and probably foremost; spider bots like google and the like). What you need to do is provide a text entry that makes more sense as linktext, and then replace that text with the image you want through CSS. You will need a unique id attribute on your li and/or a tags. 4/ Perhaps you should look into the navigation_tags extension. The r:nav / tag could make your life much easier. Since you want to use images, you would want to use ids_for_links=true or ids_for_lis=true. Check the (somewhat outdated) README at http://github.com/jomz/navigation_tags/tree/master I can not provide too much details about the CSS implementation, since that is my colleague's part of the job, but you can see a live implementation at http://www.indewulf.be. Also notice the plethora of handy css hooks r:nav provides. Regards, Benny Hi All, Today is my first day building my site with Radiant -- I'm loving it! Once I got the basic layout, snippets, and pages implemented, I had to figure out my navigation bar. It took me some tinkering, so I thought I'd post the results on the wiki: http://wiki.github.com/radiant/radiant/creating-a-ul-img-based-navigation-bar I'd appreciate any feedback or redirection if I did something ugly. I wrestled with the wiki for a few minutes trying to figure out why those extra grey spaces were showing up under each code block, but I didn't crack the problem. - Jeff ___ 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: Creating a UL/IMG based Navigation Bar
On Mon, Jun 15, 2009 at 3:12 PM, Jeff Casimirj...@casimircreative.com wrote: Benny, instead of getting the slug for that element I got the slug for the current page. you are getting the current page slug because radius tags render within the context from which they're called. to get around that and at the slug for each page in an iteration you can do something like: r:pager:slug//r:page And, actually, using the r:url works better than expected. In the situation of... http://site.com/branch/leaf/ The r:url is correctly pulling branch. So I guess what I'm saying, is that I agree it should be wrong, but it works? Do you see different results? As far as the CSS image substitution, you're probably right that it would be a better setup, but this is ok for me right now. - Jeff On Mon, Jun 15, 2009 at 4:13 AM, Benny Degezellebe...@gorilla-webdesign.be wrote: Hi Jeff, Sorry, but that snippet looks like a recipe for disaster.. Here's some feedback; 1/ You use r:url / as part of the image name. This means that, when you have deeper-nested pages, you would get image names like products/cats.gif, which is not going to work. You could use r:slug / instead, which would only produce cats.gif. 2/ You don't seem to understand the use of the r:navigation tag; r:navigation urls=Title: /news | Title: /about | Title: /contact It's supposed to be something like urls=Blog: /news | About us: /about | Contact us: /contact 3/ You use only images as content for your links. The fallback (alt attribute) is just the url, which makes for a very poor navigation for clients that cannot see images (think people surfing through WAP, people with a visual handicap, and probably foremost; spider bots like google and the like). What you need to do is provide a text entry that makes more sense as linktext, and then replace that text with the image you want through CSS. You will need a unique id attribute on your li and/or a tags. 4/ Perhaps you should look into the navigation_tags extension. The r:nav / tag could make your life much easier. Since you want to use images, you would want to use ids_for_links=true or ids_for_lis=true. Check the (somewhat outdated) README at http://github.com/jomz/navigation_tags/tree/master I can not provide too much details about the CSS implementation, since that is my colleague's part of the job, but you can see a live implementation at http://www.indewulf.be. Also notice the plethora of handy css hooks r:nav provides. Regards, Benny Hi All, Today is my first day building my site with Radiant -- I'm loving it! Once I got the basic layout, snippets, and pages implemented, I had to figure out my navigation bar. It took me some tinkering, so I thought I'd post the results on the wiki: http://wiki.github.com/radiant/radiant/creating-a-ul-img-based-navigation-bar I'd appreciate any feedback or redirection if I did something ugly. I wrestled with the wiki for a few minutes trying to figure out why those extra grey spaces were showing up under each code block, but I didn't crack the problem. - Jeff ___ 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] Newsletter extension
you know any extension compatible with 0.7x, which serves to collect email addresses (newsletter) I found only one, but this is not compatible with version 0.5 if not can someone help me thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Newsletter extension
Mauricio Dulce wrote: you know any extension compatible with 0.7x, which serves to collect email addresses (newsletter) I found only one, but this is not compatible with version 0.5 if not can someone help me Use Mailer for your form and Database_Mailer to collect those submissions. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Newsletter extension
I have run mailer _extension, i can't install other extension whit the same name or this is possible El 15/06/2009, a las 16:34, N. Turnage escribió: Mauricio Dulce wrote: you know any extension compatible with 0.7x, which serves to collect email addresses (newsletter) I found only one, but this is not compatible with version 0.5 if not can someone help me Use Mailer for your form and Database_Mailer to collect those submissions. ~N ___ 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] Newsletter extension
Mauricio Dulce wrote: I have run mailer _extension, i can't install other extension whit the same name or this is possible You have to have Mailer extension installed first, then Database_Mailer. D_M was made to work with Mailer. ~N ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Forcing Production
Jeff Casimir wrote: I looked through the Rakefile and finally had an idea. Rake wasn't looking at environment.rb, it was going for boot.rb. So I opened up my config/boot.rb, casually ignored the warnings at the top of the file, and put the following on the first line: ENV['RAILS_ENV'] = 'production' Now everything is golden. Installs are no problem. Is this dumb or bad practice for some reason? I believe that the general practice is to run rake as: rake production when installing extensions, etc. I don't think people would usually change boot.rb - on the other hand, if it works for you, it 'works for you' :) Cheers, Mohit. 6/16/2009 | 1:04 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
