Editor does not show up in node/%/edit

Editors work fine for me. I'm using Drupal HEAD with Wysiwyg HEAD (with Overlay/Seven). Vanilla D7/Wysiwyg install, just assigned CKEditor to Filtered HTML, created a node and edited it.

Hi

Same problem as pauldawg : the editor shows up in comment form, but not in node/edit.

Drupal : 7-alpha 4
WYSIWYG 7.2.dev

Thanks...

that's crazy : the editor shows up (on node/edit form) for user 2, but not for user 1 ! my god, is user 1 not supposed to be stronger than user 2 ?! :-)

I had the same problem fo user1.. but then i did a dtabase update and now it works! (with ckeditor)

@Breakerandi, Do you remember which modules had pending database updates?

Sorry, I don't.. I'm not sure.. I think it was views.. but that couldn't be the reason?

Yeah, updating Views shouldn't have that effect.

@iko, user 1 should always be able to use the editors as it has access to all input formats. Wysiwyg itself doesn't care much which user you are (or what permissions you have), it just looks at the available input formats. If I had to guess, I'd double check that the browser cache is cleared for both users, and that their themeing is done in exactly the same way (maybe being user 1 enables adds/removes something related to the page/textarea in question).

hi,

I made some tests but still don't understand. The editor is usable (by user 1) in term's description field but not in node/edit form - whatever the content type, whatever the textarea (body or custom field), whatever the editor's theming settings (theme CSS or editor's default CSS...)... I cleared the browser's cache at least twenty times (anyway, the problem occurs within several browsers...).

Well, as a matter of fact, I don't need it right now, but that's a weird behaviour. When I understand, I'll post the answer here...

Thanks,

ps. I'm using CKeditor. I didn't test it with another one.

Firefox seems to work OK for me, but not Internet Explorer 8. Doesn't even work on Drupal Gardens.

@Scott J, that may be because IE can't handle more than 31 stylesheets. As the editor's stylesheets are loaded last, it may look as if the editor is not loaded because its files are ignored. Enabling Optimize CSS on the Performance page should fix that.

Thanks TwoD,
Yes, that half fixes my problem. Without 'Aggregate and compress CSS files' the body field doesn't even display at all, but even with it turned on, the body fields are back, but still no editor.

Actually, I've just relised that my behaviour is the same for body fields as for comments, so is not the same issue as above. Sorry, I didn't mean to hijack, so I'll start a new issue.

Hi,

Having the same problem, I installed TinyMCE and CKEditor and both of them don't show, not in body wenn editing and not in commenting body. I've tried to make new WYSIWYG profiles and also edited existed once. I tried to clear all cache, Aggregate and compress CSS files also doesn't work. I tried different roles, viewing with different browsers like Firefox, safari and chrome It just doesn't seem to display the editor...

Hope anyone has a solution...

Little addon note, in Blocks the TinyMCE does work...

Just to note, I'm having the same issue:

Editor shows up for making comments to all users
Doesn't show up to add/edit pages if I'm user 1
Editor shows up if any other user

Core Modules:

Additiona Modulesl:

I've tried running update as suggested above, but no change. Using CKEditor

Been playing around with the modules I have installed and if I turn off pathauto the editor shows up as it should.

Indeed I've also disable AutoPath and now it works for me also, only thing I'm asking myself is :
Is this a autopath or a wysiwyg API problem...

Looks like PathAuto
Source File: /sites/all/modules/pathauto/pathauto.js
Line: 6

