The help tab is hidden but the markup for it is still output. What is the actual error? I see no such thing, even after clicking the help tab/viewing the video.
> Remove the Wistia iframe.
You may not find it useful but others will, thats why they are there. it’s handled in https://github.com/woocommerce/woocommerce/blob/master/includes/admin/class-wc-admin-help.php – 1 video per WC screen.
Turned out a different js error elsewhere was breaking the page. Would delete this if I could
So I have WC as the only active plugin running Twentyseventeen. Still get the errors. Still get Wistia’s damn content loading on my page when I don’t want it. You shouldn’t be loading anything from a third party until it’s requested by the user. I haven’t even toggled the help panel.
So I have WC as the only active plugin on a site with Twentyseventeen, and still get resources loading from Wistia and their errors just by going to the add new product page.
Steps to reproduce.
1. Install WordPress
2. Install WooCommerce and enable
3. Go to add new product page
4. View JS console:
JQMIGRATE: Migrate is installed, version 1.4.1 load-scripts.php:9:542
o.default.defaultView.getComputedStyle(…) is null E-v1.js:568:1683
r@https://src.litix.io/core/2/mux.js:7:28951
r/i.getStateData@https://src.litix.io/core/2/mux.js:8:2312
[16]</V.prototype.updateStateData@https://src.litix.io/core/2/mux.js:7:25431
[16]</V/<@https://src.litix.io/core/2/mux.js:7:23339
[5]</a.prototype.emit/o/<@https://src.litix.io/core/2/mux.js:7:4871
[5]</a.prototype.emit/o@https://src.litix.io/core/2/mux.js:7:4849
[5]</a.prototype.emit@https://src.litix.io/core/2/mux.js:7:4902
[16]</V@https://src.litix.io/core/2/mux.js:7:24915
[15]</t.exports</o.init@https://src.litix.io/core/2/mux.js:7:19072
r@https://src.litix.io/core/2/mux.js:8:3375
[15]</t.exports</o.monitor@https://src.litix.io/core/2/mux.js:7:18759
e.mux.setup/</n@https://fast.wistia.net/assets/external/E-v1.js:1770:2720
e.mux.setup/</u@https://fast.wistia.net/assets/external/E-v1.js:1770:2937
StopGo</t.prototype.flush/</<@https://fast.wistia.net/assets/external/E-v1.js:568:824
StopGo</t.prototype.tryAndReport@https://fast.wistia.net/assets/external/E-v1.js:568:1605
StopGo</t.prototype.flush@https://fast.wistia.net/assets/external/E-v1.js:568:769
StopGo</t.prototype.runFn@https://fast.wistia.net/assets/external/E-v1.js:568:2710
StopGo</t.prototype.run@https://fast.wistia.net/assets/external/E-v1.js:568:2507
StopGo</t.prototype._allInOne@https://fast.wistia.net/assets/external/E-v1.js:568:3346
t/this.allInOne</<@https://fast.wistia.net/assets/external/E-v1.js:568:160
e.mux.setup/</</</<@https://fast.wistia.net/assets/external/E-v1.js:1770:3515
doTimeout/u</n<@https://fast.wistia.net/assets/external/E-v1.js:245:792
E-v1.js:568:1750
Please remove that forced integration of a commercial third party without knowledge.
I don’t want wistia to know if someone uses the admin area of any site.
As @swinggraphics stated, there is no need to force loading of all the guided tour stuff for all users.
BTW: I get following error caused by the wistia integration (Latest Chrome with default settings):
GET https://fast.wistia.net/assets/external/E-v1.js net::ERR_BLOCKED_BY_CLIENT
Please create at least an option to deactivate it by removing it from DOM.
Or just
Remove the Wistia iframe.
I get the following error in WC:
[Error] SecurityError (DOM Exception 18): Blocked a frame with origin “https://fast.wistia.net” from accessing a frame with origin “https://[mydevsitehere]”. Protocols, domains, and ports must match.
This is an error generated by Ghostery, even though Wistia is whitelisted. Trying to add a new product and using the Characteristics tab to add a custom characteristic to a variable product. This is the only error on the page, and the page hangs now.
