Re: [Radiant] help with dynamic_image extension

2008-11-18 Thread Adam van den Hoven
I'll jump on IRC soonest (any suggestions for a good mac client?) in the mean time: ls -la total 84 drwxrwxr-x 10 canrc pg925332 4096 2008-11-18 23:06 . drwxr-x--x 28 canrc pg925332 4096 2008-11-18 23:06 .. -rw-rw-r-- 1 canrc pg925332 21273 2008-10-28 21:35 CHANGELOG -rw-rw-r-- 1 canrc p

Re: [Radiant] help with dynamic_image extension

2008-11-18 Thread Andreas Roedl
Hey Adam, On Wed, Nov 19, 2008 at 8:02 AM, Adam van den Hoven <[EMAIL PROTECTED]> wrote: > > I'm trying out the dynamic_image extension and I'm running into a small > problem. I keep getting "unable to open image > `/public/dynamic_images/19b15c4d2dbe9802f43d7a171b27196e.png': No such file > or di

[Radiant] help with dynamic_image extension

2008-11-18 Thread Adam van den Hoven
Hey all. I'm trying out the dynamic_image extension and I'm running into a small problem. I keep getting "unable to open image `/public/ dynamic_images/19b15c4d2dbe9802f43d7a171b27196e.png': No such file or directory: " in my output. Now I'm assuming that its a permissions issue but I'm no

Re: [Radiant] Re: page_attachments / :secret / #protect_from_forgery error

2008-11-18 Thread Sean Cribbs
For some reason, the CSRF protections in Rails require that if you use :active_record_store for sessions, the key given in your config setting must be equivalent to the key given in the call to protect_from_forgery in the controller. One way around this might be to add an after_initialize bloc

[Radiant] Re: page_attachments / :secret / #protect_from_forgery error

2008-11-18 Thread Steven Line
Geez, I don't know what just happened here, but I stuck this line of code in some obscure file I didn't even know existed and it fixed my problem. I stuck this line of code: protect_from_forgery :secret => 'asdfqwexxcoivswhallelujah!yippee!fqewwel', :except => :index into my radiant-0.

[Radiant] Re: page_attachments / :secret / #protect_from_forgery error

2008-11-18 Thread Steven Line
This link appears that it will help. I would prefer to build sites without learning anything but sometimes I am forced. http://api.rubyonrails.org/classes/ActionController/RequestForgeryProtection/ClassMethods.html -- Posted via http://www.ruby-forum.com/. _

[Radiant] page_attachments / :secret / #protect_from_forgery error

2008-11-18 Thread Steven Line
Hi - I am haunted by this :secret / #protect_from_forgery / form_authenticity_token error that seems to stop me every few months. Luckily it has been in remission for a few months. I just had a few hours to finish this site and whammo! Up pops this much feared error. The cause is that I installe

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Anton J Aylward
Steven Southard said the following on 11/18/2008 01:33 PM: > I think maybe you just need to take another approach with her. Seems > sometimes web development is more psychology then programming. Does > she just put her hand over her ears when you say Markdown or Textile? > I've had a clien

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Anton J Aylward
Adam van den Hoven said the following on 11/18/2008 01:42 PM: > You just hit on an interesting idea for an extension. > > Frequently, people are going to reuse the same bits over and over. > Instead of making them go find it, what if we put a "scratchpad" on > the right hand side of the parts

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Adam van den Hoven
A couple of thoughts. 1) In general, isn't it the case that the site developer is going to want to deal with content. When you're creating content, you're seldom calling for the the part of some other page (I prefer to do this sort of work in the the layout myself). I'm not sure exposing co

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Chris Parrish
Alright, since this post is already heading in this direction, I'll throw out some ideas that I've been working on. These are getting pretty refined in my mind and I'm looking into creating an extension around them (possibly waiting for the new UI, we'll see)... 1. I think the textareas nee

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Jim Gay
On Nov 18, 2008, at 1:42 PM, Adam van den Hoven wrote: You just hit on an interesting idea for an extension. Frequently, people are going to reuse the same bits over and over. Instead of making them go find it, what if we put a "scratchpad" on the right hand side of the parts (which will co

Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors?

2008-11-18 Thread Jose Hales-Garcia
On Nov 18, 2008, at 10:27 AM, Marcus Blankenship wrote: Everyone can get out their shotgun for what I'm about to say, but... BigMedium CMS (www.globalmoxie.com) is an excellent example of a user-friendly CMS that non-techies can use. Maybe that could be our model. If you haven't played with i

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Steven Southard
That's actually something I'd use. I really like that idea. It's kind of there with the filters and available tags but I really like the idea of a customizable scratch pad. I'd use it all the time. Steven On Nov 18, 2008, at 12:42 PM, Adam van den Hoven wrote: You just hit on an intere

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Mohit Sindhwani
Casper Fabricius wrote: However, I have a client whose content editor is very frustrated with the system. She can only just tolerate using Markup, and she refuses to write any kind of HTML - Radius tags falls into this category from her point of view. According to her, a proper CMS would hide a

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Adam van den Hoven
You just hit on an interesting idea for an extension. Frequently, people are going to reuse the same bits over and over. Instead of making them go find it, what if we put a "scratchpad" on the right hand side of the parts (which will consume some space from the parts but that should be OK t

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Steven Southard
I think maybe you just need to take another approach with her. Seems sometimes web development is more psychology then programming. Does she just put her hand over her ears when you say Markdown or Textile? I've had a client like that! She just wants to make headers, paragraphs, and upl

RE: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors?

2008-11-18 Thread Marcus Blankenship
Everyone can get out their shotgun for what I'm about to say, but... BigMedium CMS (www.globalmoxie.com) is an excellent example of a user-friendly CMS that non-techies can use. Maybe that could be our model. If you haven't played with it, you should, as Josh has done a great job of abstracting t

Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Adam van den Hoven
I'd like to see this too. I use it for exactly this purpose, to give non-technical people the ability to manage a simple website using a CMS. To be honest, I think that the mostly technical person doesn't really need an OS CMS, they can either hand code the HTML just as easily (maybe run so

[Radiant] Can Radiant be really easy to use for non-technical content editors?

2008-11-18 Thread Casper Fabricius
Hi everyone, I've used Radiant for more than 10 web sites during the past 1,5 years, and I really like it. Definitely the best CMS for Rails. However, I have a client whose content editor is very frustrated with the system. She can only just tolerate using Markup, and she refuses to write