I am using the Divi theme, with it’s built-in Builder feature. When editing a text box, the “Visual Editor” fails to load (this has the wysiwyg editor, etc.), and I can only edit raw text.
Checking all plugins, I have isolated it to Simple:Press. I’m on version 6.4.0.
Checking F12 in Chrome, and it reports multiple “DevTools failed to parse SourceMap” errors. Doesn’t point me to any specific source, though.
We just tried the DIVI Theme with only SP loaded. We created a new page and tried adding a text box The visual tab showed up.
We know Divi sometimes have issues editing existing content especially after they do an upgrade. Does this issue happen on an existing page or on a new page?
PS: The parsing of the sourcemap warnings seem to be divi maps, not SP maps.
I’m using the Divi “Extra” theme which is built on Divi, if that matters.
Yes, it happens whether editing prior content or creating new content.
I know the sourcemap warnings are referencing the Divi builder, but the errors only occur when Simple:Press is activated.
I guess I will try various SP plugins, see if it’s one of those.
You might want to try just the plain divi theme. That will let you know if its a problem with EXTRA or the core DIVI theme builder. Even though extra is a child theme, it could be that it has something added to it that is the cause of the issue.
I just realized my SP license isn’t activating as expected, so all my plugins are not updating. I opened another thread on that. Once that’s sorted, that may simultaneously fix THIS problem, too.
So let’s put this one on pause for now. I will report back.
OK, all plugins updated, no joy.
Switching to standard Divi theme also has no effect.
I tested again — switching off SP entirely fixes the problem. I’ll have to track this down to an individual plugin I think. I’ve got a ton of them, so this won’t be easy.
Problem lies with the Editor TinyMCE Rich Text plugin. Toggling that off fixes the problem site-wide. Toggling it on cripples the Visual Editor.
Not sure what to do next.
It is possible that Divi or Extra might be using a different version of TinyMCE than we are. If that’s the case then you will not be able to use the SP TinyMCE plugin – you can use the HTML Editor or BB Code editor plugins (which admittedly aren’t as user friendly). Or you’ll need to switch to a different theme. Unfortunately there’s no way around making that choice.
Alternatively, you can disable the SP tinyMCE plugin whenever you need to edit in Divi and renable it after you’re done. Its a PITA but might be a good way to work with the two together.
Note – we use the version of TinyMCE that is built into WordPress. If Divi is using a different version for some reason or just don’t like having TinyMCE scripts enabled on a page then there’s not a lot we can do about it unfortunately.
Toggling off the TinyMCE plugin in SP causes the user’s field for entering the post text down to a tiny box. See attached. Something really weird is going on. When TinyMCE is toggled on, the post field is normal size.
Huh. If you use the basic 2020 theme, does the plain editor box go back to being larger?
What happens if you press the CTRL-F5 key combo to refresh the js/css cache?