Re: [Radiant] Ruby Gems Installation Issue
Rufo Sanchez wrote: On Sat, Apr 19, 2008 at 8:28 PM, Tom Cloyd [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: locate spewed out the files in /var/lib/gems/1.8/doc/radiant-0.6.4/, of course. It also listed /var/lib/gems/1.8/bin/radiant, so, I executed the radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS command I'd tried earlier, from within that dir, and once again got: bash: radiant: command not found Tom, Apologies if you know/tried this already, but sometimes it's the simple things... What happens if you run the radiant command using the absolute path, e.g. /var/lib/gems/1.8/bin/radiant ...instead of switching to the /var/lib/gems/1.8/bin directory? Most UNIX installs don't put the current directory in PATH for security reasons, so while that may have been the radiant command you tried to launch, the shell may not have found it. If that works, you can add the /var/lib/gems/1.8/bin directory to your PATH, and from that point on you should be good to go. Hope this helps, and good luck with your Radiant adventures, Rufo Well [expletive deleted - several of them, in fact...]! That appears to have done it. I got a lot of output from that command, and it sure looks like the right sort of things happened. I realize that being rather new to Linux there is much I don't know, but this latest piece of secret knowledge flabbergasts me. Why can't radiant use the same path all the other gems seems to successfully use? How could I ever have figured out this problem without your expert help? I couldn't, it's a good bet. Now, my next big problem: it appears that I'm supposed to be Rails-cognizant, which I surely am not. I wish that had been made clear at the website. I'd still have come to this point, but would have studied up a bit beforehand. So...that's next. You only need to create the production database... Yeah, sure. I have no idea what that means. Yet. Onward. Thanks again. Much appreciated! T. -- ~ Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 [EMAIL PROTECTED] (email) TomCloyd.com (website psychotherapy weblog) sleightmind.wordpress.com (mental health issues weblog) directpathdesign.com (web site design consultation) ~ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Ruby Gems Installation Issue
Tom Cloyd wrote: [snip] I realize that being rather new to Linux there is much I don't know, but this latest piece of secret knowledge flabbergasts me. Why can't radiant use the same path all the other gems seems to successfully use? How could I ever have figured out this problem without your expert help? Update: I figured out that my earlier attempt to update my path were bases on bad information, so that the path wasn't actually being modified at all. THAT makes sense - accounts for the behavior I was seeing. I have now fixed the path, and verified the fix. Live and learn. (Not necessarily in equal parts!). t. -- ~ Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 [EMAIL PROTECTED] (email) TomCloyd.com (website psychotherapy weblog) sleightmind.wordpress.com (mental health issues weblog) directpathdesign.com (web site design consultation) ~ ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: Radiant Digest, Vol 25, Issue 32
Every extension that used shards has been rendered completely useless. None of the Admin UI additions provided by extensions show up anymore. Is there a way to fix this, has shards been integrated into core? I need help! Arik, This is a bug that snuck in to 0.6.5. Sean should be pushing a fixed release soon; in the meantime, you can apply this patch: http://github.com/jfrench/radiant/commit/ 52897147ae427b6dea4c8281e9e9bdf9e2c6fa9a j On Apr 20, 2008, at 12:55 PM, [EMAIL PROTECTED] wrote: Send Radiant mailing list submissions to radiant@radiantcms.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.radiantcms.org/mailman/listinfo/radiant or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Radiant digest... Today's Topics: 1. Re: Ruby Gems Installation Issue (Tom Cloyd) 2. Re: Ruby Gems Installation Issue (Rufo Sanchez) 3. Shards and Radiant 0.6.5 Chisel (Arik Jones) 4. Re: Ruby Gems Installation Issue (Tom Cloyd) 5. Re: Ruby Gems Installation Issue (Tom Cloyd) -- Message: 1 Date: Sat, 19 Apr 2008 18:40:22 -0700 From: Tom Cloyd [EMAIL PROTECTED] Subject: Re: [Radiant] Ruby Gems Installation Issue To: Radiant CMS List radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=windows-1252; format=flowed I just updated to ver. 0.6.5. My essential problem remains: $ radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS bash: radiant: command not found Awaiting enlightenment. t. -- ~ Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 [EMAIL PROTECTED] (email) TomCloyd.com (website psychotherapy weblog) sleightmind.wordpress.com (mental health issues weblog) directpathdesign.com (web site design consultation) ~ -- Message: 2 Date: Sat, 19 Apr 2008 23:52:05 -0400 From: Rufo Sanchez [EMAIL PROTECTED] Subject: Re: [Radiant] Ruby Gems Installation Issue To: [EMAIL PROTECTED], radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1 On Sat, Apr 19, 2008 at 8:28 PM, Tom Cloyd [EMAIL PROTECTED] wrote: locate spewed out the files in /var/lib/gems/1.8/doc/radiant-0.6.4/, of course. It also listed /var/lib/gems/1.8/bin/radiant, so, I executed the radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS command I'd tried earlier, from within that dir, and once again got: bash: radiant: command not found Tom, Apologies if you know/tried this already, but sometimes it's the simple things... What happens if you run the radiant command using the absolute path, e.g. /var/lib/gems/1.8/bin/radiant ...instead of switching to the /var/lib/gems/1.8/bin directory? Most UNIX installs don't put the current directory in PATH for security reasons, so while that may have been the radiant command you tried to launch, the shell may not have found it. If that works, you can add the /var/lib/gems/1.8/bin directory to your PATH, and from that point on you should be good to go. Hope this helps, and good luck with your Radiant adventures, Rufo -- Message: 3 Date: Sun, 20 Apr 2008 06:11:17 +0200 From: Arik Jones [EMAIL PROTECTED] Subject: [Radiant] Shards and Radiant 0.6.5 Chisel To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=utf-8 Every extension that used shards has been rendered completely useless. None of the Admin UI additions provided by extensions show up anymore. Is there a way to fix this, has shards been integrated into core? I need help! -- Posted via http://www.ruby-forum.com/. -- Message: 4 Date: Sun, 20 Apr 2008 07:59:38 -0700 From: Tom Cloyd [EMAIL PROTECTED] Subject: Re: [Radiant] Ruby Gems Installation Issue Cc: radiant@radiantcms.org Message-ID: [EMAIL PROTECTED] Content-Type: text/plain; charset=ISO-8859-1; format=flowed Rufo Sanchez wrote: On Sat, Apr 19, 2008 at 8:28 PM, Tom Cloyd [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: locate spewed out the files in /var/lib/gems/1.8/doc/radiant-0.6.4/, of course. It also listed /var/lib/gems/1.8/bin/radiant, so, I executed the radiant --database sqlite3 /home/tom/Ruby projects - Toms/radiant-test-CMS command I'd tried earlier, from within that dir, and once again got: bash: radiant: command not found Tom, Apologies if you know/tried this already, but sometimes it's the simple things... What happens if you run the radiant command using the absolute
[Radiant] [ANN] Radiant 0.6.6 - Chiseled Release (bugfixes)
Looks like it's time for another release of Radiant: http://radiantcms.org/download/ Radiant 0.6.6 Chiseled corrects two showstopper bugs in yesterday's 0.6.5 release that affect upgrading existing installations and the proper functioning of view templates in extensions. All users of 0.6.5 should upgrade immediately. 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) * 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? * Make sure extension view paths override Radiant view paths. [Josh French] * Fix problem in framework.rake when public/javascripts/admin doesn't exist. [Sean Cribbs] INSTALLATION We've worked hard to make it easy to install Radiant. For starters you can download it with Ruby Gems: % gem install 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/. UPGRADING FROM 0.6.x 1. Update the Radiant gem: % gem update radiant 2. Change the RADIANT_GEM_VERSION constant in config/environment.rb to 0.6.6. 3. Run the update rake task: rake radiant:update 4. Run migrations: rake db:migrate 4. 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: * Josh French * Sean Cribbs Thanks guys! If you'd like to hop on the development band wagon head on over to our dev site (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/ The Radiant mailing list is also accessible via Ruby forum: http://www.ruby-forum.com/forum/21 Enjoy! -- Sean Cribbs for the Radiant CMS Dev Team http://radiantcms.org ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Daft
I may be daft, but I'm not finding any information on using Javascript inside Radiant CMS sites. Are there some guidelines on how to do this? Thanks ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Daft
If you mean on the public content, then use Javascript however you would with any other system: link to the JS files on your server and go. If you mean on the admin side, you can install the Shards extension (read this http://wiki.radiantcms.org/Using_the_Shards_Extension) On Apr 20, 2008, at 2:28 PM, Andrew Gehring wrote: I may be daft, but I'm not finding any information on using Javascript inside Radiant CMS sites. Are there some guidelines on how to do this? ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Re: [ANN] Radiant 0.6.6 - Chiseled Release (bugfixes)
Fixed everything right up, thanks Sean! -- Posted via http://www.ruby-forum.com/. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Radiant 0.6.5 Upgrade, Admin Interface Errors
On Apr 19, 2008, at 9:12 PM, Phi Sanders wrote: After upgrading a site from 0.6.4 to 0.6.5, I can no longer effectively use the Radiant admin interface. Clicking on any of the Pages give the error below, and layouts just present the unprocessed radius tag r:content / The site itself appears to be fine. This is as vanilla a Radiant install as possible, just archive, markdown, and textile for extensions, and no customization (just edits via the interface). I upgraded to chiseled, 0.6.6, and everything is working swimmingly now. Thanks, ~Phi ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
