WordPress.org

Forums

Visual Editor - text white-on-white, and functions missing (3 posts)

  1. sa_cooke
    Member
    Posted 2 years ago #

    Hi,

    I have googled this issue a lot, and there is no definitive answer, although a lot of people do seem to be experiencing it. So I am posting my issue as a separate issue, even though it is quite similar to others.

    A couple of days ago, pages I had previously been able to edit with the Visual Editor started acting strangely. The editor appeared differently - less functions, and text is white-on-white. I am able to select the text by dragging the cursor over it. I have images of this behaviour, but I am unsure how to share them with this forum.

    Another symptom I have, and I believe it is related, is a warning message I am getting in the dashboard: Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 1966080 bytes)

    Does anyone have any solutions to this issue please?

    I have increased memory PHP can use (128M to 256M), I have increased memory WordPress can access from 32M to 128M (wp_config). I also tried adding adding a line into the .htaccess file, but this caused the site to crash.

    Any thoughts and/or fixes would be much appreciated.

  2. Hi,

    The editor appeared differently - less functions, and text is white-on-white. I am able to select the text by dragging the cursor over it.

    This is a tell-tale sign you have a javascript issue. The first thing you want to do is make sure you are using the most recent version of WP (3.5.1)... and that all of your plugins are updated, and compatible with WP 3.5.1.

    If you still have issues.. you need to deactivate ALL of your plugins... manually empty your browser cache.. and try the editor again to see if it loads properly. It is very important to follow these two steps in troubleshooting.

    Lastly, if it still does not load with all plugins deactivated and your browser cache manually emptied... then switch your theme to the default twentytwelve theme.. empty the browser cache.. and try again.

    The bottom line is we are trying to determine where the javascript conflict is coming from. Also, it would be most helpful to see a debug log from your browser console... but I can't take the time to explain this. If you care to Google it... post your results back here.

    Let us know how you do.

  3. sa_cooke
    Member
    Posted 2 years ago #

    Thank you Josh. I will do as you ask.

Topic Closed

This topic has been closed to new replies.

About this Topic