# \[ANN\] Radiant CMS 0.6 - Lapidary **URL:** \ **Category:** Rails\ **Created:** [April 25, 2007, 1:05am UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759 "2007-04-25T01:05:16Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 25, 2007, 1:05am UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/1 "2007-04-25T01:05:16Z")
Looks like it’s time for another release of Radiant: ``` http://radiantcms.org/download/ ``` This is the first serious release of Radiant in well over 6 months. The big news in this release is that we have created a first-class extension system to make it easier for you to tailor Radiant to meet your needs. Developers can now add their own models, views, and controllers and completely customize the administrative interface. 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](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? - Added support for extensions–an extremely flexible way to extend Radiant - Merged Behaviors into the Page class; subclass page now instead - Improved database support for Postgres and Sqlite - Limited support for SQL Server - Exceptions from tags now bubble up during testing - Page parts are now sorted by ID so the order that you create them in is preserved [Josh F.] - Implemented tag documentation DSL and UI [Sean C.] - Reworked the setup code - Renamed script/setup\_database to rake db:bootstrap - Reworked the upgrade code to work around rake tasks - Added rake tasks for freezing and unfreezing radiant to the edge - r:children:each, r:children:first, and r:children:last now all accept the same ordering and limit attributes and have the same defaults - Snippets are now responsive to global context via the r:page tag. This means that any tags inside r:page will refer to the page currently being rendered, i.e. the page requested, not the local contextual page via tags like r:children:each, etc. This is most relevant to recursive snippets like the sitemapper example [Sean C.] - r:navigation now uses the pipe character (“|”) to delimit URLs in the urls attribute rather than the semi-colon - :date now accepts a “for” attribute that specifies which attribute of the page to render. Valid values of the attribute are published\_at, updated\_at, created\_at, and now. - Created the r:cycle tag to make alternating tables and lists possible - Added popups for filter and tag documentation inside the page editing interface - Added support for optimistic locking for all models [Daniel Shepherd] - Added support to Radiant::Config for boolean values [Sean C.] - Caching no longer stores the headers and body in the same file [Daniel Shepherd] - Added support for the X-Sendfile header that works in conjunction with caching to speed it up (by default X-Sendfile support is off) [Daniel Shepherd] - Moved the images and stylesheets into images/admin and stylesheets/admin respectively to make it easier for Radiant’s assets to coexist easily with the site’s assets - Improved the Javascript that automatically updates the slug and breadcrumb based off of the title so that it now response to all change events - For the full scoop on what’s changed see Sean C.’ detailed post: [What's New in Radiant 0.6 - Sean Cribbs](http://seancribbs.com/tech/2007/04/18/whats-new-in-radiant-0-6) INSTALLATION 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 project for a website. 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. 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 page: [http://radiantcms.org/download/](http://radiantcms.org/download/). 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. CONTRIBUTORS Radiant wouldn’t be possible without the help of some fine people. The following people have made contributions to this release: - Alexander H. \* Adam W. \* Sean S. - Sean C. \* Brian G. \* Bodhi Philpot - Andrew B. \* Jesse Newland \* Josh F. - Daniel S. \* Matte E. \* Jacob B. - Chris P. Thanks guys! If you’d like to hop on the development band wagon head on over to our dev site ([http://dev.radiantcms.org/](http://dev.radiantcms.org/)). SUPPORT 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: [http://radiantcms.org/mailing-list/](http://radiantcms.org/mailing-list/) The Radiant mailing list is also accessible via Ruby forum: [http://www.ruby-forum.com/forum/21](http://www.ruby-forum.com/forum/21) Enjoy! ---
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 25, 2007, 10:14pm UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/2 "2007-04-25T22:14:24Z")
On 4/25/07, Wybo W. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > At the bottom of your page I found a link: Site powered by Mephisto… > > Why make a CMS, and not use it yourself for what it seems to be made > for ? Or is it a legacy, and on your todo-list to migrate to radiant ? > > Wybo Because Mephisto rules… as a blog engine 🙂 [http://wiseheartdesign.com/2006/12/1/now-on-mephisto/](http://wiseheartdesign.com/2006/12/1/now-on-mephisto/) – Rick O. [http://lighthouseapp.com](http://lighthouseapp.com) [http://weblog.techno-weenie.net](http://weblog.techno-weenie.net) [http://mephistoblog.com](http://mephistoblog.com) ---
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 25, 2007, 9:09pm UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/3 "2007-04-25T21:09:15Z")
One small question… Lately I was looking into rails CMSses for setting up a small company- website, and I checked out mephisto, typo, comatose, and radiant, which I liked most… So I was at the verge of choosing Radiant, when I followed the link at the bottom of the radiant-site, to your company, Wiseheart Design. At the bottom of your page I found a link: Site powered by Mephisto… Why make a CMS, and not use it yourself for what it seems to be made for ? Or is it a legacy, and on your todo-list to migrate to radiant ? Wybo – :🧑‍🎓 - History, Informatiekunde (computer linguistics, IR, webtech) and Philosophy - Member of the Center for Metahistory Groningen ([Faculty of Arts | About us | University of Groningen](http://www.rug.nl/let/cmg)) ::Free Software and Open Source Developer: - [http://www.LogiLogi.org](http://www.LogiLogi.org), Cumulative, shared commenting, publication and idea sharing: Where insight comes together… - ComLinToo, a computational linguistics toolset written in Perl - Lake ([LogiLogi.org](http://LogiLogi.org) Make), a make-replacement using makefiles in pure C++ ::Being: - In the world, wavy hair, go figure ([http://nl.logilogi.org/HomE/WyboWiersma](http://nl.logilogi.org/HomE/WyboWiersma)) ---
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 26, 2007, 5:20am UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/4 "2007-04-26T05:20:54Z")
Wybo W. wrote: > Why make a CMS, and not use it yourself for what it seems to be made > for ? Or is it a legacy, and on your todo-list to migrate to radiant ? There were at least two reasons: 1. I had heard a lot about Mephisto and wanted to see what all the fuss was about. I previously used Typo. 2. Because I needed a blogging engine that supports comments. Radiant didn’t at the time I needed something to power my blog. There are now at least two extensions for comments under development. As soon as I have some spare time on my hands I will probably switch my blog over and use one of them. But don’t let me stop you from exploring both options. Mephisto is a fine blogging engine that can double as a CMS (sort of). Radiant is a CMS that can be used as a blogging engine, but is much more flexible. – John L. [http://wiseheartdesign.com](http://wiseheartdesign.com) ---
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 25, 2007, 10:29pm UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/5 "2007-04-25T22:29:28Z")
The site Radiant was created to support: [http://www.ruby-lang.org/](http://www.ruby-lang.org/) On 4/25/07, Rick O. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > > the bottom of the radiant-site, to your company, Wiseheart Design. > > [http://wiseheartdesign.com/2006/12/1/now-on-mephisto/](http://wiseheartdesign.com/2006/12/1/now-on-mephisto/) > > – > Rick O. > [http://lighthouseapp.com](http://lighthouseapp.com) > [http://weblog.techno-weenie.net](http://weblog.techno-weenie.net) > [http://mephistoblog.com](http://mephistoblog.com) > > > – Proud supporter of DC United ---
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 26, 2007, 7:50am UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/6 "2007-04-26T07:50:05Z")
It looks like Radiant is doing some form of action caching. You know there’s a Rails plugin that can do what you’ve implemented, and more. Check it out here: [http://agilewebdevelopment.com/plugins/action\_cache](http://agilewebdevelopment.com/plugins/action_cache) If you need help with integrating this, I’m almost always available to help Nice work. Next time I need a CMS, I’ll check out Radiant again. ---
**Author:** ![John\_WSLong](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/34f0e0/32.png) [@John\_WSLong](https://www.ruby-forum.com/u/John_WSLong)\ **Post date:** [April 28, 2007, 3:29pm UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-lapidary/102759/7 "2007-04-28T15:29:20Z")
> 1. I had heard a lot about Mephisto and wanted to see what all the fuss > was about. I previously used Typo. > > 2. Because I needed a blogging engine that supports comments. Radiant > didn’t at the time I needed something to power my blog. > > There are now at least two extensions for comments under development. As > soon as I have some spare time on my hands I will probably switch my > blog over and use one of them. Great! > But don’t let me stop you from exploring both options. Mephisto is a > fine blogging engine that can double as a CMS (sort of). Radiant is a > CMS that can be used as a blogging engine, but is much more flexible. Thanks for your answer. I’m currently checking both out and I’m going for Radiant. greetings, Wybo > – > John L. > [http://wiseheartdesign.com](http://wiseheartdesign.com) – :🧑‍🎓 - History, Informatiekunde (computer linguistics, IR, webtech) and Philosophy - Member of the Center for Metahistory Groningen ([Faculty of Arts | About us | University of Groningen](http://www.rug.nl/let/cmg)) ::Free Software and Open Source Developer: - [http://www.LogiLogi.org](http://www.LogiLogi.org), Cumulative, shared commenting, publication and idea sharing: Where insight comes together… - ComLinToo, a computational linguistics toolset written in Perl - Lake ([LogiLogi.org](http://LogiLogi.org) Make), a make-replacement using makefiles in pure C++ ::Being: - In the world, wavy hair, go figure ([http://nl.logilogi.org/HomE/WyboWiersma](http://nl.logilogi.org/HomE/WyboWiersma))