Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ReferenceError: tinyMCE is not defined #790

Closed
spwebguy opened this issue Nov 7, 2016 · 8 comments
Closed

ReferenceError: tinyMCE is not defined #790

spwebguy opened this issue Nov 7, 2016 · 8 comments

Comments

@spwebguy
Copy link

spwebguy commented Nov 7, 2016

Hi team!

First of all, this tool is wonderful, I've been using it for more than a year and it's the best thing I found for creating metaboxes in my WordPress plugins.

I'm having an issue since the last update of the CMB2 plugin (2.2.3). I use it for repeating groups of fields. In short, my metaboxes look like this:

  • Repeatable group
    • Text field
    • Textarea

It's very simple. You just have a repeatable group with two fields in it.

Whenever I try to remove an item from the group (using either the red cross on the top-left corner or the "Remove" button) I get this message: ReferenceError: tinyMCE is not defined.

Here's a screenshot of the console:
Error screenshot

Thank you very much in advance, I appreciate all the work you do!

Gia —

@tw2113
Copy link
Contributor

tw2113 commented Nov 7, 2016

Curious if #730 is related to your case. Perhaps pull a copy of Trunk and re-try with that?

@jtsternberg
Copy link
Member

Yep, as @tw2113 mentioned, this is likely resolved in trunk. Please test and let us know. Thank you.

@spwebguy
Copy link
Author

spwebguy commented Nov 8, 2016

Hi both,

Thank you for the quick response, it's very much appreciated. I will test it with the version in trunk but I'm using your CMB2 WordPress plugin as a dependency for my own plugin, and the last version is throwing this error.

What I mean is even if trunk works, my users will always have the latest version you've uploaded on WordPress.org. And I don't really want to integrated/embed (sorry for the shitty English...) your entire code here in my plugin.

I hope this makes sense, let me know if I'm missing something... and thank you for reacting that fast.

Gia —

@ghost
Copy link

ghost commented Nov 8, 2016

Just to confirm I also had the same issue (in a front end form) as above/#730.

Using trunk fixed it - thanks! Will use this rather than plugin for now...

@spwebguy
Copy link
Author

spwebguy commented Nov 8, 2016

Hi all,

If I was creating a plugin now I would definitely use trunk but I have thousands of active users that were prompted to install CMB2 as a dependency, if I use the trunk code in my plugin now, the CMB2 WordPress plugin will take over and throw this error (because they already have it installed).

The solution I have now is to add the trunk's code in my plugin and ask my users to delete the CMB2 WordPress plugin, but I'd rather keep it as dependency. Is there any way you could quickly patch the WP plugin (sorry if this doesn't make sense...)?

Hope it's clear :) Keep me posted!

GIa —

@jtsternberg
Copy link
Member

I'm going to release a quick bug-fix update today.

@jtsternberg
Copy link
Member

Closing, as this has been fixed, and a release pushed out.

@spwebguy
Copy link
Author

spwebguy commented Nov 8, 2016

Wow! I don't know what to say I wasn't expecting this.

Thank you very much, you're the best.

Gia —

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants