Closed (fixed)
Project:
Wysiwyg
Version:
7.x-2.x-dev
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
31 Jan 2012 at 07:06 UTC
Updated:
22 Oct 2012 at 11:21 UTC
I have ckeditor3.6.2-1, imce 7.x-1.5, and the wysiwyg stated above. I had no problem uploading the image as well as saving it but when I went to the actual page not only was there no image but none of the changes made to the content of the page was saved. It is that way in the preview as well. What needs to be add/changed to get this fixed.
Comments
Comment #1
economy commentedSame issue here! Totally baffled by this one.
Comment #2
dczepierga commented@luluwan, u're using WYSIWYG module or CKEditor module?
Greetings
Comment #3
Oshun commentedHello,
I have this issue as well, but I am on Drupal 7.15. I keep getting the message that Drupal just encountered an error when I try to preview. I am using WYSIWYG.
Comment #4
dczepierga commentedI move this issue to WYSIWYG module.
It's not realted with CKEditor module.
Greetings
Comment #5
twodThis can happen if there are any JavaScript errors on the page when the form is submitted. Any error can cause the browser to stop all script execution, which prevents the editor from syncing its contents back to the original textarea to be submitted.
Please open the browser's JavaScript console (F12 in IE, Ctrl+Shift+J or Ctrl+Shift+I in others) and look for any errors.
If they are related to Wysiwyg or the editor itself, they could also happen if you click "Disable rich-text" below the editor. That also syncs the contents back to the original textarea. If saving the form after disabling the editor works as expected, it's likely the error happens while the form is in the process of being submitted, which narrows it down a bit.
Please also write down any module you have which either adds a lot of scripts to the edit forms or alters them a lot. Remember to disable any JavaScript optimization/minification in Drupal before checking for errors or we won't get the correct filenames or line numbers needed for debugging.
Comment #6
Oshun commentedThank you TwoD.
I will try this...
Now when you say disable any JavaScript optimization/minimization in Drupal - how do I do this? I dont recall ever having checked anything pertaining to this.
Thanks again..
Comment #7
Oshun commentedHello TwoD
I went to my site and tried to preview two posts that I saved. I got an error message that Drupal encountered an unexpected error and I couldn't preview the pages as usual.
I did like you said except it is (command+shift+J or I) on a MAC to see the errors. Now I don't know if this is right or not as I don't know how to disable the optimization for Java, but I did see a lot of warnings in yellow and about 2 errors in red.
These are the errors in red:
Error: this.getEditor(n) is null
Source File: http://mysite.com/sites/default/files/js/js_pdM_lDsI7KH1B4yotYkOttt9mkHp...
Line: 1036
Error: this.getEditor(n) is null
Source File: http://mysite.com/sites/default/filesjs/js_5v6CgszWXW4ufplNA_doYk6tLHbRE...
Line: 600
Here is an example of one of the many warnings:
Warning: Unknown property 'zoom'. Declaration dropped.
Source File: http://mysite.com/sites/default/filescss/css__9zsakYbWSOTLroLLtWO9P7zLJX...
Line: 1
Comment #8
Oshun commentedI think I will disable the module and see what happens.
Comment #9
twodThe optimization settings can be found in the Configuration->Performace section. It does look like these have been enabled as the script files are being served from sites/default/files/js and have random looking names.
The warnings are from the stylesheets and won't affect the scripts.
Comment #10
Oshun commentedI checked and the java optimization box was checked. I also disabled the plugin and I am still getting the error.
Comment #11
twodThe line numbers and filenames shown in the error messages should have changed now, showing where the error actually occurs. Could you please post the messages again?
Which plugin did you disable?
Comment #12
Oshun commentedHi TwoD
I temporarily disabled the WYSIWYG module and it didn't changed anything so I enabled it again.
This is the message I got this time:
Error: this.getEditor(n) is null
Source File: http://mysite.com/sites/default/files/js/js_5v6CgszWXW4ufplNA_doYk6tLHbR...
Line: 600
Comment #13
twodLooks like the JavaScript optimization is still active, since the filename has a hash value in it instead of looking somehting like http://mysite.com/sites/all/libraries/ckeditor/ckeditor.js.
If you disabled Wysiwyg and the error was still there, it's not from Wysiwyg module, unless some old version of the scripts has gotten stuck in your browser cache or Drupal's cache.
Btw, I searched through all our editor implementations and the editor libraries for the string 'getEditor(' and I can only find it in the openWYSIWYG editor.
If this error was still present after disabling Wysiwyg, my best guess is that you also have the openWYSIWYG Editor module enabled. Wysiwyg module is not compatible with other editor modules since they try to do the same thing, and should never be used together.
Btw, the openWYSIWYG editor library has not been updated in years and won't work in several browsers (including Chrome).
Comment #14
Oshun commentedThank you for that response. I do have openWYSIWYG editor! I guess I need to change it.
Comment #15
twodOk, I'll close the support request then.