I've installed nicEdit, openWYSIWYG, and FCKEditor. All three are installed and configurable. But when you go to create content, there's no WYSIWYG editor.

CommentFileSizeAuthor
#8 Picture 50.png219.07 KBTwelvizm
#4 Picture 48.png343.58 KBTwelvizm
#4 Picture 49.png113.64 KBTwelvizm
Picture 46.png238.98 KBTwelvizm
Picture 45.png445.82 KBTwelvizm

Comments

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Fixed

I see you're using a custom theme. The most common problem related to editors not showing up when using custom themes are outlined in the FAQ under "Q: I got it working for Garland, however, when I switch to my custom theme it says "Drupal is not defined"?.
Based on the images alone I can't determine if you also get a JavaScript error, but it's most likely you do. Please make sure the variable $closure is printed near the bottom of the page.

If that doesn't help, please reopen the issue and provide the some more info:
Have you tried with the Garland theme?
Have you tried disabling all buttons and plugins? The editor should then revert to it's default "demo" mode with all buttons enabled.
Are you getting any JavaScript errors at all? It doesn't have to be related to Wysiwyg module or the editors to stop all script execution.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Category: bug » support

Also changing to a support request unless a problem with the module itself can be identified.

Twelvizm’s picture

Twelvizm commented

Maybe I should have specified. It's not working in any default themes either.

Twelvizm’s picture

Twelvizm commented
StatusFileSize
new Picture 49.png113.64 KB
new Picture 48.png343.58 KB

Here's some updated screenshots of the create content page in Bluemarine and Garland. Still no dice.

Twelvizm’s picture

Twelvizm commented
Status: Fixed » Active

Category: Support Request, Priority: Normal, Status:Active.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Postponed (maintainer needs more info)

Which browser are you using?
Do you see any errors in the JavaScript console?

Twelvizm’s picture

Twelvizm commented

Firefox and Safari. No script errors.

Twelvizm’s picture

Twelvizm commented
Status: Postponed (maintainer needs more info) » Active
Issue tags: +Shy WYSIWYG
StatusFileSize
new Picture 50.png219.07 KB

Ok, so there is a new development. I've seen the mysterious WYSIWYG! If you make a comment on a photo (it's not visible). But, if you preview the comment without typing anything, the WYSIWYG pokes it's head out!

Does this clue help anyone to assist me with making my WYSIWYG not so shy?

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Status: Active » Postponed (maintainer needs more info)

That's interesting. I'm afraid I'm still not sure why this happens, but now there's at least a way to compare a working and a broken situation.
If you don't mind, could you PM me account details for that site, or a sandbox site which has the same problem, so I can try debugging this first-hand?

I'm specifically interested in whether the classes on the format radio buttons are all intact, as I just found out there's a problem with them not always being set right on another site. (Wysiwyg uses these to pass some state parameters per input format.)

schlitzflitzer’s picture

schlitzflitzer commented

Same error here...

The Firefox error console displays the following JavaScript error:

Fehler: WYSIWYG is not defined
Quelldatei: http://fraeulein-tussis-gratis-tipps-auf.schlitzflitzer.de/sites/all/mod...
Zeile: 38

Line 38, according to the console, reads:
var instance = WYSIWYG.config[params.field];

Similar errors occur with other editors, respectively. Their first instance in the JavaScript always seems to result in a "not defined" error...

Theme is Garland - rather fresh install. Editors are being detected and can be configured but don't show up in the text area...

Wysiwyg is 6.x-2.0 dev

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

Openwysiwyg is currently broken: see #713942: OpenWYSIWYG broken, jWysiwyg needs jQuery 1.3+. Having an input format with it enabled may halt all other script execution, preventing other editors from loading.

schlitzflitzer’s picture

schlitzflitzer commented

So that was a bad choice :-)

I had made an attempt at openwysiwyg after the earlier, similar looking tinyMCE error (with no other editor installed):

Fehler: tinyMCE is not defined
Quelldatei: http://fraeulein-tussis-gratis-tipps-auf.schlitzflitzer.de/sites/all/mod...
Zeile: 74
var instance = tinyMCE.get(params.field);

I'll rebuild my installation to see if I may have goofed somewhere else...

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Version: 6.x-2.x-dev » 6.x-2.0
Status: Postponed (maintainer needs more info) » Fixed

Please update to the latest stable.

Status: Fixed » Closed (fixed)

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

anawillem’s picture

anawillem commented
Version: 6.x-2.0 » 6.x-2.4
Priority: Normal » Major
Status: Closed (fixed) » Active

I am still having this issue in 6.x-2.4. Any suggestions?

twod’s picture

twod
Primary language Swedish
Location Sweden
commented
Version: 6.x-2.4 » 7.x-2.0
Priority: Major » Normal
Status: Active » Closed (fixed)

@anawillem, It's a bit difficult to know exactly which problem you are having since this issue contains a number of them.
Please open a new issue and answer these questions:

Is the editor listed as installed, with a version number, in the "Installation Instructions" below the list of input formats and editor profiles?
Are you using a custom theme? If so, does it work with the Garland theme?
Do you see any JavaScript errors in the browser?
Which browsers have you tested with? Same problem in all of them?
Which editors have you tested with?