[Radiant] Comments extension: 500 Internal Server Error

2007-10-11 Thread Teyo Tyree
I am a new radiant user am have some difficulty getting the comments extension working. I have svn exported the required extensions code to: /var/radiant/extensions/comments and /var/radiant/extensions/admin_part and have successfully migrated the database: rake db:migrate:extensions If I

[Radiant] conditional display of image

2007-10-11 Thread Mathieu Arnold
Hi, I'm attaching some images to some posts on my blog, and as I don't want to have too big images on the home page and on the archive pages, I devised the following code that I put on the first part of my page r:unless cond=!request.nil? Regexp.new(tag.locals.page.slug) =~

Re: [Radiant] A common repository for extensions

2007-10-11 Thread Sean Cribbs
Hans-Christian, I started an application at RailsConf that would be used to keep a registry of available extensions. It has been on the back-burner for quite a while, but I'll make it a point to get it ready for the 0.6.5 release. Sean Hans-Christian Fjeldberg wrote: Hello. I am quite

[Radiant] A common repository for extensions

2007-10-11 Thread Hans-Christian Fjeldberg
Hello. I am quite new to Radiant CMS, but not to Ruby and Ruby on Rails. I am planning to do some contributions this semester, as I am doing my last year at my university and writing a paper about open source, and using a research method called action research (never mind). As a new user

Re: [Radiant] A common repository for extensions

2007-10-11 Thread Mitch Pirtle
On Oct 11, 2007, at 09:44 , Sean Cribbs wrote: I started an application at RailsConf that would be used to keep a registry of available extensions. It has been on the back-burner for quite a while, but I'll make it a point to get it ready for the 0.6.5 release. Why not piggyback on the

Re: [Radiant] A common repository for extensions

2007-10-11 Thread Sean Cribbs
Plugins and Radiant extensions are substantially different; I don't intend to create yet another plugin repository.There are two components to this effort: 1) A website that can be updated by extension authors to list their extensions. 2) Some command-line utilities to install, uninstall,

Re: [Radiant] A common repository for extensions

2007-10-11 Thread Aitor Garay-Romero
Regarding installation of extensions, why not base it in the standard gem system? A system must be devised to let Radiant interact with the gem system, but when that is solved we can take advantage of all the gem infrastructure that is already implemented. /AITOR On 10/11/07, Sean

[Radiant] Copy/Move extension

2007-10-11 Thread Christian Billen
Hello, I downloaded and installed the copy/move extension according to the instructions at http://darcs.bigchieflabs.com/radiant/extensions/ copy_move/rdoc/, I tried in 0.6.2 and 0.6.3 and in neither case can I see the copy/ move option in the admin UI. The extension shows as installed

Re: [Radiant] Copy/Move extension

2007-10-11 Thread Christopher Zimmermann
hey there, Just installed it as well in 0.6.3 - it worked. Did you run the rake task as per the instructions? Just checking. Im just wondering if the copy-move.png image did not get copied to your public/image/admin directory somehow. You could check if the image is there - or maybe do a view

Re: [Radiant] Comments extension: 500 Internal Server Error

2007-10-11 Thread Ryan Heneise
Hi Teyo, Which comments extension are you using? I know there's a couple; mine's at http://svn.artofmission.com/svn/plugins/radiant/extensions/ comments/ One thing I noticed is the path to your extensions doesn't look right: /var/radiant/extensions/admin_part admin_part should probably be

Re: [Radiant] Copy/Move extension

2007-10-11 Thread Dominic
If you have the reorder and copy/move extension both installed one will override the others view, so you will have to combine the contents of the_node.rhtml files - to something like this: td class=duplicate-child%= link_to image('copy- move', :alt = 'CopyMove'),

Re: [Radiant] Comments extension: 500 Internal Server Error

2007-10-11 Thread Ryan Heneise
Are you using the latest version of Radiant? If not, you may be having problems with the routes that the comments extension is using. I recommend updating to the latest Radiant. Let me know if you already are, and I'll look into it further. - Ryan On Oct 11, 2007, at 11:37 AM, Teyo Tyree

