[ANN] Radiant 0.7.1 - Engraving Release (bugfix)

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


Radiant 0.7.1 Engraving is a bugfix release that corrects two errors
in the user-interface. The contents of page-parts will now maintain
escaped HTML characters across saves, and the tag reference will now
properly display when ‘’ is selected as the page type. The
spec-suite was expanded to cover these regressions. Many thanks to John
Muhl for identifying the escaping issue and a number of other community
members for diagnosing the tag reference issue.


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:



  • Properly escape page part contents in the UI. [John M., Sean C.]
  • Fix tag reference popup and spec out helper better. [Sean C.]


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

% gem install 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 project
for a website. So cd to the directory where you would like your
instance to be installed and type:

% radiant -d [mysql|postgres|sqlite3] .

Next, edit config/database.yml to taste. Then run the rake bootstrap

% rake production db:bootstrap

And start up the test server:

% script/server -e production

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/.


  1. Update the Radiant gem:

    % gem update radiant

  2. Change the RADIANT_GEM_VERSION constant in config/environment.rb
    to “0.7.1”.

  3. Restart the server

UPGRADING FROM 0.6.5 - 0.6.9

  1. Update the Radiant gem:

    % gem update radiant

  2. Change the RADIANT_GEM_VERSION constant in config/environment.rb
    to “0.7.1”.

  3. Run the update rake task:

    % rake radiant:update

  4. Run migrations:

    % rake db:migrate

  5. Restart the server

UPGRADING FROM 0.5.x - 0.6.4

The upgrade process changed significantly from last release, so listen
up! To upgrade an existing installation, BACKUP YOUR DATABASE, update
the gem, and create a new Radiant project using the instructions above.
Then point Radiant to the right database by editing config/database.yml
and execute the following command in your project directory:

% rake db:migrate

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


Radiant wouldn’t be possible without the help of some fine people. The
following people have made contributions to this release:

 John M.
 Sean C.

Thanks guys! If you’d like to hop on the development band wagon head on
over to our dev site (http://dev.radiantcms.org/).


The best place to get support is definitely 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:


The Radiant mailing list is also accessible via Ruby forum:



Sean C.
for the Radiant CMS Dev Team

I am upgrading a recently created 0.7.0 site. In step 2 I can not find

Am I missing something?


Sean C. wrote:

  1. Restart the server

Erik van Oosten

If you don’t have it, it will automatically use the latest version.
You’re fine!


Put it at the top of the file.



Sean C. wrote:

If you don’t have it, it will automatically use the latest version.
You’re fine!
Where do we add/ specify the RADIANT_GEM_VERSION? Start of the file,
end of the file?
I needed to do this for using an older version for a site that is built
on 0.6.9 and the system tries to use 0.7.0 right now. I’m setting it at
the command line before starting the server but was curious where
exactly it should go.

I’d like to also make a note of this on the wiki.

2/17/2009 | 12:33 AM.