• Resolved p24l

    (@p24l)


    I have a typical problem. I’ve upgraded to WP2.1 and WYSIWYG Editor doesn’t work.

    – WYSIWYG Editor is turned ON in my profile
    – I turned off all of my plugins

    If I turn WYSIWYG off, I can see HTML buttons. when I turn WYSIWYG on, I see only a blank textarea.

Viewing 10 replies - 1 through 10 (of 10 total)
  • Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    I had the same problem (see https://www.ads-software.com/support/topic/102581)

    Applying this patch https://trac.www.ads-software.com/attachment/ticket/3144/3144-gzipoptoins-tinymce.patch solved that problem for me.

    In UNI*X

    cd wordpress/wp-includes/js/tinymce
    patch -p0 < 3144-gzipoptoins-tinymce.patch

    After that the visual editor works fine for me.

    I’m having the same problem on my test blog and am running on a virtual server. (Haven’t upgraded to 2.1 on my live blogs yet – 2.0.7 is working just fine). Is there another way to apply the patch without going into unix?

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    You could apply the patch by hand. Make a backup copy of

    wordpress/wp-includes/js/tinymce/tiny_mce_gzip.php

    And go to line 131 and replace the line

    if ((in_array('gzip', $encodings) || in_array('x-gzip', $encodings) || isset($_SERVER['---------------'])) && function_exists('ob_gzhandler') && !ini_get('zlib.output_compression')) {

    With the changed line

    if ((in_array('gzip', $encodings) || in_array('x-gzip', $encodings) || isset($_SERVER['---------------'])) && function_exists('ob_gzhandler') && !ini_get('zlib.output_compression') && get_settings('gzipcompression')) {

    If it blows up due to a typo just put the backup copy back.

    Thanks, I’ll try that.

    In an upgrade to a live site, I’ve tried applying the patch by hand and uploading the changed file, but the WYSIWYG editor still does not display.

    In a fresh installation for a new blog, I did not have to apply the patch. The WYSIWYG editor worked out of the starting gate.

    Mine was a fresh installation. The test blog was set up to run 2.1 to iron out any bugs. I haven’t dared any upgrades yet.

    But it’s working now — yay! And many thanks.

    Thread Starter p24l

    (@p24l)

    jdembowski: that’s it. it works fine now. Thank you.

    jdembowski: i’m a novice, so bear with me. i tried applying the fix you recommended to nicobet, to no avail. i tripled checked the code i pasted into the tinymce.php file, and it was accurate.

    i want a WYSIWYG editor much like the last version of word press. why they would take that away, I have no idea. the new editor is clunky and lame.

    oh, i just installed 2.1, for your (or anyone else’s) reference.

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    @hereandthereblog

    Dunno what to say other than “Good luck!” ?? My test blog was a fresh 2.1 install on a different server and the visual editor worked out of the box. On my real blog on a different server, I went from 2.0.7 -> 2.1 and visual editor gave up the ghost. The patch fixed my problem.

    If you’re using a Linux or UNIX install and can used patch -p0 <patch.txt then I recommend it as it’s cleaner and less prone to typo’s (which I do all the time). It’s likely you are experiencing a different problem.

    Horay! It is now fixed for me. Many thanks.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘WYSIWYG Editor’ is closed to new replies.