We’ve received several reports that Ruby 1.8.7, which includes backports of functionality from the 1.9 branch breaks Radiant, primarily with respect to the Enumerator class. Please use Ruby 1.8.6 or earlier until we can resolve this issue. Contributed patches that resolve the issues while maintaining backward-compatibility with 1.8.6 and earlier would be appreciated.
RailsConf 2008 is only 5 days away! If it is anything like last year, we’ll have a large contingent of people interested in Radiant at the conference. We have several Radiant-related things going on, so here’s the lowdown.
First will be the community code drive on Thursday, 10AM-5PM. I don’t think you need to be registered for tutorials to participate, but if you’re not, lunch will be on your own. The goal of this drive will be to build a formal extension registry that will include scripts that can be used to install and uninstall extensions, track dependencies, etc. Although completing this will be my goal, there’s plenty of room for hacking on extensions, bugfixes and enhancements. Please come join us!
Radiant will have its own BoF session, moderated by Loren Johnson and myself. It will be very unstructured and could include Q&A, lightning talks, or whatever people want. It has not been scheduled yet by the organizers, so I’ll post details here as soon as we have a time blocked off.
I’ll be looking to interview some people for the podcast during RailsConf, so come find me and tell me about your Radiant projects.
Several people have talked to me about meeting informally for food and drink at some point. We’ll likely do this after the BoF session, but I’ll be available and interested to talk to any of you during the conference as well.
See you at RailsConf!
P.S. John Long and Adam Williams will not be in attendance. They will be missed!
Casper Fabricius has posted a wonderful tutorial about how to deploy Radiant on Dreamhost using their new Phusion Passenger setup. If you’re looking for a simple, inexpensive Radiant deployment option, check out his tutorial.
Radiant 0.6.7 “Mordant” resolves several security holes and includes enhancements for developers.
radiant:extensions:update_all Rake task has been added to simplify copying assets from extensions into the public/ folder.Attention extension developers: If you were using “shards” to modify the user views, please verify that your extension is unaffected. The structure of the partials and regions in the edit view has slightly changed.
To install use the gem command (with ‘sudo’ as necessary):
$ gem install radiant1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.7” or remove it altogether.
2. Update the Radiant assets in your project:
rake radiant:update3. Copy your customizations back into config/environment.rb, if necessary (see below).
4. Migrate the database:
rake production db:migrate5. Restart the server
1. Invoke the radiant command with your desired database driver:
$ radiant -d sqlite3 my_project2. Bootstrap the database:
$ cd my_project
$ rake db:bootstrap3. Startup the server and try it out!
$ script/serverconfig/environment.rbThe 0.6.5 release required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we made significant changes to config/environment.rb and config/boot.rb. When updating your existing projects, config/environment.rb will be copied to config/environment.bak. You will need to manually copy any customizations, especially config.extensions and any other libraries, etc. that you require. DO NOT copy config.load_paths, config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. If you have further questions, please address them to the mailing list. THIS BACKUP BEHAVIOR WILL BE REMOVED IN A FEW RELEASES.
Radiant 0.6.6 “Chiseled” corrects two showstopper bugs in yesterday’s 0.6.5 release that affect upgrading existing installations and the proper functioning of view templates in extensions. All users of 0.6.5 should upgrade immediately. My apologies to all who installed 0.6.5 and had problems!
To install use the gem command (with ‘sudo’ as necessary):
$ gem install radiant1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.6” or remove it altogether.
2. Update the Radiant assets in your project:
rake radiant:update3. Copy your customizations back into config/environment.rb, if necessary (see below).
4. Migrate the database:
rake production db:migrate5. Restart the server
1. Invoke the radiant command with your desired database driver:
$ radiant -d sqlite3 my_project2. Bootstrap the database:
$ cd my_project
$ rake db:bootstrap3. Startup the server and try it out!
$ script/serverconfig/environment.rbThe 0.6.5 release has required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we have made significant changes to config/environment.rb and config/boot.rb. When updating your existing projects, config/environment.rb will be copied to config/environment.bak. You will need to manually copy any customizations, especially config.extensions and any other libraries, etc. that you require. DO NOT copy config.load_paths, config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. If you have further questions, please address them to the mailing list.
It’s finally here! Radiant 0.6.5 “Chisel”, after over 4 months of grueling anticipation, is released. This represents a major leap forward for Radiant. The major changes are:
In addition to those major changes, these enhancements may be of interest:
<meta> tags using the r:meta family of tags.r:find tag now accepts relative paths.For developers:
created_by and updated_by fields on all models have been renamed to created_by_id and updated_by_id, respectively.public/javascripts/admin.To install use the gem command (with ‘sudo’ as necessary):
$ gem install radiantThe gem will install as ‘radiant-0.6.5’.
1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.5” or remove it altogether.
2. Update the Radiant assets in your project:
rake radiant:updateUPDATE: There is a minor bug when upgrading if the public/javascripts/admin directory does not exist. Please create this directory in your project to alleviate the problem. The bug has been fixed in edge.
3. Copy your customizations back into config/environment.rb, if necessary (see below).
4. Migrate the database:
rake production db:migrate5. Restart the server
1. Invoke the radiant command with your desired database driver:
$ radiant -d sqlite3 my_project2. Bootstrap the database:
$ cd my_project
$ rake db:bootstrap3. Startup the server and try it out!
$ script/serverconfig/environment.rbThis release has required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we have made significant changes to config/environment.rb and config/boot.rb. When updating your existing projects, config/environment.rb will be copied to config/environment.bak. You will need to manually copy any customizations, especially config.extensions and any other libraries, etc. that you require. DO NOT copy config.load_paths, config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. If you have further questions, please address them to the mailing list.
The first episode of the Radiant Podcast is now available. In our first episode, Sean interviews John Bachir and Josh French of Digital Pulp. In future episodes, we plan to speak with John Long, James Macaulay and Tobias Luetke of shopify, and a number of other prominent Radiant users.
Subscribe and enjoy!
It’s time for another release candidate of Radiant 0.6.5! Thanks to “Radiant Day” and some healthy participation, we’re almost there. It is my feeling that we’ll likely have a final release next week. As before, these are the big changes in 0.6.5:
In addition to those several significant changes have been made since 0.6.5 RC1:
You can download the Radiant 0.6.5 RC2 here.
This release candidate is intended for developers and is NOT intended for production use. Please report any bugs you find to the development site.
To install use the gem command (with ‘sudo’ as necessary):
$ gem install radiant-0.6.5-rc2.gemThe gem will install as ‘radiant-0.6.5’.
1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.5” or remove it altogether.
2. Update the Radiant assets in your project:
rake radiant:update3. Copy your customizations back into config/environment.rb, if necessary (see below).
4. Migrate the database if you are running 0.6.2 or earlier:
rake production db:migrate5. Restart the server
1. Invoke the radiant command with your desired database driver:
$ radiant -d sqlite3 my_project2. Bootstrap the database:
$ cd my_project
$ rake db:bootstrap3. Startup the server and try it out!
$ script/serverconfig/environment.rbThis release has required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we have made significant changes to config/environment.rb and config/boot.rb. When updating your existing projects, config/environment.rb will be copied to config/environment.bak. You will need to manually copy any customizations, especially config.extensions and any other libraries, etc. that you require. DO NOT copy config.load_paths, config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. If you have further questions, please address them to the mailing list.
As explained on the mailing list, in an effort to encourage contributions to Radiant, we have created an experimental clone of the Radiant SVN repository on GitHub. If you are on GitHub, we encourage you to fork Radiant, work on some bugs, specs, or features, and then send a pull request to Sean. If you are not on GitHub, or have no idea what ‘git’ is, ask your friends for a GitHub invite (sorry I used all of mine) and then check out the wonderful PeepCode screencast.
Brian Dillard is doing an interesting series of articles on his experience working on converting the Pathfinder Website to Radiant. You can read more about it over on the Pathfinder Weblog:
Mohit Sindhwani has also written a couple of articles helping people get up on running on Radiant:
Are you blogging about Radiant? Have you written an article helping people to get started or discussing some obscure feature of Radiant? Link it up in the comments and post it on Erik Mallinson’s wonderful Magnolia Group tracking articles about Radiant.
I’m happy to announce that the main Radiant site is now being hosted by the kind folks at AVLUX. If you are seeing this page it means that the DNS has now propagated correctly. Andrew vonderLuft has been instrumental in orchestrating the transition and deserves a medal for his patience with us during the process.
AVLUX specializes in hosting for Ruby on Rails applications. They offer both shared and dedicated plans in addition to Subversion hosting—all at reasonable prices. They can get you setup on their servers in under 24 hours with no setup fees.
If you are looking for a host for your next Radiant deployment or Ruby on Rails application, consider AVLUX!
Radiant 0.6.5 has been a long time coming! And just to be sure, we want to release a candidate or two to make sure we have everything solid. There are some really major changes in this release, and here’s the two big ones:
You can download the Radiant 0.6.5 RC1 here.
This release candidate is intended for developers and is NOT intended for production use. Please report any bugs you find to the development site.
To install use the gem command (with ‘sudo’ as necessary):
$ gem install radiant-0.6.5-RC1.gemThe gem will install as ‘radiant-0.6.5’.
1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.5”
2. Update the Radiant assets in your project:
rake radiant:update3. Copy your customizations back into config/environment.rb, if necessary (see below).
4. Migrate the database if you are running 0.6.2 or earlier:
rake production db:migrate5. Restart the server
1. Invoke the radiant command with your desired database driver:
$ radiant -d sqlite3 my_project2. Bootstrap the database:
$ cd my_project
$ rake db:bootstrap3. Startup the server and try it out!
$ script/serverconfig/environment.rbThis release has required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we have made significant changes to config/environment.rb and config/boot.rb. When updating your existing projects, config/environment.rb will be copied to config/environment.bak. You will need to manually copy any customizations, especially config.extensions and any other libraries, etc. that you require. DO NOT copy config.load_paths, config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. If you have further questions, please address them to the mailing list.
Ryan Heneise, of Art of Mission, has just launched a new service built on Radiant. It’s called Radiant Factory. Basically, Ryan is offering professional assistance to anyone who needs help getting up and running with Radiant.
Ryan can help you:
This is a dream come true for people looking to get started on Radiant who don’t have a lot of experience with Rails or Ruby. Ryan and I were chatting about this last week when he told me that he believes ease of deployment is one of the main things holding Radiant back right now. Rails applications are notoriously hard to deploy. Especially, when you compare them to something written in PHP. With Radiant Factory Ryan is hoping to lower the barrier of entry a little. Hopefully, this will make it easy for more people experience this great little CMS.
Update: Ryan has had to put Radiant Factory on hold as he is now busy with other business.
We are very happy to welcome Mislav Marohnić to the RadiantCMS core team. His contributions to cleaning up the Javascript in Radiant 0.6.4 have been invaluable. Mislav is also a member of the Prototype core team and a contributor to numerous other open-source projects. Congratulations, Mislav, and keep up the good work!
This release contains a few major changes as well as numerous bug-fixes and enhancements. Included in the release are Rails 1.2.5, Prototype 1.6 and script.aculo.us 1.8. Significant refactorings have been done to the admin UI Javascripts, thanks to Mislav Marohnic. The release also provides better support for MS SQL Server via Rails ticket/patch #8886 and stricter XHTML compatibility.
For a complete list of what’s new, see the CHANGELOG.
To upgrade:
1. Update the Radiant gem:
gem update radiant2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.4”
3. Update the Radiant assets in your project:
rake radiant:update4. Migrate the database if you are running 0.6.2 or earlier:
rake production db:migrate5. Restart the server
Please give the gem a chance to propagate to the RubyForge download servers.
