rpeacan

I’m not able to put much together at the moment, but it was visible to me in Chrome, and it appeared to be something to do with the wp-polyfill script in the footer. Directly after it, there was a broken script tag. Here is what was in the footer when viewing source:

<script type="text/javascript" src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill.min.js?ver=7.4.4" id="wp-polyfill-js"></script>
<script type='text/javascript' id='wp-polyfill-js-after'>
( 'fetch' in window ) || document.write( '<script src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill-fetch.min.js?ver=3.0.0"></scr' + 'ipt>' );( document.contains ) || document.write( '<script src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill-node-contains.min.js?ver=3.42.0"></scr' + 'ipt>' );( window.DOMRect ) || document.write( '<script src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill-dom-rect.min.js?ver=3.42.0"></scr' + 'ipt>' );( window.URL && window.URL.prototype && window.URLSearchParams ) || document.write( '<script src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill-url.min.js?ver=3.6.4"></scr' + 'ipt>' );( window.FormData && window.FormData.prototype.keys ) || document.write( '<script src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill-formdata.min.js?ver=3.0.12"></scr' + 'ipt>' );( Element.prototype.matches && Element.prototype.closest ) || document.write( '<script src="https://website.com/wp-includes/js/dist/vendor/wp-polyfill-element-closest.min.js?ver=2.0.2"></scr' + 'ipt>' );
</script>

and this is what would appear at the bottom of the page:

' );( document.contains ) || document.write( '' );( window.DOMRect ) || document.write( '' );( window.URL && window.URL.prototype && window.URLSearchParams ) || document.write( '' );( window.FormData && window.FormData.prototype.keys ) || document.write( '' );( Element.prototype.matches && Element.prototype.closest ) || document.write( '' );

I’m also experiencing this on Chrome with WordPress v5.6 and plugin v3.3.6.

For the time being, I’ve enabled Email Sharing because of @rpasillas comment above and it fixes the bug, but just wanted to let you know this is still occurring.

Thank you very much, I really appreciate it. That confirms where I should be putting the information.

It turns out I am actually having trouble with MAMP locally for development. It doesn’t support https with curl so that’s where my issue was. When I threw it up on a dev server it all started working fine.

I suppose I’ll start looking for another method to develop locally with, but it seems the plugin itself is working fine if the environment is set up correctly. My bad!

I’m seeing that DO isn’t actually supported right now… Which is a big bummer considering it appeared to support it. But it seems like they’re changing things on their end so it makes sense.

That being said, I can’t get this to work with S3 either. Any tips? Thanks for your help.