Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
> > But I think you missed the dot at the end of the command (referring to the > current directory) > % radiant -d [mysql|postgres|sqlite3] . > Ah! You are absolutely right, Jim! Thanks for pointing that out. -dan ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
On Jul 29, 2008, at 10:29 AM, Dan and Norine Simpson wrote: As for Dan and Norine Simpson's message about needing to specify the directory for a new instance, I don't recall ever not needing to do that. The rails command has the same requirement. But perhaps I'm misunderstanding something. I don't recall having to do that in the past. I only noted it because it was at odds with Sean's installation instructions. -dan Sorry Dan. I didn't realize that. But I think you missed the dot at the end of the command (referring to the current directory) % radiant -d [mysql|postgres|sqlite3] . ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
> > As for Dan and Norine Simpson's message about needing to specify the > directory for a new instance, I don't recall ever not needing to do that. > The rails command has the same requirement. But perhaps I'm misunderstanding > something. I don't recall having to do that in the past. I only noted it because it was at odds with Sean's installation instructions. -dan ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
There was a minor error in a feature added to 0.6.8 If you had a database with pages that referenced page types that no longer existed, you would have received errors about undefined constants. 0.6.8 tried to address this by only loading that class if the class was defined. This is a great way to allow you to easily remove extensions without repercussions, but there was an oversight in that that feature wasn't reloading in development mode. 0.6.9 Is in the works and should be out soon, but this is fixed on edge. As for Dan and Norine Simpson's message about needing to specify the directory for a new instance, I don't recall ever not needing to do that. The rails command has the same requirement. But perhaps I'm misunderstanding something. -Jim On Jul 29, 2008, at 9:45 AM, Anton J Aylward wrote: Dan and Norine Simpson said the following on 28/07/08 11:46 AM: A brand new installation seems to require specifying the name of the directory for your installation. So, for example: Most of us here are already using radiant and every upgrade makes me nervous. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
Dan and Norine Simpson said the following on 28/07/08 11:46 AM: A brand new installation seems to require specifying the name of the directory for your installation. So, for example: Most of us here are already using radiant and every upgrade makes me nervous. -- It is the test of a good religion whether you can joke about it. - G. K. Chesterton ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
A brand new installation seems to require specifying the name of the directory for your installation. So, for example: -bash-3.00$ radiant Usage: /home/danorine/ruby/bin/radiant /path/to/radiant/app [options] Options: -r, --ruby=path Path to the Ruby binary of your choice (otherwise scripts use env, dispatchers current path). Default: /home/danorine/ruby/bin/ruby -d, --database=name Preconfigure for selected database (options: mysql, postgresql, sqlite3, sqlserver). Default: mysql Radiant Info: -v, --versionShow the Radiant version number and quit. -h, --help Show this help message and quit. General Options: -p, --pretendRun but do not make any changes. -f, --force Overwrite files that already exist. -s, --skip Skip files that already exist. -q, --quiet Suppress normal output. -t, --backtrace Debugging: show backtrace on errors. -c, --svnModify files with subversion. (Note: svn must be in path) and, yet: -bash-3.00$ radiant radiant create create CHANGELOG create CONTRIBUTORS create INSTALL create LICENSE create README create config create config/environments create config/environments/development.rb create config/environments/production.rb create config/environments/test.rb create db create log create public create public/.htaccess create public/404.html create public/500.html create public/dispatch.cgi create public/dispatch.fcgi create public/dispatch.rb create public/favicon.ico create public/images create public/images/admin create public/images/admin/add-child.png create public/images/admin/brown-bottom-line.gif create public/images/admin/clear-page-cache.png create public/images/admin/collapse.png create public/images/admin/expand.png create public/images/admin/layout.png create public/images/admin/minus.png create public/images/admin/new-homepage.png create public/images/admin/new-layout.png create public/images/admin/new-snippet.png create public/images/admin/new-user.png create public/images/admin/page.png create public/images/admin/plus.png create public/images/admin/remove-disabled.png create public/images/admin/remove.png create public/images/admin/snippet.png create public/images/admin/spinner.gif create public/images/admin/view-site.gif create public/images/admin/virtual-page.png create public/javascripts create public/javascripts/admin create public/javascripts/admin/admin.js create public/javascripts/admin/ruledtable.js create public/javascripts/admin/sitemap.js create public/javascripts/admin/tabcontrol.js create public/javascripts/application.js create public/javascripts/controls.js create public/javascripts/dragdrop.js create public/javascripts/effects.js create public/javascripts/pngfix.js create public/javascripts/prototype.js create public/javascripts/string.js create public/robots.txt create public/stylesheets create public/stylesheets/admin create public/stylesheets/admin/main.css create script create script/about create script/breakpointer create script/console create script/extension create script/performance create script/performance/benchmarker create script/performance/profiler create script/process create script/process/inspector create script/process/reaper create script/process/spawner create script/process/spinner create script/runner create script/server create script/spec create script/spec_server create script/version create vendor/extensions create vendor/plugins create script/generate create config/database.yml create Rakefile create config/routes.rb create config/environment.rb create config/boot.rb readme ../../../../INSTALL == Installation and Setup Once you have extracted the files into the directory where you would like to install Radiant: 1. Create the MySQL/PostgreSQL/SQLite databases for your Web site. You only need to create the "production" database, but you may also want to create the "development" and "test" databases if you are developing extensions or running tests. 2. Edit config/database.yml to taste. 3. Run the database bootstrap rake task: % rake production db:bootstrap (If you would like bootstrap your development database ru
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
There's a minor error in the radiant:update:configs task that I discovered this morning when fixing the demo site -- this should only affect upgrades from older versions. I have pushed the fix to github. If you want to stay on the gem, the workaround is to do two things: 1) Make sure you have a unique secret in your config.action_controller.session setting. 2) Add the line "Page.load_subclasses" to the end of the file (outside the config block). Sean Mohit Sindhwani wrote: Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.6.8 "Incise" adds a number of new features that enhance support for extensions and completes the project's move to github. Of special note are: * Extension installer/uninstaller scripts (script/extension) and a global 'extension registry' at http://ext.radiantcms.org * Support for freezing edge Radiant using 'git' * Remember-me functionality for the admin UI Thanks! I don't think that this changes the documentation much, so it's still good! Cheers, Mohit. 7/28/2008 | 2:36 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] [ANN] Radiant CMS 0.6.8 "Incise" Release
Sean Cribbs wrote: Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.6.8 "Incise" adds a number of new features that enhance support for extensions and completes the project's move to github. Of special note are: * Extension installer/uninstaller scripts (script/extension) and a global 'extension registry' at http://ext.radiantcms.org * Support for freezing edge Radiant using 'git' * Remember-me functionality for the admin UI Thanks! I don't think that this changes the documentation much, so it's still good! Cheers, Mohit. 7/28/2008 | 2:36 PM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
