WYSIWYG Not Working?

dannyboy
(@dannyboy)

17 years, 3 months ago

Hey everybody-

I just upgraded to 2.1 (which, by the way, is fabulous!).

The only problem I’m having is with my WYSIWYG editor. I have tried to post an image, and the little box is opening where I put the URL in. I had all of the settings filled out, however there is no “OK” or “Done” etc. button! I tried to hit “Enter” and “Return” and it just cleared my values. The “X” button to close the window doesn’t work, either.

In addition, I have a Firefox extension that validates Javascript and the like, and when I try to do anything in the image box, a Javascript error appears at the bottom of my browser.

Any ideas?

Viewing 15 replies - 1 through 15 (of 28 total)

1 2 →

juvenal
(@juvenal)

17 years, 2 months ago

I’ve also just upgraded to 2.1
My WYSIWYG toolbar only contains the following:
bold, italic, split post and spellchecker
Should there be more? I have activated visual editor under Your Profile

Samuel B
(@samboll)

17 years, 2 months ago

Some people have reported a conflict with the WP rte and Firefox.

exilefromgroggs
(@exilefromgroggs)

17 years, 2 months ago

I’d also say that the visual editor works an awful lot better under IE than under Mozilla – where the tabs are incredibly slow. Is this to do with lack of JavaScript support outside Microsoft, perhaps? If so, can I suggest an early move away from JavaScript?!

marekklein
(@marekklein)

17 years, 2 months ago

I am also missing RTE after upgrade to 2.1.
The behavior is same in IE6.0 and Opera 9.10.

marekklein
(@marekklein)

17 years, 2 months ago

There is a javascript error:

Error: dbxManager is not defined Source file: http://gregoriana.sk/wordpress/wp-admin/dbx-admin-key-js.php?ver=3651&pagenow=post-new.php Line: 1

Atta
(@atta)

17 years, 2 months ago

Yes, I am getting similar issues. The Errors I have are:

JavaScript – http://www.theflax.f2s.com/wp-admin/post-new.php
Inline script compilation
Syntax error while loading: line 1 of linked script at http://www.theflax.f2s.com/wp-includes/js/tinymce/tiny_mce_gzip.php?ver=20061113 :
<br /
–^

JavaScript – http://www.theflax.f2s.com/wp-admin/post-new.php
Inline script thread
Error:
name: ReferenceError
message: Statement on line 35: Reference to undefined variable: tinyMCE
Backtrace:
Line 35 of linked script http://www.theflax.f2s.com/wp-includes/js/tinymce/tiny_mce_config.php?ver=20061113
tinyMCE.init(initArray);

JavaScript – http://www.theflax.f2s.com/wp-admin/post-new.php
Inline script thread
Error:
name: ReferenceError
message: Statement on line 5: Reference to undefined variable: tinyMCE
Backtrace:
Line 5 of inline#5 script in http://www.theflax.f2s.com/wp-admin/post-new.php
if (tinyMCE.isMSIE)
else

eberthmq
(@eberthmq)

17 years, 2 months ago

the exact same thing is happening to me, the icons on wysiwyg are not appearing

drmike
(@drmike)

17 years, 2 months ago

Be sure to clear out your browser cache and do a forced reload of the page that you’re looking at.

Please see if that helps,
-drmike

Atta
(@atta)

17 years, 2 months ago

It didn’t help for me I’m afraid.

bigbaddie
(@bigbaddie)

17 years, 2 months ago

Zoinks! Clearing the cache solved the problem for me. I can now see the icons for the RTE. I’m using Firefox.

marekklein
(@marekklein)

17 years, 2 months ago

Clearing the cache is not help for me.
See this screenshot:
http://gregoriana.sk/images/write_post.png
I also do not see an option for turning visual editor on/off. Where should I find it?

mikeymoo
(@mikeymoo)

17 years, 2 months ago

The Option to use the Visual Editor is under your profile.

Hope that helps 🙂

juvenal
(@juvenal)

17 years, 2 months ago

First I tried IE instead of Firefox, and RTE was fine.

Then I cleared Firefox cache, and now I have RTE there as well.

Thanks folks!

waterblossoms
(@waterblossoms)

17 years, 2 months ago

I’m having the same problem. Clearing the cache in Firefox and using IE did not fix it. 🙁

I mourn!

Advice?

arbitrarymarks
(@arbitrarymarks)

17 years, 2 months ago

Try the Chenpress plugin to get a better WYSIWYG editor. I can’t help fix the problem, though. This is why I rolled back to 2.0.7 and am waiting for them to fix 2.1.