Visual & Text tabs displaying blank/empty after saving edits to content

Hi!

I’m having exactly the same problem. I can only save it in Chrome when in text-mode (on a Mac)

Great plugin, love it! It’s in my standard toolkit for building websites too…

Hope this is solved shortly, though!

Keep up the good work, this seems to be a minor problem (important minor problem…).

Cheers, Rolf

Hi there,
unfortunately I am not able to reproduce the issue on my Safari 5.1.7 (on Win 7).
I’d suggest to take a look at your browser error console.
Also a browser clean up (cache + cookies) may help.

Marco,

Thanks for the reply. Did you try it on a Mac? On a PC it seems to work fine..

Below my output copied from the console (Safari/Mac):

[Error] TypeError: ‘undefined’ is not an object (evaluating ‘a.createRange’)
getRng (wp-tinymce.php, line 6)
getNode (wp-tinymce.php, line 6)
(anonieme functie) (wp-tinymce.php, line 54)
r (wp-tinymce.php, line 8)
fire (wp-tinymce.php, line 9)
setContent (wp-tinymce.php, line 10)
update_content (black-studio-tinymce-widget.min.js, line 2)
deactivate (black-studio-tinymce-widget.min.js, line 2)
(anonieme functie) (black-studio-tinymce-widget.min.js, line 2)
dispatch (load-scripts.php, line 3)
handle (load-scripts.php, line 3)
trigger (load-scripts.php, line 3)
trigger (load-scripts.php, line 8)
(anonieme functie) (load-scripts.php, line 3)
each (load-scripts.php, line 2)
each (load-scripts.php, line 2)
trigger (load-scripts.php, line 3)
(anonieme functie) (load-scripts.php, line 28)
j (load-scripts.php, line 2)
fireWith (load-scripts.php, line 2)
x (load-scripts.php, line 4)
b (load-scripts.php, line 4)

—

It’s magic for me, but maybe it helps you solve the issue!

Cheers!

Rolf

I’m not having problems with Safari 6 on Mac. Anyway, your console error log was useful to identify the point where the problem occurs, so I made some change. Please could you try the current dev version available on Github (link “Download ZIP” on the right)? You have to uninstall your current version first (no widgets data will be lost).

Marco,

Thanks for the reply. I downloaded and installed the new dev version and it works! Great man!

Maybe it is good to know I also tested it on another WP install (with a couple of different plugins installed, like Contact Form 7) and there the problems didn’t occur (just like you tested it).

BTW: do I have to install the original Plugin folder or can I just rename your dev version when I like to update your plugin?

Again, really appreciate your help! Keep up the good work!

Cheers,

Rolf

Hi Rolf,
I think the problem was due to concurrent js event handlers that were not executed in the same order in all situations. Anyway the fix should prevent this issue from occurring.
You may keep the dev version as it is, it will be updated when the new stable release will be published, just like if you installed it from the WP repo.

Marco,

Okay, thanks again! Really nice..

Cheers,

Rolf

I’m having this same problem in Chrome. Happens on both Mac and Windows PC. Deactivated and uninstalled the one from the WP repo, and installed the one from GitHub, still same issue. With the one in WP repo, the WYSIWYG controls are there, but when I enter content and hit Save, they disappear and the content auto-changes from Visual to Text mode. With the one from GitHub, the TinyMCE controls never appear. I haven’t tried in FF or Safari yet, but I can’t make a user use a specific browser. I also double-checked to make sure that disable visual editor is unchecked.

It was an issue with my theme. I narrowed it down to something related to the Customizer. Soooo, as always, be sure to try in the default theme! :p

I have been using this plugin on all my sites – Great plugin but recently and only on WordPress 4.0 am I getting the issue described above.
First load the page all fine. DO some edit save and the Visual tab is blank select the Text tab all edits are there. Can’t switch back to the visual tab. Error on console is
TypeError: t is undefined
Have try the developer version and same result.

@w2kd It’s probably a conflict with another plugin. Please read our FAQ and open a new thread with the relevant information. This topic was related to another issue and it has been marked as resolved.