# \[ANN\] Radiant 0.6.3 - Rock Grinder Release **URL:** \ **Category:** Radiant CMS\ **Created:** [October 6, 2007, 11:19pm UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530 "2007-10-06T23:19:25Z")\ **Posts on this page:** 10\ **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:** [October 6, 2007, 11:19pm UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/1 "2007-10-06T23:19:25Z")
Looks like it’s time for another release of Radiant: ``` http://radiantcms.org/download/ ``` This release contains many progressive changes and bugfixes, especially with respect to the extension system. Of special note are: - conversion to using ActiveRecord-based sessions and storing the id of the logged-in user in the session instead of the complete user object - addition of the ability to specify the loading-order (and inclusion/exclusion) of extensions in environment.rb - automatic loading of Rails plugins included in extensions upon activation. 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? - Add generic public/ copy task to generated extensions. [Sean C.] - Fix typo in StandardTags. [oli] - Added db:remigrate:extensions task. [Sean C.] - Show all child pages on remove confirmation, regardless of sitemap expansion. [Sean C.] - Make LoginSystem store user ids in session rather than whole user objects. [Sean C.] - Plugins included in an extension’s vendor/plugins directory will automatically be loaded before the extension is activated. Plugins included in more than one extension will be loaded only once according to the extension load order. [Sean Cribbs] - Allow subclassing of FileNotFoundPage. [Daniel S.] - \ should not return FileNotFoundPage. [Daniel S.] - Change test for tabs to just check dupes and for the requested tab rather than a specific list (test was breaking if a real extension added a tab). [Daniel S.] - Ensure test extensions are loaded in the test environment. [Daniel Sheppard] - Prevent ExtensionInitializationTest from unloading real extensions. [Daniel S.] - Expire the old URL from the cache when the page slug changes. [Daniel Sheppard] - Fix failing tests in instance mode. [Daniel S.] - Move difference assertions upstream from forms extension into a test helper. [Sean C.] - Update Prototype to 1.5.0 final release. [Sean C.] - Allow specification of extension loading order in environment.rb [Daniel S.] - Fix bugs in assert\_global\_tag\_defined and assert\_tag\_defined of ExtensionTagTestHelper. [Sean C.] - Make sure included stylesheets and javascripts are only linked to once in. [Sean C.] - Fix navigation tag tests. [vitali] - Suppress errors about missing default helper by providing a blank helper. [Sean C.] - Fix mis-alignment of “Clear cache” button when homepage not present. [Sean C.] - Fix issues with misnesting of modules in fixture loading extension and test suites running randomly from dispatchers. [Sean C.] - Remove invalid image alignment. [tolbrino] - Display not\_found.rhtml on standard ‘not found’-like exceptions. [Sean Cribbs] - Make sitemap.js use relative URLs. [Earl C.] - Preliminary support for active\_record sessions. [John L.] 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: 2. Change the RADIANT\_GEM\_VERSION constant in config/environment.rb to “0.6.3”. 3. Run the update rake task: 4. Run the Radiant migrations: 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. CONTRIBUTORS Radiant wouldn’t be possible without the help of some fine people. The following people have made contributions to this release: - oli \* Daniel S. \* vitali - tolbrino \* Sean C. \* Earl C. - John L. 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) ---
**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:** [October 7, 2007, 4:26pm UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/2 "2007-10-07T16:26:20Z")
Congrats! Do you have any details on how to make use the" “\* Add generic public/ copy task to generated extensions.” Feature?? Do we have to do something besides put files in the extensions/foo/public directory??? Regards, Hiram On 10/6/07, Sean C. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote: > inclusion/exclusion) of extensions in environment.rb > > - Built using Ruby on Rails (which means that extending Radiant is > - Add generic public/ copy task to generated extensions. [Sean C.] > will be loaded only once according to the extension load order. [Sean > - Expire the old URL from the cache when the page slug changes. [Daniel. [Sean C.] > - Make sitemap.js use relative URLs. [Earl C.] > Once the Radiant gem is installed you have access to the `radiant` > > over to our dev site ([http://dev.radiantcms.org/](http://dev.radiantcms.org/)). > The Radiant mailing list is also accessible via Ruby forum: > > * * * > > Radiant mailing list > Post: removed\_email\_address@domain.invalid > Search: [http://radiantcms.org/mailing-list/search/](http://radiantcms.org/mailing-list/search/) > Site: [http://lists.radiantcms.org/mailman/listinfo/radiant](http://lists.radiantcms.org/mailman/listinfo/radiant) – Regards, Hiram Blog: [http://hiramchirino.com](http://hiramchirino.com) ---
**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:** [October 7, 2007, 5:52pm UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/3 "2007-10-07T17:52:37Z")
Hiram, You don’t have to do anything special except put files in the public/ directory of your extension. The task will ignore all SVN-related files and copy everything else, including creating the directory structure. Either generate an extension or have a look at lib/generators/extension/templates/tasks.rake. Sean ---
**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:** [October 10, 2007, 3:52am UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/4 "2007-10-10T03:52:17Z")
Will, Try this inside your Radiant project: rake radiant:unfreeze Sean ---
**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:** [October 10, 2007, 3:39am UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/5 "2007-10-10T03:39:57Z")
I just noticed this, but the admin login screen still claims to be radiant 0.6.1. I do not have 0.6.1 installed anywhere on my system, and my RADIANT\_GEM\_VERSION = ‘0.6.3’ == Will G. ---
**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:** [October 10, 2007, 3:52am UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/6 "2007-10-10T03:52:17Z")
Yeah, might help if I rake radiant:unfreeze == Will G. ---
**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:** [October 10, 2007, 5:20am UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/7 "2007-10-10T05:20:54Z")
I just ran the update and things seem to be okay…when i go to the admin page of my install it says ‘powered by Radiant CMS version 0.6.3 (gem)’ (this does indicate success, right?). I even updated a page and it works. but i’m not sure what to do when i go back to my ssh session at this point? it shows: * * * –help[2007-10-09 20:51:47] INFO going to shutdown … [2007-10-09 20:51:47] INFO WEBrick::HTTPServer#start done. removed\_email\_address@domain.invalid [/path/to/radiant]# script/server -e production =\> Booting WEBrick… =\> Rails application started on [http://0.0.0.0:3000](http://0.0.0.0:3000) =\> Ctrl-C to shutdown server; call with --help for options [2007-10-09 20:52:00] INFO WEBrick 1.3.1 [2007-10-09 20:52:00] INFO ruby 1.8.6 (2007-03-13) [x86\_64-linux] [2007-10-09 20:52:00] INFO WEBrick::HTTPServer#start: pid=11639 port=3000 * * * and then a cursor and that’s it. any pointers (or just general info)? thanks ---
**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:** [October 10, 2007, 6:27am UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/8 "2007-10-10T06:27:56Z")
Sean C. wrote: > Ideally you shouldn’t use WEBrick in a production setting. I would > investigate Mongrel or FCGI, both of which can be ‘daemonized’. > > Sean Sean, thanks for your rapid response. i did read that on the radiant page after the fact (unfortunately i have to get this up and running a week ago so i’m having to do a lot of things in a hurry–not good i know, but it’s for a class and i don’t have any say in the timeline). but my question was because there was no return to the prompt(?). i’m not sure if that is even the right term…but what i mean is that usually in the terminal after you execute a command ‘username@domain…#’ displays followed by the cursor. that didn’t happen but things seem to have worked–so do i need to type in another command or am i all set (and hence clear to go investigate mongrel/fcgi and also how to daemonize while i’m at it)? thanks, damonica ---
**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:** [October 10, 2007, 3:46pm UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/9 "2007-10-10T15:46:43Z")
Damonica Miller wrote: > week ago so i’m having to do a lot of things in a hurry–not good i > > damonica If you can keep the shell running, you don’t need to do anything else. At the point you described, WEBrick was waiting for its first request. Sean ---
**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:** [October 10, 2007, 5:58am UTC](https://www.ruby-forum.com/t/ann-radiant-0-6-3-rock-grinder-release/116530/10 "2007-10-10T05:58:51Z")
Ideally you shouldn’t use WEBrick in a production setting. I would investigate Mongrel or FCGI, both of which can be ‘daemonized’. Sean