# \[ANN\] Radiant CMS 0.6.5 "Chisel" Release **URL:** \ **Category:** Ruby\ **Created:** [April 19, 2008, 7:54pm UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-5-chisel-release/135248 "2008-04-19T19:54:25Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![smc7000](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/ed655f/32.png) [@smc7000](https://www.ruby-forum.com/u/smc7000)\ **Post date:** [April 19, 2008, 7:54pm UTC](https://www.ruby-forum.com/t/ann-radiant-cms-0-6-5-chisel-release/135248/1 "2008-04-19T19:54:25Z")
Looks like it’s time for another release of Radiant: [http://radiantcms.org/download/](http://radiantcms.org/download/) Radiant 0.6.5 “Chisel” represents a major leap forward for Radiant. Included in the release are Rails 2.0.2 and RSpec 1.1.4. All test/unit tests are now converted to RSpec specs. The extension-loading mechanism has also been rewritten to resolve numerous issues with loading-order. There are also tens of other small enhancements and bug-fixes from our community of contributors. Primary Radiant development is now done on GitHub. You can follow the progress at [http://github.com/seancribbs/radiant](http://github.com/seancribbs/radiant). We will maintain a Subversion mirror in the original location until feasible to move completely to Git. 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/](http://radiantcms.org/demo/) WHAT’S NEW IN THIS RELEASE? - Convert StandardTags specs to nested describe blocks. [Sean C.] - Remove test/unit tests - all RSpec now. [Sean C.] - Fix radiant:update:javascripts task. [Sean C.] - Fix problem in test fixtures. [Adam Keyes] - Add \ tag and appropriate fields to pages table. [Sean Cribbs] - Move admin-related javascripts to admin/. [Bjørn Arild Mæland] - Add if\_self and if\_ancestor\_or\_self tags. [Marty H., Sean C.] - Rename created\_by and updated\_by columns on standard models. [Sean Cribbs] - Fix Dir glob for extension rake tasks. [Sean C.] - Respect view\_paths set by plugins in extensions. [xtoddx] - Move extra initialization into after\_initialize block. [Sean C.] - Notice area now fades away after 3 seconds. [Andrew O’Brien] - \ now accepts paths relative to the current page. [Andrew O’Brien] - Update RSpec and RSpec on Rails to r3333. [Josh F.] - Add autotest support for Radiant and extensions. [Josh F.] - Add pkg/ ignore to git, correct CSS problems with fieldset tables. [Sean C.] - Ignore git files when building gem. [Sean C.] - Fix generated test and spec harnesses, convert core extensions to specs. [Sean C.] - Cover edge case in Page spec. [Sean C.] - Increase coverage of helper, controller, and model specs. [Sean Cribbs] - Correct some view and spec bugs. [Sean C.] - Added specs for view helpers. [Sean C.] - Use TH for fieldset tables and correct error in CSS. [skrat] - Adjust admin links and r:breadcrumbs tag to deal with Rails site prefix. [Sean C.] - Adjust tags to deal with Rails site prefix (relative\_url\_root). [Sean C.] - Resolve issue with undefined method :view\_paths in ActionMailer. [Sean C.] - Fixed incompatibility with RubyGems \>= 0.9.5 that broke radiant:freeze:gems rake task. [Michael Klett] - Fixed problem with the list of templates containing duplicates in the db:bootstrap rake task when not running in instance mode. [John L.] - Update Subversion URL so rake radiant:freeze:edge works. [John L.] - Add AVLUX to list of links in Styled Blog template. [John L.] - Fix Ruby 1.8.5 compatibility issue with Dir[]. [Sean C.] - Backup old environment.rb when copying new version. [Sean C.] - Fill out more controller specs. [Sean C.] - Fix Admin::PageController specs. [Sean C.] - Make autotest work. [Matthew Elder] - Clean up cache files before running site\_controller spec. [Matthew Elder] - Add r:status tag. [Andrew O’Brien] - Add ability to set publication date manually. [Nick Plante, Sean Cribbs] - Remove blank nodes in r:navigation tag. [ben] - Bubble up parsing exceptions in development mode. [jonleighton] - Fix authorization system for controller inheritance [Josh F.] - Add ‘nolinks’ attribute to breadcrumbs tag. [abstractioneer] - Fix fixtures for RSpec enabled extensions. [andreas] - Generate extensions with RSpec support by default, fix rake and script/spec in instance mode. [Andrew O’Brien] - Support database templates in a Radiant instance. [Benny D.] - Make rake test:extensions work in instance mode. [Daniel S.] - Fix tests failing in instance mode with config.extensions set. [Daniel S.] - Finished converting page\_controller\_test.rb to page\_controller\_spec.rb [John L.] - Completed converting user\_controller\_test.rb to user\_controller\_spec.rb [John L.] - Fix failing extension loading tests, remove irrelevant ones. [Sean Cribbs] - Fix test:extensions Rake task. [Sean C.] - Prevent following the link that toggles visibility of meta items on page edit. [Mislav Marohnić] - Fix extension loader and previously failing unit tests; update specs. [Mislav Marohnić] - Fixed problem with response\_cached? returning true when perform caching was off; fixed failing spec. [John L.] - Fixed issues with whitespace in page.rb. [John L.] - Fix filtering in tag reference popup. [Mislav Marohnić] - Updated rspec and rspec\_on\_rails. [John L.] - Add more controller specs and a matcher for LoginSystem features. [Sean C.] - Make all extensions loaded by default. [Sean C.] - Update extension loader spec. [Sean C.] - Work around a nasty issue with extensions + Dependencies unloading in development mode. [Mislav Marohnić] - Fix the tree expansion issue in admin interface (cookie-related). minor cleanup server-side [Mislav Marohnić] - Cleanup up the underscore layout hack by using method chain. [Mislav Marohnić] - Refactored initialization, extension loading, updated plugins. [Sean Cribbs] - Fix SiteController#show\_page for Rails 2.0. [Mislav Marohnić] - Minor optimization for Page; remove the unneccessary ‘virtual’ accessor. [Mislav Marohnić] - Fix tests for PostgreSQL: comment out a test that breaks most of the specs somehow. [Mislav Marohnić] - Failures in initializer\_spec.rb fixed [John L.] - Failure in site\_controller\_spec.rb fixed. [John L.] - The last test/unit failure is now fixed. [John L.] - Failing tests in page\_controller\_test.rb fixed. [John L.] - Error in response cache spec fixed. [Keeran Hawoldar] - ActionController::Base.view\_paths is now set correctly for extensions. [John L.] - Changed view extensions to “.html.erb” [John L.] - Fixed content type test failures. [John L.] - Fix page\_test. [John L.] - Updated environments. [John L.] - Modify ApplicationController spec. [Loren J.] - Modify SiteController spec. [Loren J.] - Fix failing unit test for old type of logger. [Daniel S.] - Fix problems preventing script/console from running: acts\_as\_tree is now a plugin, view\_paths is now a core feature. [Daniel S.] - Upgrade to Rails 2.0.2 [Daniel S.] - Escape angle brackets to avoid assertion warnings in StandardTags. [Sean C.] - Remove unused ConsoleUtils module and fix failing specs. [Sean C.] - Added standard\_tags\_spec.rb [John L.] - Make sure all scenario pages have at least a body part. [Sean C.] - Added render matcher. [John L.] - Modify pages scenario. [Loren J.] - A beginning on the Application and Site controller specs. [Loren Johnson] - Fix failing specs - use of before(:all) when before(:each) was needed [Daniel S.] - Fix failing extension\_load\_order\_test.rb [Daniel S.] - Don’t load scenarios stuff unless using specs. [Sean C.] - Add initializer spec. [Sean C.] - Add extension loader spec and refactorings. [Sean C.] - Added user\_spec.rb [John L.] - Upgrade Rails to 1.2.6. [Sean C.] - Added user\_action\_observer\_spec.rb [John L.] - Removed duplicate load paths from environments/test.rb [John L.] - Added text\_filter\_spec.rb [John L.] - Added status\_spec.rb [John L.] - Added spec/models/snippet\_spec.rb [John L.] - Added response\_cache\_spec.rb [John L.] - Small improvements to page\_part\_spec.rb [John L.] - Remove duplicate specs and move Radiant::ExtensionMigrator? spec to proper location. [Sean C.] - Fix admin.js to initialize TabControl even if there are no tabs. [Benny D.] - Correct RenderTestHelper to better resemble expectations from Rails. [Sean C.] - Add model specs and scenarios. [John L.] - Modify script/spec to work in instance mode. [Andrew O’Brien] - Add RSpec to load path in test environment. [Andrew O’Brien] - Add specs for Radiant::Extension and Radiant::Taggable. [Sean C.] - Fixed admin CSS for IE6 - ugly borders begone! [Bjørn Arild Mæland] - Fixed that homepage is no longer cached outside of cache dir, but to “\_site-root.data”. [Bjørn Arild Mæland] - Fix typo in pngfix.js. [Mislav Marohnić] - Turn off auto-loading RSpec stuff, even in test environment. [Mislav Marohnić] - Add specs for Annotatable, InheritableClassAttributes, LocalTime, MethodObserver, and Simpleton. [Sean C.] - Add spec for Radiant::AdminUI and Users scenario. [Sean C.] - Import and create boilerplate for RSpec and Scenarios. [Sean C.] - Honor config.extensions when running rake test:extensions and also include core extensions. [Daniel S.] - Propagate global page when using \ with inherit attribute. [Sean C.] 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 -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 page: [http://radiantcms.org/download/](http://radiantcms.org/download/). UPGRADING FROM 0.6.x 1. Update the Radiant gem: % gem update radiant 1. Change the RADIANT\_GEM\_VERSION constant in config/environment.rb to “0.6.5”. 2. Run the update rake task: rake radiant:update 1. Run migrations: rake db:migrate 1. 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. CONTRIBUTORS Radiant wouldn’t be possible without the help of some fine people. The following people have made contributions to this release: - Adam Keyes \* Marty H. \* xtoddx - skrat \* Michael Klett \* Matthew Elder - Nick Plante \* ben \* jonleighton - Josh F. \* abstractioneer \* andreas - Keeran Hawoldar \* Loren J. \* Benny D. - John L. \* Andrew O’Brien \* Bjørn Arild Mæland - Mislav Marohnić \* Daniel S. \* 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/](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! – Sean C. for the Radiant CMS Dev Team [http://radiantcms.org](http://radiantcms.org)