Active
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 May 2013 at 16:01 UTC
Updated:
8 Jan 2014 at 21:46 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
saltednutComment #2
wim leersThe Drupal 8 backport (#2111667: Backport Drupal 8's Edit module to Drupal 7) might have fixed this. Can you please test again?
Comment #3
wim leersI can't reproduce *this*, but there's definitely something going wrong: the Media Filter's CKEditor integration doesn't appear to work when CKEditor is being used in inline mode.
Edit knows the type of the filter, and the CKEditor in-place editor's request to the server to retrieve the unfiltered version so the user can start in-place editing it succeeds, with the correct response. CKEditor's in-place editor correctly loads CKEditor plugins, including the
mediaCKEditor plugin, so that's also not the problem. Hence the problem lies with the Media plugin for CKEditor: it works fine on the full node form (where CKEditor is in iframe mode), but it fails while in-place editing (where CKEditor is in inline mode).Happens both with "pre beta 1" aka "ancient" Edit and with RC1: see attached screenshots.
Comment #4
saltednut'Curate' is an incorrect queue for this issue to be moved to it is not something that would be isolated to just sites using 'Curate' to manage their CKEditor/Edit/Media config.
This issue should be moved to the CKEditor module queue, in my opinion. (Though some might argue the problem belongs to the Media modue.)
It certainly should not be tracked for a single distribution.
Comment #5
wim leersIt's possible that it's a Curate-induced problem — however unlikely. That's why I felt it more appropriate that it lived in Curate, until you determined the exact module that causes the problem.
Since this integration between CKEditor and Media indeed seems to be provided by the CKEditor module (as per #1504696: Integration with CKEditor module), this appears to be the appropriate issue queue indeed.
Comment #6
saltednut