I am using Footnotes with WYSIWYG (7.x-2.1) and CKEditor (3.6.3.7474). When I activate the Footnotes Wysiwyg and then activate the footnotes button in the WYSIWYG configuration I lose my editor window. Instead I get a blank space on the page where the editor should be. When I deactivate the footnote button in the WYSIWYG configuration, I again get the WYSIWYG CKEditor window with an appropriate button bar. The behavior toggles on and off by checking/unchecking the button in the WYSIWYG button configuration settings.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

GuyB’s picture

I have the same issue using a slightly older version of CKEditor (3.6.2.7275).

erald’s picture

same with CKEditor 3.6.0.6902

auraell’s picture

same with CKEditor 3.5.2.6450

gsquirrel’s picture

I think this is a duplicate of http://drupal.org/node/1333748 - I found upgrading to the dev version got things working.

GuyB’s picture

The dev version works for me. Thanks gsquirrel.

rossb89’s picture

For anyone who has been having javascript errors with footnotes and CKeditor v4.0 onwards (presumably). More specifically, the error "Uncaught TypeError: Object [object Object] has no method 'addCss' "

This causes footnotes_wysiwyg module to 'wipe out editor window' again -This patch against 7.x-2.x-dev fixes the error.

It's only 1 line of javascript in the plugin.js that needed changing; line 26 - changed
editor.addCss(
to
CKEDITOR.addCss(.

kiwad’s picture

Priority: Normal » Major

Footnote 7.x-2.x-dev + CKEditor 4.0.1

Patch in #6 does provide the solution to a bug that makes footnotes otherwise unusable

bruitism’s picture

Status: Needs review » Reviewed & tested by the community

I can confirm that patch #6 works with 4.0.1.d02739be4b as well.

pyrojonc’s picture

I have footnotes-7.x-2.5 and CKEditor 4.1.1. I am having this issue and the patch does not work for me. Wysiwyg editor works fine when footnotes_wysiwyg module is disabled, but the text editor does not show up when it is enabled.

dtrees’s picture

This patch does not work for me either. I am using CKEditor 4.0.1.1.270438, i've tried both the dev and footnotes-7.x-2.5 versions. I've double checked that changes were made to plugin.js via the patch and the WYWIYG editor window is still wiped out. Any help in troubleshooting this is greatly appreciated. Thanks

pjcdawkins’s picture

The patch in #6 works for me. @pyrojonc and @dtrees, did you clear Drupal and your browser caches?

R.Muilwijk’s picture

This issue might be interesting for you #2025027: Add support for ckeditor 4.x

jrao’s picture

Yes, patch in #6 works, will need to clear browser cache for it to take effect.

jrao’s picture

Issue summary: View changes

Clarification

JThan’s picture

Version: 7.x-2.5 » 7.x-2.x-dev
Issue summary: View changes

Patch in #6 worked for me instantly. Thanks.

Have the latest dev Versions of WYSIWYG and Footnote. CKEDITOR 4.3.1 without (sic!) the patch from here https://drupal.org/node/2025027

WillowDigit’s picture

I can confirm that #14 works.

I have also found out that dropping the jQuery down from 1.10 to 1.8 solves the problem for me and I am now able to use it with the ckeditor module (foregoing wysiwyg)

ecat’s picture

I'm having trouble with this. I've been using the dev version of Footnotes (7.x-2.5+7-dev). I have applied the patch in #6 (manually changed line 26). I've tried WYSIWYG with ckeditor 3.3.1, 3.6.6, and 4.4.2. I've cleared my cache at Configuration > Performance > Clear cache every time, and also cleared my browser's cache. Also tried the latest version of the CKEditor module (7.x-1.14). No matter what, I still get a blank space under "Body" when the footnotes wysiwyg button is turned on (everything works fine when it's turned off). Any ideas much appreciated.

fonant’s picture

Footnotes works fine for me if I use:

  • WYSIWYG 7.x-2.2
  • Footnotes Wysiwyg 7.x-2.5+7-dev
  • CKeditor library 3.6.6.1 (latest version supported by WYSIWYG)
  • jQuery 1.4.4 (Drupal 7 core version)

Any chance the current DEV release could be made an official 7.x-2.6 version?

andersju’s picture

Works for me when using WYSIWYG 7.x-2.2+46-dev, Footnotes Wysiwyg 7.x-2.5+7-dev, CKEditor 4.4.5.25cdcad (latest right now), jQuery 1.7 (jquery_update setting for admin pages), and the patch from #6.

GiorgosK’s picture

for wysiwyg (with ckeditor plugin) there was no need for this patch
for ckeditor module even this patch did not work

GiorgosK’s picture

spoke too soon
its not working with or without the patch, it was working for a while (don't know why)
tried clearing cache, and changing to jquery 1.4 (default for drupal 7)
but it does not seem to work

maybe it conflicts with something some other module

pifagor’s picture

Status: Reviewed & tested by the community » Closed (outdated)
tky’s picture

Version: 7.x-2.x-dev » 7.x-3.1
Status: Closed (outdated) » Active

I have enabled modules in below:

  • footnotes_wysiwyg 7.x-3.1
  • ckeditor module 7.x-1.18
  • Ckeditor 8.0 (via //cdn.ckeditor.com/4.8.0/full-all)

The editor toolbar and input area were wiped out, unless I unchecked the "Add footnote" option in Plugins of ckeditor profile setting.

I have changed the ckeditor version by modified the version number in CDN, but no luck at all. Have to disable this pluging to make ckeditor functioning.

Proteo’s picture

For newcomers:

The patch from #6 works just fine with the following combination:

Footnotes & Footnotes Wysiwyg 7.x-3.1
Wysiwyg 7.x-2.5
CKEditor (library) 4.9.2

Apply the patch and flush caches, done. Works fine with jQuery 1.10, no need to touch that.

DamienMcKenna’s picture

Version: 7.x-3.1 » 7.x-3.x-dev
Status: Active » Reviewed & tested by the community

Agreed, this problem could still happen with the latest release.

pifagor’s picture

  • pifagor committed 0ed2996 on 7.x-2.x authored by rossb89
    Issue #1589130 by rossb89, pifagor, tky, Proteo, DamienMcKenna:...

  • pifagor committed d9a9f9d on 7.x-3.x authored by rossb89
    Issue #1589130 by rossb89, pifagor, tky, Proteo, DamienMcKenna:...
pifagor’s picture

Status: Reviewed & tested by the community » Fixed

Done

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.