After a few sporadic reports in the past with an issue with the Visual Editor and Weaver Xtreme Plus, we’ve finally found a problem.
There IS a problem IF you have added custom Fonts using a particular format for the font family name.
So, if you have supplied a font-family name such as: font-family: “Gloria Hallelujah’, cursive; using a double quotation mark (“), this triggers what I would call a bug in TinyMCE that makes the display fail to display correctly (it does seem it is displaying white text on a white BG). Weaver Xtreme Plus Version 3.0.1 will fix this, but that won’t be released immediately.
To fix this problem, simply use single quotation marks instead: font-family: ‘Gloria Hallelujah’, cursive;
This may require re-defining any font-family definitions that use a double quotation. Delete the current definition, and re-enter. This is a very subtle bug, and explains why it was so difficult to track down. No one thought to mention they were using a custom font!