Error when trying to use the development (source) version of CKEditor [#2138969]

I can't get the module to work with the development version of CKEditor (from GIT: https://github.com/ckeditor/ckeditor-dev)

I get the following error:

TypeError: editor.ui.addButton is not a function
command : 'drupalbreak'

Disabling drupalbreak removes the error, but CKEditor still doesn't show up.

Isn't it possible to use the development version of CKEditor?
I really need it to debug a custom plugin.

Comment	File	Size	Author
#8	ckeditor-local-version-config-plugins.png	101.58 KB	Anonymous (not verified)

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

anrikun CreditAttribution: anrikun commented 19 November 2013 at 09:46

Issue summary:

View changes

Added a link to the GIT page.

Comment #2

anrikun CreditAttribution: anrikun commented 22 January 2014 at 12:43

Any answer please.

Comment #3

cFreed CreditAttribution: cFreed commented 26 February 2015 at 00:35

Hi,

I just got the same behaviour.

Having to debug my own ckeditor plugin, I wanted to replace the ckeditor minified version by the development one.
I loaded exactly the same built (4.4.7 full, plus "widget" plugin) which previously worked fine.

And suddenly I get the error "TypeError: editor.ui.addButton is not a function".
It fires not only on "drupalbreaks" plugin (as noticed by anrikun) but also on "video-filter" plugin and on my own new plugin, both using the same add-button strategy.

In addition, what puzzles me is: with Firebug, if I activate the "Stop on any error" option, it does NOT stop on the error, and also turns deactivated as soon as the error message appeared.
So we can't even look at the current data to explain what happened.

Nobody interested?

Fred

Comment #4

berenddeboer CreditAttribution: berenddeboer commented 27 March 2015 at 07:43

To get people going, here some tricks. To get the dev version to turn up in wysiwyg/editors/ckeditor.inc.wysiwyg_ckeditor_version() have a return statement as the first line:

return '4.4.7';

In sites/all/libraries/ckeditor/core/config.js make sure you set the plugins property to something like this (loads all):

	plugins: 'dialogui,dialog,about,a11yhelp,dialogadvtab,basicstyles,bidi,blockquote,clipboard,button,panelbutton,panel,floatpanel,colorbutton,colordialog,templates,menu,contextmenu,div,resize,toolbar,elementspath,enterkey,entities,popup,filebrowser,find,fakeobjects,flash,floatingspace,listblock,richcombo,font,forms,format,horizontalrule,htmlwriter,iframe,wysiwygarea,image,indent,indentblock,indentlist,smiley,justify,menubutton,language,link,list,liststyle,magicline,maximize,newpage,pagebreak,pastetext,pastefromword,preview,print,removeformat,save,selectall,showblocks,showborders,sourcearea,specialchar,scayt,stylescombo,tab,table,tabletools,undo,wsc',

I think the minimum plugin you need is dialog.

Comment #5

gifad CreditAttribution: gifad commented 1 April 2015 at 13:08

Thanks berenddeboer, your post helped me to get out of my confusion between sites/all/libraries/ckeditor/core/config.js and sites/all/libraries/ckeditor/config.js

Comment #6

cFreed CreditAttribution: cFreed commented 19 April 2015 at 15:47

Hi berenddeboer, thanks a lot for this post.

Unfortunately I'm reading it late, so without any response at the time I fired the issue, I was led to dig more into the minified source and to guess something like you explain about plugins activation, but didn't know how to achieve it.

So for my needs (debug my own ckeditor plugin) I "simply" modified the minified version inserting line-breaks where I wanted the debugger to be able to work... then testing, finding other interesting place and inserting new line-breaks... and so on... This was a painful exercice, but quite improving my skills though!

Anyway, thanks to have given an explanation which finally enlightens me.

Comment #7

cFreed CreditAttribution: cFreed commented 19 April 2015 at 15:51

Status:

Active

» Closed (fixed)

Comment #8

Anonymous (not verified) CreditAttribution: Anonymous as a volunteer commented 23 October 2015 at 02:22

File	Size
ckeditor-local-version-config-plugins.png	101.58 KB

To add additional information to this ticket. You can also achieve the results without editing any files.

Edit any CKEditor profile within the modules' configuration page and at Advanced options in the 'Custom JavaScript configuration' you can add something like this:

config.plugins = 'a11yhelp,about,adobeair,ajax,autogrow,basicstyles,bbcode,bidi,blockquote,button,clipboard,codesnippet,codesnippetgeshi,colorbutton,colordialog,contextmenu,devtools,dialog,dialogadvtab,dialogui,div,divarea,docprops,elementspath,enterkey,entities,fakeobjects,filebrowser,find,flash,floatingspace,floatpanel,font,format,forms,horizontalrule,htmlwriter,iframe,iframedialog,image,image2,indent,indentblock,indentlist,justify,language,lineutils,link,list,listblock,liststyle,magicline,mathjax,maximize,menu,menubutton,newpage,pagebreak,panel,panelbutton,pastefromword,pastetext,placeholder,popup,preview,print,removeformat,resize,richcombo,save,selectall,sharedspace,showblocks,showborders,smiley,sourcearea,sourcedialog,specialchar,stylescombo,stylesheetparser,tab,table,tableresize,tabletools,templates,toolbar,undo,widget,wysiwygarea,xml';

I use the local CKEditor provided by the Debian operating system package repository. After pointing the module configuration to the local version, I had to manually insert the plugin configuration above. If you insert a plugin that does not exist, CKEditor will not load.

You can check the debugger in your browser to see what plugin is reported to be not found. This is an edit and refresh repeat process for each missing plugin. To find out what plugins are available you will have to browse to the location of your CKEditor plugin folder provided by the installation.