Closed mxbclang closed 3 years ago
I've performed some testing on this. Reproducible as per this recording, more insights below:
wp_enqueue_script('google_charts', $src ='https://www.google.com/jsapi',$deps = array(), $ver = false, $in_footer = false);
@bethanylang Moving to backlog for engineer review.
Another user reported the same issue & have installed The Monetizer plugin.
My initial intuition is that that plugin also uses the Google charts library, and maybe they are loading it unconditionally even on Site Kit-controlled screens. Basically they're still loading the version that Site Kit has had the conflict with, and the problem is they might be loading it in more places than they should.
I can have a look to verify, but if that's the case, the problem lies on their end rather than on ours.
Indeed, this is a problem in the "The Moneytizer" plugin, they load their CSS and JS unconditionally on all admin screens of WordPress, which causes this problem in Site Kit (see https://plugins.trac.wordpress.org/browser/the-moneytizer/trunk/themoneytizer-config.php#L3). I'm not sure what the best strategy is here, but this needs to be fixed on their end.
Per discussion in today's meeting, this issue needs to be fixed on The Moneytizer plugin. @jamesozzie will reach out via their support forum to request a fix. James, when you've done so, can you please close out this issue and link to your support topic? Thank you!
Thanks all for reviewing.
@bethanylang I've created a WP Support topic now, you'll find it here. For impacted users feel free to keep watch of that support topic.
Tested and confirmed the latest Moneytizer update has a fix in place (Version 9.0).
Bug Description
Two users in the support forum (here and here) reported still receiving the
Cannot read property 'ea' of undefined error
(#3132) that resulted from the Google Charts API update earlier this week even after updating Site Kit to v1.3.0. This error occurred when going to Site Kit > Dashboard.Ultimately both users discovered that deactivating The Moneytizer plugin fixed the issue. One user reported that they had had The Moneytizer plugin installed since June 2020 without issue until updating to v.1.3.0, so it appears that this conflict may have been introduced in our most recent release.
Steps to reproduce
Additional Context
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation Brief
Test Coverage
Visual Regression Changes
QA Brief
Changelog entry