Make WordPress Core

Opened 7 years ago

Closed 7 years ago

Last modified 6 years ago

#41124 closed defect (bug) (fixed)

TinyMCE popup doesn't works with latest release

Reported by: umeshsingla's profile UmeshSingla Owned by:
Milestone: 4.9 Priority: normal
Severity: normal Version: 4.8
Component: TinyMCE Keywords:
Focuses: Cc:


I'm using TinyMCE popup for a custom plugin, with latest WordPress 4.8, it throws a error.

I dig in deeper, and found out, the changes in, are causing the issue.

dom and util are loaded directly and not as plugins, and hence when createInstance is called in, tinymce is unable to resolve the Classnames and it throws the above error.

The fix is to revert the path to tinymce.util.Dispatcher and tinymce.dom.DOMUtils

I couldn't locate the use of these at other places in core, so not sure, if that's gonna break something else. But I did test the regular text editor in WordPress and TinyMCE Advance plugin, they both worked fine with the changes.

Attachments (1)

41124.diff (1.1 KB) - added by UmeshSingla 7 years ago.
Updated dom and util path for tinymce

Download all attachments as: .zip

Change History (8)

7 years ago

Updated dom and util path for tinymce

#1 @azaozz
7 years ago

  • Milestone changed from Awaiting Review to 4.9

This was fixed upstream and will be in the next TinyMCE update. Can also add it i the next dot update as it is in an external TinyMCE plugin. See:

However this functionality (tinymce-popup.js) is a left over/compatibility mode for TinyMCE 3.x that was last used in WordPress 3.8. It will be much better to update your plugin to not use such outdated APIs.

Last edited 7 years ago by azaozz (previous) (diff)

This ticket was mentioned in Slack in #core by melchoyce. View the logs.

7 years ago

#4 @melchoyce
7 years ago

  • Milestone changed from 4.9 to 4.9.1

#5 @iseulde
7 years ago

  • Resolution set to fixed
  • Status changed from new to closed

This was fixed upstream in TinyMCE 4.6.7 and is included in WordPress with [41604].

#6 @johnbillion
7 years ago

  • Milestone changed from 4.9.1 to 5.0

#7 @johnbillion
6 years ago

  • Milestone changed from 5.0 to 4.9
Note: See TracTickets for help on using tickets.