I noticed that the latest dev release works as expected with the optimized version of the latest CKEditor 4.x download using the Builder, http://ckeditor.com/builder. However, if I build it as "Source" for development, the "The version of CKEditor could not be detected" error appears.

Is there interest in providing detection as well for this non-optimized source version that might be helpful for development?

CommentFileSizeAuthor
#2 wysiwyg-ckeditor-4-source.2243645.2.patch2.76 KBTwoD
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jmuzz’s picture

Yes I don't see why it shouldn't be supported. I tried to do this today as well. Being able to easily mess with the CKEditor code that's actually in use on an installation could prove very helpful for development.

TwoD’s picture

Status: Active » Postponed (maintainer needs more info)
FileSize
2.76 KB

I am interested in using the Source variants of editors, where available, because it helps debugging and making sure new features work.
The Source variant of CKEditor 4 does however not include a version number in the ckeditor.js file, so we'll need to check the changelog instead. Another issue is that we currently have no idea which plugins were included (Wysiwyg assumes the Full package was downloaded), and it's likely the package has been customized since it's pretty much part of the download procedure to do so. That's something we'll need to solve for non-source variants as well, and all editors.

Anyway, a patch like this should be enough to make it possible to detect and use the Source variant when installed, but apparently the CKEditor API is different in this variant?!

We're missing editor. ui.addButton(), which is used by the cross-editor plugin code (and the native CKEditor plugins!) to add the buttons to the toolbar.

In an attempt to work around this, I removed all the cross-editor plugin code, but still CKEDITOR.replace(params.field, settings); does nothing. No exceptions - even caught ones - or anything else. The editor just does not run in this mode, and I don't have time to figure out why...

manuelBS’s picture

I had the same problem as discribed in the initial issue. The patch works nice and fixed the problem for me. Thanks!