Default CKEditor toolbar used instead of the CKEditor profile because toolbar configuration not a JS Array

I'm having the same problem. Have you found a solution yet? I'll post here if I do find a solution.

Awesome Module BTW.

it should be working, what kind of settings are not kept? (during my testing toolbar buttons and UI color were working).

same here. for ckeditor4.0.1.1 (full)

edit: same for 4.0, having less buttons as only standart version
with 3.6.6 the quickedit does not show an editor at all.

the color is respected, but it just shows the full profile, even if deleted.
so i guess, i just shows all buttons no matter what ...

the question also would be, which text-format should the quick edit use anyway ?

2nd edit: problem is that ckeditor module does not add any js_settings etc. to the normal page ...
so - somehow edit module should trigger this ?

3rd edit: this just didn't let me be .. i debugged, and found out that when in
drupalckeditorwidget.js:50
i set the settings with the printed property out of console it works.
so fe:

settings.toolbar = [
  ['Source'],
  ['Cut','Copy','Paste','PasteText','PasteFromWord','-','SpellChecker', 'Scayt'],
  ['Undo','Redo','Find','Replace','-','SelectAll','RemoveFormat'],
  ['Image','Media','Flash','Table','HorizontalRule','Smiley','SpecialChar'],
  ['Maximize', 'ShowBlocks'],
  '/',
  ['Format'],
  ['Bold','Italic','Underline','Strike','-','Subscript','Superscript'],
  ['NumberedList','BulletedList','-','Outdent','Indent','Blockquote'],
  ['JustifyLeft','JustifyCenter','JustifyRight','JustifyBlock','-','BidiLtr','BidiRtl'],
  ['Link','Unlink','Anchor', 'Linkit']
];

the toolbar is showing.

so it seems to me an string / array confusion ..
jQuery.parseJSON fails, because of the one splitter ('/') not in square bracktes ..

still the used text format is unkown to me, it comes out of
Drupal.edit.metadataCache[propertyID].custom
as long as I have one format i'm fine ... (didn't trace that for now)

solution is to use eval .... so add
settings.toolbar = eval(settings.toolbar);
at
sites/all/modules/edit/createjs/editingWidgets/drupalckeditorwidget.js:50

be aware: this introduces another vulnerability
(ckeditor is using it as well ..)

and here a patch - if you're fine with eval

invalid patch

improved.

making the array when setted, not getted, no longer using evil'd.
should be merged to ckeditor module #1935186: remove eval

changed check from is not array to is stirng

I have a test installation with a minimal number of modules enabled, and the Bartik theme. I have a couple of articles on the site, showing as a standard list of teasers (no views) on the front page.
Using 7.x-1.alpha6 the buttons appear to be respected when editing the teaser display, but not when editing the full node

does my patch from #10 work for you ?

@ytsurk
Yes it does! Way cool!!!

Tested and working fot the 7.x-1.0-alpha6 but not for the latest dev version.

I don't see how it's possible that this patch works for alpha 6 but not for the latest dev version (645e1af9ef1c4ba0b940412c3d3bd14c360d31ff). None of the changes could have any effect on this AFAIK.

me neither ..

caches cleared ?

I'm sorry but I don't get it. Where do I find the file to do the patch in?

It's indicated at the beginning of the patch file, but you should find it at /sites/all/modules/edit/js/edit.js

Investigated this. This is happening because the CKEditor module uses a weird, non-standard JSON serialization to describe the toolbar configuration. The CKEditor module itself deals with converting this somewhere in the PHP code, because it will output Drupal.settings.cke_toolbar_Drupal(Advanced|Basic|Full) for its JS to use. Hence the Edit module has to perform a similar conversion.

http://drupalcode.org/project/edit.git/commit/952cb59

I can confirm that it works.

However, another question (maybe off topic).
Is it by design that the "source" and "full screen" buttons don't show up?

#20: When doing in-place editing? Full Screen: yes, by CKEditor's design. Source: as of CKEditor 4.1, it is possible to have the "Source" button show up when doing in-place editing. One must use CKEditor 4.1's "Source Dialog" plugin to achieve that.

However, you're absolutely right that this is not yet implemented here in Drupal 7. This is how we did it in Drupal 8: #1964316: Automatically use "sourcedialog" plugin/button instead of "sourcearea" plugin/button when using CKEditor for in-place editing. I created an issue+patch to do the same in D7 Edit, please review: #1964320: Automatically use "sourcedialog" plugin/button instead of "sourcearea" plugin/button when using CKEditor for in-place editing.

Ok everything clear now.

Committed? In #19 it shows it was committed, back in March 2013. Doesn't that mean it should be working in the January 2014 full release? It's not, I'm just wondering if I have to use the dev version to get this working.

@cindyr - ditto - I am finding this problem in both 7.x-1.0 and 7.x-dev

Can someone shed some light on this issue? It was "committed and closed", but I don't think the patches listed are against 7.0, they appear to be against version 8. Was anything ever provided to fix this in Drupal 7?

#26: the solution is definitely in the 7.x-1.0 version of Edit: http://drupalcode.org/project/edit.git/blob/5b286e8a91d03d6ab34b3ff9ff63....

None of this is for Drupal 8, because this problem only exists in Drupal 7, since it's related to the Drupal 7 CKEditor module!

If you still have this problem, please create a new issue (and reference this one).

No need, just set chmod 777 for sites/all/modules/ckeditor/ckeditor.config.js file.