Re: [Radiant] Comments extension: 500 Internal Server Error

2007-10-11 Thread Teyo Tyree
Ryan, I am using radiant 0.6.3. Then latest version of admin_parts and the most recent version of your comments extension. -teyo On 10/11/07, Teyo Tyree [EMAIL PROTECTED] wrote: I am a new radiant user am have some difficulty getting the comments extension working. I have svn exported the

Re: [Radiant] Installation problems, Radiant 0.63 fresh install

2007-10-11 Thread Teyo Tyree
Hi Niko, The path to radiant should be /usr/bin/radiant. Does that file exist? If it does there is likely something wrong with your $PATH environment variable in your shell. What is the output of echo $PATH? -teyo On 10/11/07, Niko Kotiniemi [EMAIL PROTECTED] wrote: Hi, I've tried

[Radiant] Installation problems, Radiant 0.63 fresh install

2007-10-11 Thread Niko Kotiniemi
Hi, I've tried Googling for a solution and reading through the tutorials, how to's etc. but to no avail, it seems that I've a rare sort of problem. I have Ruby, Rails and Radiant (+MySQL) installed on a Ubuntu 7,04 desktop computer, Rails and Radiant were successfully installed through gems.

Re: [Radiant] Installation problems, Radiant 0.63 fresh install

2007-10-11 Thread James Thompson
Does the 'rails' command work? If not, then wherever gem is installing executables isn't in your path. If so, then my guess is something went awry when Radiant installed, have you tried a gem uninstall and then reinstall? -James On Oct 11, 2007, at 3:09 PM, Niko Kotiniemi wrote: Hi,

[Radiant] TinyMCE

2007-10-11 Thread Jason Campbell
Hi All, I am new to Radiant and ROR, I have kept my eye on the Radiant CMS for a while now and am getting ready to install it for a client project I am working on. A while back there was a TinyMCE extension which I downloaded and, however the extension no longer seems to be available (I get a 503

Re: [Radiant] A common repository for extensions

2007-10-11 Thread Mitch Pirtle
On Oct 11, 2007, at 10:32 , mark.a.brand wrote: and what value does workingwithrails add ? it appears to me to be an site sponsored by an aggressive commercial entity. Easy tiger, it was just an idea. Seemed like we'd be duplicating a lot of effort that they have already done, that's

Re: [Radiant] TinyMCE

2007-10-11 Thread Ryan Heneise
I have an extension that uses TinyMCE here: http://svn.artofmission.com/svn/plugins/radiant/extensions/rich_text/ Unfortunately, I can't provide any support for it, but it works for me(tm). Maybe it will get you started in the right direction. - Ryan On Oct 11, 2007, at 2:30 PM, Jason

Re: [Radiant] TinyMCE

2007-10-11 Thread Edwin Vlieg
I updated the code from the original TinyMCE extension to work with other extensions. Unfortunately I didn't have time to test it very well, so you might run in to problems. If you find bugs, please contact me. http://code.google.com/p/radiant-tinymce-extension/ Edwin Op 11-okt-2007, om

Re: [Radiant] A common repository for extensions

2007-10-11 Thread Sean Cribbs
In what sense? WWR is primarily a directory of people, groups, projects, and companies. Its focus is entirely different. Is there something I'm not picking up on? Please don't take these questions as confrontational, I just don't understand how WWR is related to the problem that an

Re: [Radiant] TinyMCE

2007-10-11 Thread Daniel Sheppard
On Thu, 11 Oct 2007 16:11:19 -0500 Ryan Heneise [EMAIL PROTECTED] wrote: Forgot to mention... the rich_text extension requires the admin_parts extension: http://soxbox.no-ip.org/radiant/svn/extensions/admin_parts/ I would advise moving your extensions away from admin_parts and using shards. I

[Radiant] Mailer Extension question

2007-10-11 Thread Will Green
Perhaps more a Ruby question than a Radiant question, but... I'd like to alter the html that the Mailer Extension outputs for r:mailer:option tags within a r:mailer:radiogroup. Rather than have the Label tag follow the Input tag, I want to wrap in Input tag in the Label tag (with the label