Sean,

Thanks for the help.

Yep, there is a fck extension which I only used briefly as I had some 
issues with it (I can't recall what didn't work/fit for me). Since then 
I have been using the fck plugin at 
http://rubyforge.org/projects/fckeditorp/ with a radiant extension which 
replaces the textarea if the filter type is "RichText". With fck setup 
to ignore radiant tags, this was working fine, until uploading documents 
broke. I just can't figure out why uploading is no longer working.

If you can share your fck extension I would grateful. It may help me 
work out what has gone wrong for me.

Also, is it possible to install a rails plugin within a radiant extension?

Cheers,
Mark

Sean Cribbs wrote:
> Mark,
>
> Yes, we have an FCKeditor extension, but it's so customized, I'm not 
> sure how well it will translate to the outside world. Correct me if I'm 
> wrong, but there is an existing FCK extension.  I wrote one from 
> scratch, with just a few ideas from an existing WYSIWYG extension (being 
> able to toggle the control on and off).
>
> Normally I don't recommend a WYSIWYG editor for Radiant because of the 
> potential smattering of Radius tags that would not be understood by the 
> editor.  We got by with this in two ways:
>
> 1) Most pages used a template (one of the mentioned extensions) that hid 
> the majority of the Radius code.
>
> 2) For the tags that HAD to be in the editable content areas, we made 
> sure they could operate as singletons (they automatically render a 
> snippet) and used FCK to generate placeholders inside them.  I believe 
> we had only two kinds of these.
>
> Redken is also a very graphic-intensive site, so most pages consisted of 
> several graphics in a row without text.  So FCK was mostly used to 
> preview the inserted images.
>
> Sean
>
> Mark Gallop wrote:
>   
>> Hi Sean,
>>
>> Does the FCKEditor integration comment indicate that you have a working 
>> FCKEditor extension for page editing? I have been trying get fckeditor 
>> working for page editing but the results have been a bit inconsistent.
>>
>> Cheers,
>> Mark
>>
>> Sean Cribbs wrote:
>>   
>>     
>>> Folks,
>>>
>>> Here's the moment you have all been waiting for (or at least I'd like to 
>>> think)!  For the past four to five months I have been working with the 
>>> wonderful team at Digital Pulp to develop the new website for Redken.  
>>> We are proud to say that it has had its official launch this morning!  
>>> Check it out:
>>>
>>> http://redken.com
>>> - and -
>>> http://redkensalon.com
>>>
>>> It has been an incredible experience working with them, and the Radiant 
>>> community has greatly benefited.  We have released two new versions of 
>>> Radiant and numerous extensions during this tenure.  The following 
>>> extensions were a direct result of my work for Digital Pulp:
>>>
>>> * shards (http://dev.radiantcms.org/svn/radiant/trunk/extensions/shards)
>>> * related_content 
>>> (http://dev.radiantcms.org/svn/radiant/trunk/extensions/related_content)
>>> * reorder, the non-Ajax version 
>>> (http://dev.radiantcms.org/svn/radiant/trunk/extensions/reorder)
>>> * scheduler 
>>> (http://dev.radiantcms.org/svn/radiant/trunk/extensions/scheduler)
>>> * share_layouts 
>>> (http://dev.radiantcms.org/svn/radiant/trunk/extensions/share_layouts)
>>> * multi_site 
>>> (http://dev.radiantcms.org/svn/radiant/trunk/extensions/multi_site)
>>>
>>> I also intend to release a some more over the next weeks, after they 
>>> have been cleaned up for public consumption, namely:
>>>
>>> * file_system - Save/load Radiant models to/from the file system so they 
>>> can be managed in an SCM
>>> * templates - Structure pages externally and provide a customized 
>>> interface for editing
>>> * asset_manager - A full-featured asset manager, with mass upload, asset 
>>> expiration, usage reports, and FCKEditor integration
>>>
>>> A big thank you and congratulations to all of the team at Digital Pulp 
>>> (in no particular order) -- John, Justin, Josh, Michael, Alex, Brian, 
>>> Sarah, David; and to my good friend Scotty Moon who also helped on the 
>>> project.
>>>
>>> Cheers,
>>>
>>> Sean
>>> _______________________________________________
>>> Radiant mailing list
>>> Post:   [email protected]
>>> Search: http://radiantcms.org/mailing-list/search/
>>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>>
>>>   
>>>     
>>>       
>> _______________________________________________
>> Radiant mailing list
>> Post:   [email protected]
>> Search: http://radiantcms.org/mailing-list/search/
>> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>>
>>   
>>     
>
> _______________________________________________
> Radiant mailing list
> Post:   [email protected]
> Search: http://radiantcms.org/mailing-list/search/
> Site:   http://lists.radiantcms.org/mailman/listinfo/radiant
>
>   

_______________________________________________
Radiant mailing list
Post:   [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to