[ANN] Radiant CMS 0.5.2 - Raildust

Looks like it’s time for another release of Radiant:


This is primarily a security update. A critical security vulnerability
has been discovered in Rails 1.1.4 and previous versions. Rails 1.1.6
seems to fix the problem. This version of Radiant is identical to 0.5.1
apart from the Rails upgrade. It is highly recommended that you upgrade.


Radiant is a no-fluff content management system designed for small
teams. It’s similar to Movable Type or Textpattern, but is more than a
blogging engine. It’s a Web developer’s CMS with just enough features to
make it worthwhile. We’ve intentionally left the kitchen sink out!

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)
  • Special page-oriented plugins called behaviors
  • 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:



Radiant 0.5.2

  • Upgraded Rails to 1.1.6

Radiant 0.5.1

  • Upgraded Rails to 1.1.5
  • Added basic support for upgrades to the radiant command
  • Gem now includes the .htaccess file (this should make Apache users
  • Updated icon for layouts
  • Migrations are now repaired so that you can run rake migrate to
    create the initial database. (The recommended method is still
    script/setup_database, but enough people had complained about this
    that I felt it was in the general interested to fix it.)
  • When you collapse a branch in the admin page tree view and move to
    another tab the collapsed status is now saved so that when you
    the collapsed status is preserved. Also the status of collapsed
    branches is preserved when collapsing and expanding parent nodes.
  • Fixed documentation problem in response_cache.rb
  • Fixed problem with timezones on fixtures causing tests to fail in
  • Fixed a problem with an error being thrown when the <r:context /> tag
    was rendered with the inherit attribute set to true and the page part
    did not exist


We’ve worked hard to make it easy to install Radiant. For starters you
can download it with Ruby Gems:

% gem install --include-dependencies radiant

Once the Radiant gem is installed you have access to the radiant
command. The radiant command is similar to the rails command (if you
are from the Rails world. It’s how you generate a new Radiant instance
application. An instance application is an application that references
the source code which is located somewhere else (in this case the
Radiant gem.) So cd to the directory where you would like your
instance to be installed and type:

% radiant .

Next, create a database for your application and setup the appropriate
config/database.yml file. You’ll find several examples in the config
directory. Radiant supports MySQL, SQLite, and PostgreSQL.

Then run the script/setup_database command:

% script/setup_database production

And start up the test server:

% script/server

Finally, hit the /admin/ URL and you should be off to the races. See the
README file in the release for additional details.

If you are interested in other download options, visit the download
page: http://radiantcms.org/download/.


To upgrade an existing installation, update the gem and execute the
following command in the directory where you have Radiant installed:

% radiant --upgrade .

If you have problems during the upgrade, please let us know on the
mailing list.


Perhaps the best place to get support is on the Radiant mailing list.
There’s a crowd of people there who have been hanging around for many
moons now. Newbie questions are welcome! To sign up, go to:



John L.