I'm using Drupal 6.1, with the latest stable releases of both the editor itself and the module... I'm also using it on a 5.7 installation, and it works flawlessly. Yet, for some reason, it doesn't seem to show up in 6.1. I thought it might be my theme that was doing this, so I tested it with Garland, and I still have the same problem. ... Is it a common 6.1 issue?

Comments

wwalc’s picture

Check your profile and the global profile, maybe you have accidentally set exclude/include mode to "include", leaving all fields empty.

Another thing you may want to try is to uninstall 6.x-1.1, download 6.x-1.x-dev and install it. Let me know if installing 6.x-1.x-dev solved your problem.
(btw. you did uploaded FCKeditor (the editor itself) into modules/fckeditor/fckeditor directory, right?)

pobster’s picture

Priority: Normal » Critical

Can I just check that you're having the same issue as I am, is the problem specific to comments? It seems to enable fine for all node types, but fail on comments with an actual browser error of;

'val[].length' is null or not an object

I'm *sure* this didn't happen in the previous release - am wondering if it's cropped up due to the fix on fckeditor.module 1.20.2.19 - fckeditor + drupal teaser break. Obviously comments aren't built the same way as nodes so the val[].length would be null...? It makes perfect sense?

Pobster

chuckyrose’s picture

Version: 6.x-1.2 » 6.x-1.1

I can confirm pobster's problem on my installation too. When I downgraded back to the 1.1 release, the editer shows up again in the comments no problem. I am going change this to be listed as a bug in the 1.2 branch if that's ok.

It appears that the teaser-break fix affects how the editor shows up in comments. Pobster's comment seems correct, but I'm not one of the coders so I don't know. It showed up fine for creating nodes, but when trying to use it in the comments section, it would show me a tiny comments area with the same script error as pobster.

Chuckyrose

chuckyrose’s picture

Version: 6.x-1.1 » 6.x-1.2
wwalc’s picture

Version: 6.x-1.1 » 6.x-1.2

Check the latest relese: 6.x-1.2-1 (hopefully it works this time).

wwalc’s picture

Status: Active » Fixed
Anonymous’s picture

Status: Fixed » Closed (fixed)

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