When I add a content, CKEditor is fine. It works well and save the content exactly as it is being entered. Now when I try to edit that node or any random existing node, the textarea of CKEditor no longer contains the content entered while it's being added but contains an entire page of a particular page from my Drupal site. The weird thing is that, some existing nodes works correctly on edit mode? I've tried adding just a simple content e.g. "this is a very plain content" but still the problem persists. Anyone experienced this too?

Comments

Mark Vincent Verallo’s picture

Please share your thoughts.

nelson_carvalho’s picture

i have the same problem... but in my case it seems that he contais the html from the location of the chEditor to the end of page including script, etc.

Anyone knows whats happening?
And better yet, any solution?

Mark Vincent Verallo’s picture

I have this same issue. I've been struggling on this the entire day and even since the previous days. Up until now, I haven't known a concrete solution to this. I have a feeling that some module might be conflicting with ckeditor. So I am in the process of mirroring my site and then, disable one by one the modules in the copied site until the issue is fixed. If any of you already have solved this issue, please share the solution here..

Mark Vincent Verallo’s picture

I have this same issue. I've been struggling on this the entire day and even since the previous days. Up until now, I haven't known a concrete solution to this. I have a feeling that some module might be conflicting with ckeditor. So I am in the process of mirroring my site and then, disable one by one the modules in the copied site until the issue is fixed. If any of you already have solved this issue, please share the solution here..

Mark Vincent Verallo’s picture

I've solved this issue. I don't know if this is also your case. But try this. Do you have search module enabled? Try disabling it.

Beulette’s picture

Had the problem several times. Maybe it's not a CKEditor issue, it happened because an AJAX request returned an error.
I've no concrete example right now because I haven't seen this problem for months, but this was a common problem when some of my custom modules used to write things or errors on page displays.

I just had to track the error which was kind of an HTTP header problem...

Whatever, problem in many cases is due to conflict with a custom of contrib module.

Mark Vincent Verallo’s picture

It could be that a custom module is the culprit, yes. But in my case, I really tried to prove if the search module is the problem by enabling it back. When it's enabled, the problem returns. And to think search is a core module right?

bluenile1999’s picture

In my case this problem was solved by disabling the extensions in google chrome.

Jonas Bärtsch’s picture

Disabling the search module fixed it for me.

sandboxpl’s picture

Same here, #5 helps,
tested on versions 7.x-1.12, and current dev release.

wwalc’s picture

Does the ajax callback to filter/xss return the whole page once the search module is enabled? Check ajax calls in Firebug.

It still will not explain anything (why the search module breaks this ajax call), but at least the problem will be identified in this particular place.

dymale’s picture

Version: 7.x-1.9 » 7.x-1.13

I have the same problem.
I got D7.22, CKEditor 7x-1.13 and JS CKEditor 4.1.1
By disabling of search module I have returned site back to normal.

steveaz98’s picture

I have the same issue, displaying login page in ckeditor. Disabling search resolved the issue, but would like to know the root cause.

Drupal 7.22
CKEditor 3.6.6.1

Martin Schauer’s picture

The problem most likely lies within the search-module's cronjob to index the page. This cronjob kind of views the nodes it wants to index. If you use hook_node_view() anywhere in your modules and the cron-user gets an error or gets lead anywhere by a drupal_goto(), the behaviour you described is the result.

Solution: Disable the search-module if you don't need it. If you need it though, check the $view_mode in your hook_node_view()-implementations. If it says "search_index", no redirects should be made. (the easiest way is to just return $node if $view_mode == "search_index")

sandboxpl’s picture

Ok, solution with disabling search module was good, but now i've needed search-box working, so i've made a research and found another thing.

In my case the problem was Plugin for inserting drupal teaser and page breaks. I've had this plugin switched off, but button "DrupalBreak" was added to Used button list.

My solution:

  1. Go to CKEditor profile settings page at '/admin/config/content/ckeditor/edit/[profile_name]'
  2. Switch of "Plugin for inserting Drupal teaser and page breaks" in appearance settings.
  3. Make sure, that "DrupalBreak" button is not in use.

Please, reproduce this steps at your instalations, and let me know if this solution works for you ;-).

eidoscom’s picture

I disabled the search module and then enabled again and for me the problem sloved :))

Martin Schauer’s picture

@eidoscom: Your problem is probably only solved until Drupal needs to index content of the error-producing content-type for its search the next time (via cron).

