Radiant 0.6.5 - Chisel Release
It’s finally here! Radiant 0.6.5 “Chisel”, after over 4 months of grueling anticipation, is released. This represents a major leap forward for Radiant. The major changes are:
- Rails 2.0.2 included (0.6.4 used Rails 1.2.5)
- RSpec 1.1.4 is used in core and supported in extensions
In addition to those major changes, these enhancements may be of interest:
- It is now possible to edit the published date of a page from the editing interface.
- Pages now have “description” and “keywords” fields that can be output as
<meta>tags using the
r:metafamily of tags.
- Green notice areas will fade from the interface after 3 seconds.
r:findtag now accepts relative paths.
- URLs in the admin interface and in standard Radius tags should now respect when Radiant is installed in a “subdirectory” rather than the root URL namespace.
- RSpec and scenarios are supported in extensions.
updated_byfields on all models have been renamed to
- Radiant has its own Autotest class that runs extension specs as well as the core specs.
To install use the gem command (with ‘sudo’ as necessary):
$ gem install radiant
The gem will install as ‘radiant-0.6.5’.
Upgrading an existing project/site
1. Change the RADIANT_GEM_VERSION constant in config/environment.rb to “0.6.5” or remove it altogether.
2. Update the Radiant assets in your project:
3. Copy your customizations back into
config/environment.rb, if necessary (see below).
4. Migrate the database:
rake production db:migrate
5. Restart the server
Creating a new project/site
1. Invoke the
radiant command with your desired database driver:
$ radiant -d sqlite3 my_project
2. Bootstrap the database:
$ cd my_project $ rake db:bootstrap
3. Startup the server and try it out!
Internal Changes to
This release has required a lot of changes to the internal API of Radiant. End-users should be unaffected, but as a result of these requirements, we have made significant changes to
config/boot.rb. When updating your existing projects,
config/environment.rb will be copied to
config/environment.bak. You will need to manually copy any customizations, especially
config.extensions and any other libraries, etc. that you require. DO NOT copy
config.plugin_paths, or any of those items to the new file; those settings have been internalized in this release. If you have further questions, please address them to the mailing list.