Change
$('fieldset#edit-path', context).setSummary(function (context) {
to
$('fieldset#edit-path', context).drupalSetSummary(function (context) {

http://drupal.org/node/777082

Can you confirm?

This change worked for me also...

Thanks

So, unless anyone objects, this is a duplicate of #777082: setSummary is now drupalSetSummary?
JavaScript errors in other modules can cause script execution to halt before editors are initialized.

Thanks for the fix, worked like a charm.

I have not installed pathauto module.Still the editor is not showing for adding content.

same thing happened to me for 6.x 2.x.
I wanted to change to tinymce because of some issues with ckeditor (i wasnt using wysiwyg then). i have done some experimenting with wysiwyg+tinymce+imce+bridge as user1. i decided it was all good so removed ckeditor module and its folder. then this same thing happened. (trying to recreate what i have done but i might have forget some steps.) i can use wysiwyg with other roles (both ckeditor and tinymce with wysiwyg) but i cant use any wysiwyg editor as user1 (which has role assigned etc). (even reinstalled ckeditor, it doesnt work either.) I have done a clean install with just these 4 addons (wysiwyg+tinymce+imce+bridge) it works all fine, so maybe something dangling in database causes this?

@memedu, Roles don't matter to Wysiwyg module, only input format availability.
Check to make sure you don't also have the tinymce module installed, maybe it's enabled for some users in which case it'll interfere. If you're using a separate (custom) theme for user 1, pleasse check that it prints $closure at the end of the page template.

@slyerindu, memedu,
This issue is fixed and closed so commenting here won't make it show up in the regular queue list. I would recommend creating a new issue if this isn't related to pathauto module.
Check the console for JavaScript errors and include them in the report.

this might be related to skinr in my case. after reading your comment about themes i thought maybe skinr 2.x dev version causing some problems. switched back to 1.5 stable and it is all good. thank you for really fast response. (found a similar issue in skinr http://drupal.org/node/912440)

@TwoD thanks when I Aggregated the CSS and Javascript files that did the trick.

I have tried to read through the existing issues - but my case is a bit different - The editor does not show up at all!

I have installed it in two different sites, one a fresh install of Drupal 7 with WYSIWYG being the only additional module, and one in an upgraded version of Drupal 7 (with a few additional, existing modules - though WYSIWYG is new to this site). I have used this module on several Drupal 6 sites before and I am familiar with the install/configuration routine. On both sites I have installed CKeditor and TINYMCE - both show up as being installed correctly, I have configured the modules, created profiles for Full HTML, Filtered HTML and Plain text, added buttons, etc. I am using added themes but have also checked the problem using Garland. I have even checked to see if it appears in comments (as mentioned in a few posts above). While everything indicates that the module is working properly - it simply does not appear. I have confirmed this to be the cae in Opera, IE9 and Firefox - I'm stumped.

This issue is marked "closed (duplicate)", and since you also say your problem appears to be slightly different you should probably create a new support request.

Btw, Wysiwyg recently disabled a debug/fallback mode where editors would show their default toolbar instead of the buttons enabled under "Buttons and plugins" when no buttons had been checked. That could make it appear as if the editors aren't loaded at all.
So, if you create a new issue please enable just a few basic buttons first and look for errors in the script console. Also check if the "Disable rich-text" link is visible.

Hi,

I tried to install tinyMCE with WYSIWYG but nothing appear. I tried different version 3_3_9_3, 4beta, 4, but nothing. Of course I configured TinyMCE to display the button, etc

Then I tried with CKEditor and it showed up successfully!

Finally, I haphazardly opened my ancient IE6 and the tinyMCE appeared!

So my conclusion is the tinyMCE with WYSIWYG on Drupal 7 viewing with Firefox 3.6 or with SRWare Iron doesn't work, although it works with the same config on Drupal 6.

If anyone solved this issue, please tell me because I was so happy to definitively quite my IE6 );

I found that using fieldsets that use java script was causing my WYSIWYG to not show up. I turned off all modules except core & wysiwyg, and was still having the problem. Decided to try a new content type with a "long text" and it showed up on creation and edit. So decided to compare, and narrowed it down to the use of fieldsets in my content types. Let me know if you find a work around for this as I like fieldsets.

I just want to confirm that after optimizing CSS and javascript in performance, the issue was fixed. Thank you all.