Closed (fixed)
Project:
FCKeditor - WYSIWYG HTML editor
Version:
6.x-1.2-1
Component:
User interface
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
6 Apr 2008 at 23:40 UTC
Updated:
12 Oct 2018 at 22:11 UTC
Comments
Comment #1
avb commentedSame problem at my site (using drupal 6.1.).
I tried nearly all possible combinations of profiles and rights but the editor doesn't showing up.
Comment #2
giorgoskdid you enable a profile and assigned it to a role ??
are you trying to edit with a user of that role ??
I think you should provide more information if you have done the previous ...
Comment #3
avb commentedfound the problem. it was theme-related. the custom theme had no
print $closureat the end. added it and now fckeditor works fine.Comment #4
john.karahalis commentedI was using the -dev branch of FCKeditor on Drupal 6 and it was working fine. After upgrading to the final release, FCKeditor is not displayed. I did not change my theme (burnt) any time near the upgrade, so I don't see how this can be a purely theme-related issue.
I did not try o0avb0o's fix because I do not know where to apply it. As I said, it seems that this is not (at least not completely) a theme issue, and is at least partly a major bug of FCKeditor.
Comment #5
wwalc commentedJohn Karahalis:
A couple of questions:
- Did you upgrade/install any other modules at the same time?
- Did you upgrade to 6.x-1.2-1? (6.x-1.2 had a very ugly bug).
- Does switching to Garland theme solve this issue?
- Are FCKeditor profiles assigned to the correct Drupal roles?
- If you go to admin/settings/fckeditor, does any error message appear?
Comment #6
john.karahalis commentedThank you for the response.
-I likely did upgrade/install other modules at the same time. It's hard for me to remember which, since our site has been changing rapidly.
-Yes, I'm running 6.x-1.2-1
-Switching to Garland does not fix the issue
-Yes the permissions are set correctly
-No error message on the settings page
I did, though, upgrade FCKeditor from -dev to the final release in a strange way (I didn't know Drupal automated the update process). I disabled the module, removed the sites/all/fckeditor folder, and then reinstalled it. I have been doing this for most of the modules I use and it has never caused any problems before.
Comment #7
john.karahalis commentedI un/re-installed FCKeditor several times to no avail. I even un/re-installed from each of my sites (I'm running multisite) but that did not work either. As I said before, I am using the theme burnt and did not have this problem with the development versions of FCKeditor for Drupal 6.
Comment #8
ddease2 commentedI had the same problem with FCEditor not working. I took the advice above and changed to Garland, and it does work with that theme. I am using the META Theme, which is obviously the problem. Can anyone direct me to a fix for this theme so I can have them both?
Thanks!
Comment #9
xgmorkx commented$enclosure did it for me too.
Maybe a good idea to add in the Readme?
Comment #10
wwalc commentedThere is another thing to check, this was the problem that John Karahalis had (thanks for letting me check that).
When upgrading from earlier versions of FCKeditor module, make sure that all roles with "access fckeditor" permissions are assigned to at least one FCKeditor profile.
Comment #11
Jorrit commentedComment #12
moisesc commentedHow to I update the customer theme? Where exactly can I put this "
print $enclosure"? My FCKeditor was working and after creating a blog with an embedid video it stop working. I am not sure where to start looking for this "print $enclosure"...please help....