I have OpenPublic profile installed with wysiwyg module 7.2.4.

I have CKEditor version 4.6.2.20af917 installed in "sites/all/libraries/ckeditor"

The wysiwyg module is 7.x-2.4 and all settings for the Full HTML profile are configured, including "Full HTML" for the CKEditor.
The javascript is engaged accoring to the console log.

The CKEditor toolbar does not show up in local Acquia DevDesktop on Windows 7 although it DOES show up on a server Acquia Dev site from which the local site was updated. This is extremely aggravating, since all of the settings seem to be correct.

Disable/Enable Rich-Text shows at the bottom of the text area box. So the CKEditor javascript is being loaded.

I am inclined to think that OpenPublic has done something to destroy the ability of the CKEditor to display on the page . . . like implementing panels maybe?

It toggles between raw HTML and a BLANK text area. HTML display does not show in the Text Area and there is never any WYSIWYG CKEditor toolbar visible.

I am recommending that CKEditor be trashed. None of the online documentation supplies any explanation for the behavior (CKEditor toolbar javascript fails to properly integrate with Drupal 7 textareas).

I suggest that our team try another WYSIWYG editor and just forget about CKEditor from here on out. CKEditor works in Drupal 8.x core, but it is miserable and completely unreliable in Drupal 7.x.

CommentFileSizeAuthor
#5 ckeditor_styles-n2888639-5.patch1.21 KBDamienMcKenna
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

pkosenko created an issue. See original summary.

AlbionBrown’s picture

CKEditor been reliable for me up to now. But this sounds like the same issue I have. Creating a new filter format profile works but isn't a good solution. No logged errors or anything in console output.

AlbionBrown’s picture

Going into the WYSIWYG text profile, checking the "Show enable/disable rich text toggle link" option and saving makes it the editor appear when you then enable rich text on the text area you're using CKEditor with.

AlbionBrown’s picture

Credit to chumkui for that find

DamienMcKenna’s picture

Status: Active » Needs review
FileSize
1.21 KB

This appears to solve the problem for me.

DamienMcKenna’s picture

Status: Needs review » Active

Sorry, wrong issue X-)

Schreck Anne’s picture

Hello.
I installed the latest (june 2018) Wysiwyg module (with Drupal 7) and CkEditor library but had no toolbar...I went quite crazy trying to figure out what was wrong.
I found a solution on an other website : it appears that this module isn't compatible with jQuery 1.10...
So I went into Configuration/development/JQuery update and I choose jQuery 1.8...And it was magic...I had a nice toolbar !
I hope this can help others...

DamienMcKenna’s picture

For my scenario it turned out to be caused by the Footnotes module, see {#1589130] for details.

TwoD’s picture

Status: Active » Closed (cannot reproduce)
Issue tags: -ckeditor

I don't have and environment with Windows 7, Acquia DevDesktop to test with so I can't say if that changes anything (I doubt Win 7 itself is the problem, more likely the browser being used in it if it's an older IE).

I had a quick look at OpenPublic's 7-x-1.x branch just now and their Wysiwyg integration does a few odd things. Their hook_install() implementation directly writes to the {wysiwyg} table using an old settings structure.
They also forcibly set CKEditor to use the 'kama' skin in hook_wysiwyg_editor_settings_alter(), and hardcodes its path to sites/all/libraries/ckeditor/skins/kama/,
but CKEditor no longer ships with Kama included.
Both these changes could very well be responsible for CKEditor failing to load.

I am not exactly sure why the workaround mentioned by @joshbrown81 works, but saving a profile would flush Wysiwyg's cache and it re-builds the editor settings/preferences structure put into the databse. Should not matter which setting is toggled though.

As far as other possible causes go I am thinking this could somehow be a cache/JS-aggregation related issue. The only times I've been unable to get editors to show up when properly configured, their scripts have not been properly aggregated and are thus missing from the page completely.
The Advanced CSS/JS Aggreggation has been know to - at least in earlier versions, mess with the order in scripts were added, and sometimes miss aggregating them completely. A colleague encountered the opposite of that problem (scripts got added multiple times when loaded over AJAX) a while ago but that was fixed in #2956697: ajaxPageState settings are incorrectly removed..

@Schreck Anne, I have tested Wysiwyg itself with jQuery 1.10 and it works fine. Some specific editors may have problems with 1.10 but CKEditor should not be one of them. If you are able to reproduce that issue please look for errors in the browser's JavaScript console and post them in a separate issue.

Closing this as "Can't reproduce" for now. Please re-open if you can get the same problem when the OpenPublic issues are fixed.

10thstreetlabel’s picture

I have the Windows 7, Acquia DevDesktop environment and I disabled the advanced editor and wasn't able to enable it again but I set up custom editor and came to the conclusion that when I was putting buttons on it and when the buttons went it to the 2nd line on the TOOLBAR CONFIGURATION page the entire toolbar would not show up. I think it is around 28 buttons on the selection page. I not sure if this helps or not. Upon further testing some of the buttons were not installed properly so please disregard.

alexmoreno’s picture

Be careful if you are aggressively caching javascript (hello Google), or using advagg modifiers, as this could be breaking the toolbar or just making it dissapear.

/admin/config/development/performance/advagg/mod