I installed FCKeditor and somehow ended up with an old version, 2.0rc3. It caused some popups since you are activating different features now... so I went and downloaded 2.3.2.
Oddly enough, while 2.0 comes up and works (with three popup errors related to toolbar items) neither 2.3.2 nor 2.4 actually ever appears in the page. In fact, not only does fckeditor never appear, but the textbox is gone, too!
Comments
Comment #1
ontwerpwerk commented2.4 is not supported yet
2.3.2 should work, but be careful to remove every trace from the old version before installing the new version (on your site, and in your browser cache)
Comment #2
hyperlogos commentedNo, what I am saying is that 2.3.2 doesn't work. The textarea disappears and is never replaced by anything else. I actually went so far as to delete the entire module directory and re-unpack it for each version I tried (2.0rc3 worked, 2.3.2 and 2.4 both failed to ever appear.)
Right now I'm using TinyMCE but I am willing to do further testing (it's just a test site.)
The site is a totally clean install as of yesterday.
Comment #3
Jhef.Vicedo commentedIm also experiencing similar problem.. Both on 2.4 and 2.3, the editor does not appear on the custom block edit page. But I can see and use it to add/edit node content
Comment #4
ontwerpwerk commentedjhefmv24: what you're seeing might be by design, check the exclusion settings
Comment #5
hyperlogos commentedExclusion settings should make FCKeditor not appear at all, leaving the textarea alone, it shouldn't make the textarea just disappear and not be there at all, leaving a blank space in the page. I don't know if that's what's happening to him, but it's what happened to me.
Comment #6
ontwerpwerk commenteddrinkypoo: I know, but I was specifically replying to jhefmv24
Does the behaviour for you change if you select one of the other toolbar sets?
Comment #7
ontwerpwerk commenteddrinkypoo: does it work with the latest 5.x-1.x-dev version of the module and fckeditor 2.4?
Comment #8
ontwerpwerk commentedJust to be sure: You will need the module with at least revision 1.19.2.3 for fckeditor.module and 1.4.4.2 for fckeditor.config.js
Comment #9
forresto commentedI might be having the same problem with my upgrade to drupal 5.1... I have 5.x-1.x-dev and FCK 2.4 installed, and popup does nothing as in-page gives the is an iframe with the drupal "file not found" error.
Comment #10
petithomme commentedSame problem here. I've tried them all and I get the empty body. No text zone, nada. Gotta try 2.0.
Comment #11
Jhef.Vicedo commentedYes, I have the same problem with drinkypoo. The textarea is not there at all. It flashes for a while then disappear after..
Comment #12
ontwerpwerk commentedpeople, please try to debug a little more.. if the fckeditor does not show that means something is wrong - but I have no idea what might be wrong from your descriptions - please find out if all files are correctly extracted, at the right location and no javascript errors are found.
Comment #13
hyperlogos commentedall files were correctly extracted in the proper location and I got no javascript errors.
You were saying? :)
Comment #14
ontwerpwerk commenteddig deeper.. are ther 404 errors? are there hidden javascript errors (yes they may be hidden)
Comment #15
hyperlogos commentedHow would I find a hidden javascript error?
Comment #16
ontwerpwerk commentedthere are some files that are not loaded visibly for fckeditor.. and the fckeditor code catches some warnings for you - this means those errors don't show up in internet explorer warning dialogs
debugging these warnings is easier in firefox with the firebug extension where you can see more of the errors and warnings as they occur
I understand the fckeditor does not show up sometimes.. but there may be a million reasons why, I need some hints to know in which direction to look for, any error or warning message that is under the hood can help, as can examples. (Feel free to use the contact form to point me to websites where I can look at the real life examples, please don't abuse it though)
Comment #17
RubenV commentedI seem to got the same error, haven't tried 2.0 yet tough.
Firebug and the Javascript console (firefox) give me these errors:
FCKeditor is not defined
|-> var oFCKeditor_edit_body = new FCKeditor( 'edit-body' );
oFCKeditor_edit_log has no properties
|-> oFCKeditor_edit_log.ReplaceTextarea();
It seems like the FCKeditor class can't be found.
Hope it helps :-)
Comment #18
RubenV commentedIt seems I already found the solution: the problem seems to be a theme related problem. When comparing the page.tpl.php files from my theme (initially made for 4.7) with the new garland theme I found out that you need to add
print $scriptsafter
print $headprint $styleswhich will result in:
print $headprint $stylesprint $scriptsI then got an error that said that UniversalKey is an unknown item for the toolbar. This is fixed by removing it from fckeditor.conf.js tough :-) (and clear you cache)
Comment #19
wmostrey commentedThis created some confusion with me too. While the Garland theme has the $script by default, the bluemarine theme doesn't. You might want to add a line in the README.txt specifying that the following line should be place in the theme if it isn't already there:
print $scriptsComment #20
(not verified) commented