jillh68’s picture

Under CKEditor's Global Profile, setting the Use Toolbar Drag & Drop feature to Disabled worked for me.

GiorgosK’s picture

Issue summary: View changes

search module is not the problem (at least for me)

#18 disabling toolbar drag and drop did not work

#15 worked disable the drupal teaser plugin from each profile that uses it (by default the FULL HTML)

webmestre’s picture

Hello,

- disabling search module => not working
- disabling drag and drop => not working
- disabling drupal teaser => not working

Any adea ?

== edit ==
A PHP code was used in 2 themes and was responsible for a conflict.
All is OK now.

CKEDITOR is NOT responsible about this issue !!!

GiorgosK’s picture

@webmestre
which themes where responsible
what files ?
what code ?

please post most details about your findings to help someone else fix this once and for all

webmestre’s picture

@GiorgosK

we are trying to clean the code. I'll be back with news as soon as possible to explain what produced the issue.

Ignigena’s picture

I am experiencing a similar issue in which it appears that the nodes CKEditor is breaking on is happening due to the /ckeditor/xss POST request being made to the root of the site "/" instead. For example, here's what it should be doing on a node that works without loading my site in the preview box:

POST /ckeditor/xss HTTP/1.1
Host: dev.com
Connection: keep-alive
Content-Length: 8567
Pragma: no-cache
Cache-Control: no-cache
Accept: /
Origin: http://dev.com
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Content-Type: application/x-www-form-urlencoded
Referer: http://dev.com/node/48/edit?destination=admin/content

And this is what it looks like for nodes that I see my entire site loading in the CKEditor form:

POST / HTTP/1.1
Host: dev.com
Connection: keep-alive
Pragma: no-cache
Cache-Control: no-cache
Accept: */*
X-Requested-With: XMLHttpRequest
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.95 Safari/537.36
Referer: http://dev.com/node/240/edit?destination=admin/content

Both requests are obviously the XSS request since the headers have text, input_format and token headers present.

I am observing this using the latest version of CKEditor module and JS library (from the CDN)

cyberitch’s picture

Hi all,
I did a copy of my LIVE web site into our DEV server, and now I have this issue, but its not in the LIVE.
I did the cope again, just to make sure, and still there.
Anyone found the real source of that issue?

I tried all the proposed solution and none worked.

Thank you.

jn2’s picture

About 6 months ago, I had a similar issue. CKeditor had been working fine one day, then did this the next. In that case, it was a server setting, and the host support fixed it.

cyberitch’s picture

Any idea what settings they changed?

I'm on a shared hosting, but I doubt they will troubleshoot my Drupal if I can't provide some sort of explanation on the conflict or settings to adjust.

Thanks.

jn2’s picture

Sorry, no. They knew what it was because they had just done it, said they knew it affected Wordpress, but didn't know it affected Drupal. It was shared hosting, and they did say it was some kind of security setting.

tce’s picture

Had this issue, the problem was due to a strict ModSecurity rule (973343) after I'd had some server hardening done.

mvnovick’s picture

In my case, disabling the search module works, but I really need it on my site. Disabling the search module and then enabling it back also fixes the issue, but in about a day or so CKEditor again starts to load the homepage instead of the content it should be loading.

The fix that actually worked for me was hacking the CKEditor module by adding exit at the end of the ckeditor_filter_xss() function in the ckeditor/includes/ckeditor.page.inc file.

scotwith1t’s picture

We encountered the same thing. Disabling the core search module corrected it, and upon re-enabling it the error was not immediately there. But as #29 said, I believe it will come back...we will keep an eye on it and hope for one of the maintainers to chime in with a theory on why this might be? Not sure if it makes any difference, but we also initially had the custom_search and search404 modules enabled. Search404 is still enabled but custom_search is now disabled.

itsnadeem’s picture

Most probably if this issues raises search cron job wont run due to error in some node.

zkrebs’s picture

I updated my server from Ubuntu 12.04 Apache to Ubuntu 14.04 and also upgraded Drupal to 7.53 and this issue just started for us. Ideas?

NancyDru’s picture

We were having this problem, so I disabled Search. I also disabled the plug-ins mentioned above. I have modified all my custom modules to avoid doing things when view-mode is "search_index" or $_GET['q'] == 'cron.php'. The problem is still happening.

EDIT: This may have been residual junk. I have updated all the nodes and am not seeing it any more.