Looks like it's time for another release of Radiant:
Radiant 0.6.7 "Mordant" resolves several security holes and includes
enhancements for developers. CSRF attacks are now partly mitigated by the
built-in Rails helpers and every user account now has its own password salt
that remains secret. All admin view templates have been converted to use Haml
instead of the standard ERb templates. Additionally, the "shards" extension
has been folded into the core, allowing flexible manipulation of the
administration UI for extensions.
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.
* 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:
WHAT'S NEW IN THIS RELEASE?
* Integrate shards extension into core. [Sean Cribbs]
* Convert all views to Haml. [Sean Cribbs, John Long]
* Avoid authenticity check when listing page children. [Sean Cribbs]
* Add radiant:extensions:update_all task. [Josh French]
* Tweak LoginSystem to allow attempted URL redirection after login and
auto-redirect from login URL if logged in. [Josh French]
* Add per-user salting to password encryption. [Sean Cribbs]
* Address CSRF vulnerabilities in forms. [Sean Cribbs]
* Remove clear cache action, always clear cache after saving a page. [Sean
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 task:
% 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
UPGRADING FROM 0.6.x
1. Update the Radiant gem:
% gem update radiant
2. Change the RADIANT_GEM_VERSION constant in config/environment.rb
3. Run the update rake task:
% rake radiant:update
4. Run migrations:
% rake db:migrate
5. Restart the server
UPGRADING FROM 0.5.x
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 Long * Josh French * Sean Cribbs
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: