Do the following steps to reproduce.

1. Have 2 content filters, one with a wysiwyg editor, one without. The one without should be the default one
2. go to /node/add/page
3. You should not see the WYSIWYG editor OOTB. Now click on the content filter and select the WYSIWYG one
4. The editor should show up
5. Now Press F5
6. The editor is dissapperd. In my content filters no content filter is active anymore
7. Click on the WYSIWYG content filter and you get the error below. The editor wont load anymore

Drupal.wysiwyg.instances[params.field] is undefined

stacktrace

anonymous(Document page, Object format=format2 editor=fckeditor field=edit-body)wysiwyg.js?1 (Zeile 128)
anonymous()wysiwyg.js?1 (Zeile 58)
anonymous(Object originalEvent=Event change type=change)jquery.min.js?1 (Zeile 19)
anonymous()jquery.min.js?1 (Zeile 19)
[Break on this error] var editor = Drupal.wysiwyg.instances[params.field].editor;\n

Comments

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

Which browser does this happen in?
I have 3+ input formats on my dev site, only "Full HTML" currently has an editor (FCKeditor).
I can reproduce this up to step 6. In my case the PHP format is selected (num 3, where 2 was selected before refresh).
FCkeditor sometimes complains about our custom toolbar being missing on page load, but it can be re-enabled by switching format.
I am not able to reproduce this if I use Web Developer toolbar to disable caching. Then it jumps back to the first and default format without any editor being loaded.
It's 5:30 am here so I'm not going to try to debug this until after getting some more sleep...

eugenmayer’s picture

eugenmayer commented

Well iam on a FF 3.5, Ubuntu (64bit).

I have the Webdev bar enabled, with a disabled cache.

BUT: I have jquery_update *dev (jquery 1.3.x) and jquery_ui 1.7.x.

Iam using a clean D6.15. I will try to reproduce it on other Drupal installtion (from scratch) with a other browser and on my other client using FF.

Also it could be related to http://drupal.org/project/wysiwyg_imageupload as its activated. Maybe the bootstrap explodes somehow?

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

I was testing on FF 3.5.7 on Win XP, I'll try this on my Ubuntu machine later.
This is a bit strange as I have not seen this bug before and I have no clue as to why it happens. Since it's a new node form, it should reset everything back to the defaults when reloading, but it looks like that doesn't happen.

Btw, I am using Firebug with a JavaScript syntax highlighter plugin and I lost the highlighting yesterday. Firebug itself has also been acting very weird when debugging scripts. Sometimes I'm no longer able to read or access variables which should be in the scope chain regardless of if I'm actually debugging or not, that of course kills scripts which try to use those variables. I could only fix it by enabling and clearing the cache again.
I'll try disabling Firebug completely and see if that might be interfering.

I am not using wysiwyg_imageupload so that is not the cause.

twod’s picture

twod
Primary language Swedish
Location Sweden
commented

My Firebug problems were unrelated. (Btw, don't upgrade to Firebug 1.5 on Ubuntu if you're running their 64bit custom build. Firebug will instantly crash Firefox when opened. Mozilla doesn't support 64bit so they won't fix it and Ubuntu's fix in 3.5.8 isn't released yet.)

I found this bug report https://bugzilla.mozilla.org/show_bug.cgi?id=394782 and a great article explaining it http://www.ryancramer.com/journal/entries/radio_buttons_firefox/.

This bug happens because the number of form elements don't match after the page has reloaded if there's no editor enabled.

Looks like we have to turn off autocompletion for the form to completely get rid of this...

eugenmayer’s picture

eugenmayer commented

Ah yes, well that firebug bug was known for me, exactly using the comintation Ubuntu , FF 3.5.7 and 64bit. Anyway thanks for the hint

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: When you reload a /node/add/XXXX page, the editor fails to load if not the default content filter is WYSIWYG enabled » Firefox: Editor fails load to when reloading a form with enabled editor
Priority: Normal » Minor

All we can and will do here at max, is to prevent any JS errors upon reload, if there are any that can be replicated at all.

eugenmayer’s picture

eugenmayer commented

Sun actually i cant reproduce it anymore myself. The steps i decribed where completely reproduceable..after installing and removing some modules of any type...the error dissapeared.

For me i mark this one as a "broken due development frickeling". So for me, that one can be closed, if you agree.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Closed (won't fix)

hah! Happy to do that ;)