Hello Sean,

You should run EasySocial in "Static" mode The settings is available at Settings > System Preferences

I just set it to Static. I had it as Optimized because there is a note that said to use Optimized if I was running multiple StackIdeas components on the site.
I am still have the problem where none of the javascript works in the EasySocial Menu bar.
I also ran GTmetrix again but it is still reporting the bad requests.
I have Javascript compression set to "Compressed". Should I maybe switch to Uncompressed?
I have Inline configuration set to No. Should I be changing that to Yes?
In order to have my site start working properly again I did just now turn OFF two of the settings you told me to turn on. I would like to turn them back on but if I do I will lose my Javascript again.
EasySoicial -: system Preferences -> Enable CDN and Client-side CDN have to be OFF for my Javascript to work and to make GTmetrix happy again. If I turn them on I will go from 97% to 91% immediately on my GTmetrix Page Speed result because of the 404/410 errors that appear on the site.
You are very welcome to login to my backend and turn those settings back to On in order to test things out. But, as of now turning those on breaks my Javascript.
Sean

Hello Sean,

This is probably because when you have turned on CDN, Cloudflare is activated and it would actually render those js files on the fly. Most statistics software would think that this is bad because it makes multiple requests but again, this is what Cloudflare does and there's no way around this

Thank you Mark,
I am actually using Amazon's CloudFront and not the CloudFlare CDN. :-)
So, I am thinking that if a person is using Amazon's Cloudfront CDN then they should NOT "Enable CDN" or "Client-side CDN" at EasySocial -> Settings -> System Preferences - CDN settings?
It does seem strange to me that without that setting all of the URLS that are being called for the Javascript are also URLS to files that exist within our filesystem. Once we turn ON those two settings then the URLs are all being written out to non-existent paths with our domain name appended in front of them. I think there may be a bug?
Sean

Ah yes, Eileen is right! I think that's why you are hitting this error. You'll need to set the protocol as the prefix.

Thank you Eilleen and Mark,
I did indeed not have a fully qualified URL. I just put it in with the https:// in front.
And, it appears to be the answer I was needing! :-)
I am very happy.
I love this forum!
Sean

Thanks for updating Sean, glad that your issues are resolved now