Make WordPress Core

Opened 4 years ago

Closed 15 months ago

#40274 closed defect (bug) (invalid)

invisible fonts in admin panel, visual editor missing

Reported by: dadapotok Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.7.3
Component: TinyMCE Keywords: close
Focuses: ui, administration Cc:

Description (last modified by azaozz)

invisible fonts in admin panel, visual editor missing
more search words:
error - white fonts in text editor, visual editor disappeared

known fix:
This widely known bug and how to fix it is already described here and here:
7 months ago:
in 2013:
I had same bug at 2017-03 in WP 4.7.3 and used fix

define('CONCATENATE_SCRIPTS', false);

without any idea of what happened and what am I doing. It worked, but it wasn't a pleasant experience.

Reinstalling WordPress does not fix it, and it always needs a manual fix I thing it is a good thing to report it as a bug

Attachments (1)

Screenshot 2017-03-26 post content renders in white in any browser.jpg (400.1 KB) - added by dadapotok 4 years ago.
text and buttons cannot be seen neither in Visual nor Text mode

Download all attachments as: .zip

Change History (5)

4 years ago

text and buttons cannot be seen neither in Visual nor Text mode

#1 @SergeyBiryukov
4 years ago

  • Component changed from Administration to TinyMCE
  • Focuses performance removed

#2 @azaozz
4 years ago

  • Keywords close added

This happens when there are JS errors on the page. Best is to search the support forum for the exact error. If none found, paste the errors in a new thread.

See: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors.

#3 @dadapotok
4 years ago

I'm sorry I can't comprehend this + I already used the fix and replaced my site with test site copy that works fine. All I can say is that 2013 post and 2016 post I mentioned earlier shows that there are a lot of people experience same issue for a long time.

#4 @azaozz
15 months ago

  • Description modified (diff)
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

As far as I've seen on the support forums there is a chance that some cache somewhere is not updated fast enough which sometimes results in js errors on the (old) Edit Post screen. These errors "break" the classic editor, even when they are not directly in it. They usually "magically" fix themselves after some time when the cache is updated.

Best place to get help for these cases is the support forum. There are several steps to try to fix or determine what's the problem.

Note: See TracTickets for help on using tickets.