#42722 closed defect (bug) (fixed)
Plugins failed to load
Reported by: | solutiondriven | Owned by: | azaozz |
---|---|---|---|
Milestone: | 4.9.3 | Priority: | normal |
Severity: | normal | Version: | 4.9 |
Component: | TinyMCE | Keywords: | fixed-major |
Focuses: | javascript | Cc: |
Description (last modified by )
After updating to WordPress 4.9, I am getting over 30 Console errors with a 403 status meanwhile all the plugins are present in the plugins folder. And then I get this error
tinymce.min.js?ver=4607-20171116:28 Uncaught (in promise) TypeError: Cannot read property 'getNotificationManagerImpl' of undefined
at h (tinymce.min.js?ver=4607-20171116:28)
at k (tinymce.min.js?ver=4607-20171116:28)
at <anonymous>
Attachments (2)
Change History (23)
#3
@
7 years ago
I am getting over 30 Console errors with a 403 status meanwhile all the plugins are present in the plugins folder.
My apologies, I glanced over that - That kind of error would probably indicate a file permission error, using the builtin reinstaller may correct it, but it might also be a host-related block or something
#4
@
7 years ago
Following, this is happening to me after upgrading as well.
tinymce.min.js?ver=4607-20171116:28
#5
@
7 years ago
To follow up, I took the advice to reinstall 4.9 and the errors seem to go away. This could be the right fix.
#9
@
7 years ago
I came here from:
https://github.com/tinymce/tinymce/issues/3947
Since October 2017 dozens of people are reporting this exact same issue in the above ticket. Hashtag me too.
In the WordPress 4.9 admin dashboard, I get the same JS error in the console - but it only appears when I scroll. Even weirder: when the page loads and I don't scroll until it's finished loading, the error will not show up.
Same for me when I'm on an Admin page using both Select2 JS (bundled with a custom fields plugin) and wp_editor
.
#10
@
7 years ago
What does reinstalling wordpress mean? I use a deploy system that pulls fresh wordpress files each time and would always be "reinstalled" on every deploy but still seeing this issue.
Admins, editors can't see styles isn't going over so well.
#11
@
7 years ago
- Component changed from Plugins to Editor
- Focuses javascript added
- Keywords reporter-feedback removed
The original report appears to cover two seperate issues. As @dd32 suggests, the 403 errors are likely a broken install.
The uncaught promises are the result of a TinyMCE bug fixed by a recent commit on the TinyMCE repo. It was fixed in TinyMCE 4.7.0
I've been able to reliably reproduce it under the following conditions on the WP 4.9 branch:
- multiple instances of
wp_editor()
are correctly called on the edit screen - TinyMCE is not cached by the browser and a scroll event is triggered before it loads
@azaozz @iseulde would you consider bumping/hacking TinyMCE for WP 4.9.2?
#12
@
7 years ago
- Milestone changed from Awaiting Review to 4.9.2
Yes, seems we will have to update TinyMCE in a dot release, don't think we can backport this fix. There are also other bugs that will be fixed, see #43012.
#13
@
7 years ago
@azaozz
I've uploaded 42722.diff which I think covers the required fixes only for TinyMCE if you'd rather include only the fixes.
Unfortunately the TinyMCE commit referenced covers two unrelated changes so it's a little unclear as to which portion is the fix and which portion is the enhancement.
#14
follow-up:
↓ 16
@
7 years ago
@peterwilsoncc yep, I got pretty much the same patch plus a bit more to fix the second part of #43012. The problem is that we will also have to update tinymce.min.js. We cannot rebuild TinyMCE 4.6.7 as it pulls scripts from other locations that are usually different/updated. We can try to patch and minify tinymce.js the same way we minify the rest of the core js but that yields different results. This should be "safe" to do however there is a (tiny) chance to introduce regressions and I'd be "nervous" to try it in a dot release. Seems the best option is to have a long-ish beta and try to get it tested extensively.
#17
in reply to:
↑ 16
@
7 years ago
Replying to SergeyBiryukov:
Yes, nearly ready.
#18
@
7 years ago
- Owner set to azaozz
- Resolution set to fixed
- Status changed from new to closed
In 42576:
Hey @solutiondriven and welcome to Trac,
This sounds like it's either due to a partial upgrade, or a plugin/theme conflict. As there's been no other reports of this, it sounds like a much more localised issue than something general with 4.9.
Could you please try reinstalling WordPress first (It'll just refresh the files, to make sure they're all up to date) by going to Dashboard -> Updates and clicking reinstall?
While you're there, check if there's any updates to plugins.
If neither of those fix it, if you could disable all plugins temporarily to see if one of those is causing the issue, that'd also be appreciated.