Fieldtype

Community
Support

Biber Ltd. does not actively monitor this forum
(but you can still get help from other EE users).

EE 1
EE 2
CKEditor Field

Back to this add-on's main page
View Other Add-ons From Biber Ltd.

CKEditor Field  >  Thread
     

You must be logged in to post.

Has anyone run this with an upgraded CKEditor?

General

TacomaWeekly
Posted: 26 January 2011 05:33 PM
TacomaWeekly

I am going to slip in CKEditor 3.5 and test, but I am wondering if anyone else has done the same?  Any issues or gotchas?
 
TacomaWeekly
Posted: 26 January 2011 07:03 PM # 1
TacomaWeekly

To get some knowledge in to the community, I’ll report my own findings:

First, CKEditor 3.5 seems to be a clean transplant.  While I don’t have extensive usage yet, early testing looks clean.  If I run in to any issues I will report here.

Second, I had also moved my EE System folder from my site root to a location outside of my site root.  This broke the field.  The issue is that by design the CKEditor javascript library is expected in a defined path under the system.  This was something like this:

/system/expressionengine/third_party/bbr_ckeditor/ckeditor/ 

Taking my lead from some other wysiwyg plugins I have seen, I put my copy of the ckeditor javascript library under my themes folder.  I used this path:

/themes/third_party_ckeditor/ 

I did need one change to this plugin to support that.  I located the file ft.bbr_ckeditor.php under the third_party folder and edited line 154 to read this:

$ckeditor = new CKEditor('/themes/third_party/ckeditor/'); 
 
     
 
CKEditor Field ERROR →