coriannas

Just seconding that this is a bug – I am also having this problem on my site. Specifically, it seems to happen on Chrome and Firefox, but not Safari.

• This reply was modified 6 months, 2 weeks ago by coriannas. Reason: Added details

Actually, I just realized that if I turn off “Combine Javascript Files” on SiteGround’s Speed Optimizer plugin, it fixes the issue. I wasn’t able to find any files from this plugin in their dropdown to exclude (which I have read means that they are likely hardcoded, rather than properly enqueued), so I just disabled the feature entirely, but it would be great to be able to just exclude the javascript files from combination in the future!

Thanks for your help.

What kind of additional information would be helpful to you? The error above only happens on Safari, and only when logged in. If not logged in, I don’t get any error at all, but the feed will not load.

In Firefox, I’m getting this error, both when logged in and when I am not: “Facebook SDK is being shimmed by Firefox. See?https://bugzilla.mozilla.org/show_bug.cgi?id=1226498?for details.”

The only error I’m getting in Chrome is “Uncaught TypeError: Cannot read properties of undefined (reading ‘use’)
at (index):204:3
at (index):205:4″

The widget does not load in any of those browsers whether logged in or not, except oddly, it does load when I am logged into the dashboard in Chrome.

Hi Milap,

I’ve deleted the plugin and installed the latest version (6.4), but I’m still getting the same problem. Any other ideas?

@data443 thank you! The new update fixed the problem for me.

I am having the same problem as ethanjrt, where the gtag code in the head is getting split between the head and body of the page – I have temporarily moved it to the body of the site, but would prefer being able to put it in the head…is there a fix in the works for this issue?

@hawaiipersson For me, the image does crop properly, but you’re correct, it’s sending me to the error page after update, rather than back to the edit page with a nice little notice to let me know it’s been updated properly.

Same exact problem here too!

True. Suppose I should have checked that first. Thanks.

In my case, I can get rid of the error by adding both ‘wp-bruiser,jquery.js’ to the “Exclude Scripts” list in Autoptimizer. It’s not ideal, since it likely slows the site down to some extent, but it doesn’t seem to be awful. In my case, it makes sense to load jQuery in the header anyway, since this is probably not the only plugin that will not work with it loading in the footer, and the speed hit I take isn’t too terrible. I will continue looking for other solutions, but in the meantime, I hope this helps someone else down the line

Hm… Done, but the error is still there.

Thanks. The site is here.

Thanks for reporting the issue. Instead of messing with the source files, I just downgraded back to version 1.3.0.1. I’ll keep track of the progress. Looking forward to being able to update!