Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?
Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: 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 all this technical stuff and provide custom forms for all types of content. Casper, my solution would be to find a slightly more technical client :P No, I'm joking (of course!) Here's what I would recommend: 1. First, factor out as far as possible so that whatever is not page specific is in snippets. 2. If all she needs is a few styles of pages, I would create different page types or layouts. 3. Then tell her that the different parts that she wants need to go into different page parts. It would be cool if you could modify the Add Child behavior to allow you to select the kind of child page you want and then give you a blank page with all the different tabs created (page parts)... or it could be done with a bit of Javascript that detects when you change the Layout/ page and automatically adds in the different page parts? It could even be a special drop down box next to the Page Type that triggers the actions? 4. The problem: she still needs to use textile for some of the things, such as images. I'm not sure if the Textile Helper will help? It's been a while since I looked at it, but there's a hello world guide on my blog: http://notepad.onghu.com/2007/3/28/using-textile-editor-plugin-and-acts_as_textiled It could make some things easier for her, I hope... without going down the path of WYSIWIG. If you do go down WYSIWIG, I hear good things about WymEditor - and Benny's on the list! Of course, Casper, you are more experienced than I am. Do let us know what you eventually settle on :) Cheers, Mohit. 11/19/2008 | 2:45 AM. ___ 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
[Radiant] Passenger on openSUSE
I've recently given up on Mandriva and moved to opehSUSE and on the whole don't regret it. However I now have some problems wit virtual hosts and passenger. I used to have a demo of Radiant on my laptop. Entry in the hosts file for 'radiantdemo.tld' == 127.0.0.1, and a few other virtual hosts like that. Moving my old virtual hosts files to the openSUSE apache2 config directory has proven unsuccessful and confusing. Attempting to install passenger is further confusing, I get an error from apache2 on start-up saying it can't find the 'ruby' module. I anyone on this forum using openSUSE + passenger ? Any pointers? -- Over the last few centuries, mathematicians have demonstrated a remarkable tendency to underestimate the cryptanalytic powers of blunt and heavy objects. -- Jamie Reid, CISSP ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] help with dynamic_image extension
Adam van den Hoven wrote: I'll jump on IRC soonest (any suggestions for a good mac client?) Colloquy is what everyone I know uses. Sean ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Re: page_attachments / :secret / #protect_from_forgery error
It seems Rails just patched a CSRF vulnerability yesterday. http://weblog.rubyonrails.com/2008/11/18/potential-circumvention-of-csrf-pro tection-in-rails-2-1 Victor On 11/18/08 11:41 PM, Sean Cribbs [EMAIL PROTECTED] wrote: 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 block like so: config.after_initialize do ActionController::Base.request_forgery_protection_options.update :secret = 'putyourreallylongsha1hashkeyhere' end Sean Steven Line wrote: 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.6.9/app/controllers/admin/page_controller.rb and the error went away. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant Victor Zuniga Westerville Public Library 126 S. State St. | Westerville, OH 43081 Phone: 614.882.7277 | ext 165 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] help with dynamic_image extension
yeah that's what I'm using now... Thx, by the way, for the help. Adam On 19-Nov-08, at 6:31 AM, Sean Cribbs wrote: Adam van den Hoven wrote: I'll jump on IRC soonest (any suggestions for a good mac client?) Colloquy is what everyone I know uses. Sean ___ 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] help with dynamic_image extension
Colloquy http://colloquy.info/ On 18 Nov, 2008, at 23:42, Adam van den Hoven wrote: I'll jump on IRC soonest (any suggestions for a good mac client?) ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Can Radiant be really easy to use for non-technical content editors?
I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: 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 all this technical stuff and provide custom forms for all types of content. Casper, my solution would be to find a slightly more technical client :P No, I'm joking (of course!) Here's what I would recommend: 1. First, factor out as far as possible so that whatever is not page specific is in snippets. 2. If all she needs is a few styles of pages, I would create different page types or layouts. 3. Then tell her that the different parts that she wants need to go into different page parts. It would be cool if you could modify the Add Child behavior to allow you to select the kind of child page you want and then give you a blank page with all the different tabs created (page parts)... or it could be done with a bit of Javascript that detects when you change the Layout/ page and automatically adds in the different page parts? It could even be a special drop down box next to the Page Type that triggers the actions? 4. The problem: she still needs to use textile for some of the things, such as images. I'm not sure if the Textile Helper will help? It's been a while since I looked at it, but there's a hello world guide on my blog:
RE: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors?
Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: 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 all this technical stuff and provide custom forms for all types of content. Casper, my solution would be to find a slightly more technical client :P No, I'm joking (of course!) Here's what I would recommend: 1. First, factor out as far as possible so that whatever is not page specific is in snippets. 2. If all she needs is a few styles of pages, I would create different page types or layouts. 3. Then tell her that the different parts that she wants need to go into different page parts. It would be cool if you could modify the Add Child behavior to allow you to
Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors?
Off topic, possibly... But is that FLEX app open source? Andrew On Wed, Nov 19, 2008 at 11:28 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: 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 all this technical stuff and provide custom forms for all types of content. Casper, my solution would be to find a slightly more technical client :P No, I'm joking (of course!) Here's what I would recommend: 1. First, factor out as far as possible so that whatever is not page specific is in snippets. 2. If all she needs is a few styles of pages, I would create different page types or layouts. 3. Then tell her that the different
RE: [Radiant] Can Radiant be really easy to use fornon-technicalcontent editors?
Sorry, then. Yes, the Flex language/compiler is open source, and that app was as well. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Gehring Sent: Wednesday, November 19, 2008 10:39 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use fornon-technicalcontent editors? Off topic, possibly... But is that FLEX app open source? Andrew On Wed, Nov 19, 2008 at 11:28 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're probably better off going with some WymEditor-like solution + cleaning up and education. Apart from the actual editing of content, it'd be really cool to find and easy way to hide some stuff in Radiant from the customer. Eg. some things such as the CSS and RSS things, and sometimes some page-parts. And maybe in some cases even the popup menus: layout, page type, status and filter. cheers, Simon PS. I begun the search for the perfect solution to this in my thesis, if anyone's interested: http://simon.fi/en/thesis On Nov 18, 2008, at 20:46 , Mohit Sindhwani wrote: 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 all this technical stuff and provide custom forms for
RE: [Radiant] Can Radiant be really easy to usefornon-technicalcontent editors?
Oh, sorry. ;-) This is the original page, and has a source link. (http://weblogs.macromedia.com/mc/archives/disclosableRTE.zip) If you like that sort of thing, here's a few more flex resources. Forgive if this if off topic. Adobe Flex downloads page: http://www.adobe.com/products/flex/flexdownloads/ Nice, free actionscript / Flex IDE: http://www.flashdevelop.org/community/ I you want any help getting it compiled/changed/working, let me know. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Gehring Sent: Wednesday, November 19, 2008 10:45 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to usefornon-technicalcontent editors? I didn't mean your post was off topic, I meant mine might be :-) What/where is the source to the app? Thanks, Andrew On Wed, Nov 19, 2008 at 11:41 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Sorry, then. Yes, the Flex language/compiler is open source, and that app was as well. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Gehring Sent: Wednesday, November 19, 2008 10:39 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use fornon-technicalcontent editors? Off topic, possibly... But is that FLEX app open source? Andrew On Wed, Nov 19, 2008 at 11:28 AM, Marcus Blankenship [EMAIL PROTECTED] wrote: Another thought, crazy as it might be, would be to create a FLEX component that represents a content editor. We do this on some of our flex apps, and it works well. Here's an example: http://cfsilence.com/blog/tips/rte/bin/richTextEditor.cfm This might allow for more control than JS based editors give, I'm not sure. Just another thought, from a FLEX nerd. Marcus -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Casper Fabricius Sent: Wednesday, November 19, 2008 10:21 AM To: radiant@radiantcms.org Subject: Re: [Radiant] Can Radiant be really easy to use for non-technicalcontent editors? I am happy my frustrations resulted in some discussion and good ideas. The ideas for extensions for a scratch pad, filter toolbars and som WymEditor + paperclipped would all be highly usable to me, but I don't have the time to build any of them right now. I have used TinyMCE filter for some projects, but it has - amongst other things - resulted in me having to say to the customer: No, you have to let me edit the frontpage, if you edit it, it will get messed up (Because TinyMCE has a habit of messing HTML up). But WymEditor might be more clean at that, so I think I'll try and use it. The template extension can do many of the things you mention, such as providing custom forms for different templates, and allowing the user to select the appropriate template when clicking Add Child. I'll let you know if I make any interesting discoveries along the way. Med venlig hilsen / Best regards, Casper Fabricius http://casperfabricius.com On 19/11/2008, at 10.19, Simon Rönnqvist wrote: Hi! Yes some WymEditor + paperclipped combination could be really cool. I've never really used WymEditor for any of my clients.. but I've tried both Markdown and a tightly configured TinyMCE (which would be pretty close to WymEditor). With Markdown I've seen that the content remains largely unstyled, the client eg. just used UPPERCASE-letters for headings and so on... maybe a Markdown-toolbar would help stimulate the usage of Markdown-code? With the TinyMCE solution again stuff got marked up a bit inconsistently, and often using strong for some headings, even though it didn't cause quite the mess that a normal 'liberal' WYSIWYG would have. My guess is that using WymEditor would be a good way to give your customer a way to try and express what she's looking for, but chances are that you'll have to go in and clean up after her a few times... but along with that you could also try to agree with her on certain practices in the future, to retain consistency. I've been searching for the perfect solution for quite some time, but I've begun thinking that this last step of cleaning up and educating can't really be avoided if you want perfect results... we can just try to minimize this last task. Markdown+toolbar could also be something to try out, but I fear it might still be considered a bit too intimidating (and Textile I find even more intimidating). Another thing that I've been thinking that could be suitable for some cases (but I haven't tried out) is in-place editing... but I don't know how well that'd fit into Radiant. And yes forms (using your own plug-in) or splitting content into many page parts could definitely also in some cases be the right solution... but in cases where we want to allow more flexibility, to allow the customer to structure their content more freely... we're
[Radiant] Help with Radiant/Rails Implementation
I'm stumped and could use some help/advice -- time to show your mad hackr skillz... Please forgive the length, there's some needed background involved. Background -- SnS TextAsset models track their dependencies (each model parses its content and identifies r:javascript or r:stylesheet tags within). Easy. Then, when any model is updated, it announces this to all the other instances who check their dependencies and, if they depended on the updated model, adjust their own effectively_updated_at date. So far, still easy. The Problem --- Saving the effectively_updated_at date -- not so easy. TextAsset models have callbacks -- none of which should fire when only saving effectively_updated_at. Specifically, these are: * Rails automatic timestamps (created_at, updated_at) * before_update and before_create callbacks (via Radiant's UserActionObserver to set created_by and updated_by) * My own before_save callback which parses the content to update its own dependencies (mentioned above) * My own after_save callback to announce to the other models that this one's been changed (mentioned above) Current Solution The current solution is to store effectively_updated_at in a separate model with a has_one relationship to its TextAsset. That way changes to the date are done directly through that sub-model and so doesn't trigger the callbacks on the related TextAsset. This works but it *really* bugs me having a separate table just for one field (a field that really belongs to another model). Help? - Can anyone think of some clever solution that will let me move this attribute into TextAsset? How could I update and save a TextAsset's effectively_updated_at attribute without waking up those callbacks? Or am I just being too picky? Ideas - I'm open to anything here, really. My current ideas include: * Make the TextAsset model explicitly handle all the above callbacks (no more auto timestamps, no more using Radiant's built-in observers). And then, in those callbacks, inspect an instance variable flag (say, @exit_callbacks) to end each routine. It's a bit messy but it also replaces some mess in dealing with the extra table. Mostly I don't like that it ignores Radiant's and Rails built-in tools. I'm also not sure how to make current_user available to a TextAsset (but that's probably not hard). * Add some way to disable callbacks on a particular instance (like maybe: http://github.com/cjbottaro/without_callbacks/tree/master). Seems neat but also sounds like a lot of code for one attribute. I've never used it either so I'm not sure how reliable it is or if it's solid across different Radiant/Rails versions. * Save to the effectively_updated_at column directly using the ActiveRecord's #connection method and SQL commands. Never done this before and it sounds like, well, yuck (but maybe I don't understand it well enough either). And could this even be done in a db-agnostic way? * Your idea here... Thanks, Chris ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Help with Radiant/Rails Implementation
Chris Parrish wrote: * Your idea here... Probably way out on a limb here (blame it on the time), but how about keeping that 1 table for that 1 column! OK, before you relegate it to Junk Mail :) here's an explanation: If I remember correctly (and I may be completely wrong), SnS supports certain types of extensions? If that's the case, then it could be that all extensions using/ relying on SnS can assume the existence of this 1 table for storing information that is updated via callbacks and is intended to bypass all the other callbacks that you mentioned? (Even if you're not supporting extensions, this could be a model/ table that general extensions can use for storing exactly this kind of thing). Cheers Mohit. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Could not load extension from file:
Hello, I am trying deploying my first Radiant site and am running into issues when trying to start the server/console/whatever and running the rake task to migrate the extensions fails as well: Could not load extension from file: fckeditor_extension. #NameError: uninitialized constant FckeditorExtension Could not load extension from file: mailer_extension. #NameError: uninitialized constant MailerExtension The directory names do not have _extension on them. vendor extensions fckeditor mailer I've tried renaming the directories, etc I've installed them locally no problem, but on production this is not the case. Radiant is frozen, if that makes a difference. I'm deploying from a git repo. Anyone have any thoughts. This is being deployed via capistrano to a Joyent Shared Accelerator. Thanks, -- Mike ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Could not load extension from file:
Hi Michael, Could you run the rake task with --trace and post the output? Manuel On Wed, Nov 19, 2008 at 11:10 PM, Michael Krisher [EMAIL PROTECTED] wrote: Hello, I am trying deploying my first Radiant site and am running into issues when trying to start the server/console/whatever and running the rake task to migrate the extensions fails as well: Could not load extension from file: fckeditor_extension. #NameError: uninitialized constant FckeditorExtension Could not load extension from file: mailer_extension. #NameError: uninitialized constant MailerExtension The directory names do not have _extension on them. vendor extensions fckeditor mailer I've tried renaming the directories, etc I've installed them locally no problem, but on production this is not the case. Radiant is frozen, if that makes a difference. I'm deploying from a git repo. Anyone have any thoughts. This is being deployed via capistrano to a Joyent Shared Accelerator. Thanks, -- Mike ___ 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] Could not load extension from file:
Thanks for the reply Manuel, here is the output: ** Invoke production (first_time) ** Execute production ** Invoke environment (first_time) ** Execute environment Could not load extension from file: Fckeditor_extension. #NameError: uninitialized constant FckeditorExtension Could not load extension from file: Mailer_extension. #NameError: uninitialized constant MailerExtension ** Invoke db:migrate:extensions (first_time) ** Invoke environment ** Execute db:migrate:extensions -- Mike ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Could not load extension from file:
Michael Krisher wrote: Hello, I am trying deploying my first Radiant site and am running into issues when trying to start the server/console/whatever and running the rake task to migrate the extensions fails as well: Could not load extension from file: fckeditor_extension. #NameError: uninitialized constant FckeditorExtension Could not load extension from file: mailer_extension. #NameError: uninitialized constant MailerExtension The directory names do not have _extension on them. vendor extensions fckeditor mailer I've tried renaming the directories, etc I've installed them locally no problem, but on production this is not the case. Radiant is frozen, if that makes a difference. I'm deploying from a git repo. Anyone have any thoughts. This is being deployed via capistrano to a Joyent Shared Accelerator. Silly question, this, but have you done rake production db:migrate first? Cheers, Mohit. 11/20/2008 | 10:26 AM. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Could not load extension from file:
yes, db:migrate fails with same extension errors. In trying to figure it out, I've tried installing the Ray extension and trying to manage the extensions that way. However, it is now failing on production as well: bash$ script/console production Loading production environment (Rails 2.0.2) Could not load extension from file: fckeditor_extension. #NameError: uninitialized constant FckeditorExtension Could not load extension from file: mailer_extension. #NameError: uninitialized constant MailerExtension Could not load extension from file: ray_extension. #NameError: uninitialized constant RayExtension I'm adding some output to the extensions_loader to try and figure out why it is failing, guessing it is a pathing issue at this point, not sure why though, possibly due to freezing 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] Could not load extension from file:
John, I hadn't thought of that. I cloned them to install them. I may need to make them submodules and then add them? Thanks, -- Mike ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Could not load extension from file:
On 2008/11/19, at 20:20, Michael Krisher wrote: John, I hadn't thought of that. I cloned them to install them. I may need to make them submodules and then add them? If you cloned them then I can't imagine what the problem might be. ray will default to using submodules if the project you're adding the extension to is managed with git, so I thought maybe that behavior might be tripping things up. Do you see equivalent content in the directories for your local version of the extension and the one in the production environment? It seems like you're missing the ext_name_extension.rb files that should in the root of the extension directories. If I setup a new project and `./script/extension install ray` then delete everything from vendor/extensions/ray I get the exact same error you're getting. ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
