Hi!
That’s weird.
The URL in your code snippet is also optimized by Asset Cleanup, could you disable Asset Cleanup, to see if the same issue occurs with only OMGF enabled?
Thanks,
Daan
Hello Daan,
Thank you for your quick reply.
Yes, I have ACU set up, but so far it was not a problem (and still is not on the production server).
Anyway I deactivated it, as requested.
<link rel='stylesheet' id='oceanwp-google-font-poppins-css' href='http://pm6.local/wp-content/uploads/omgf/oceanwp-google-font-poppins/oceanwp-google-font-poppins.css?ver=1657466711' media='all' />
Slightly better, but still a problem.
Since my website is in https, it still creates a problem
Chrome dev tools says :
Mixed Content: The page at 'https://pm6.local/' was loaded over HTTPS, but requested an insecure stylesheet 'http://pm6.local/wp-content/uploads/omgf/oceanwp-google-font-poppins/oceanwp-google-font-poppins.css?ver=1657466711'. This request has been blocked; the content must be served over HTTPS.
And yes, I have Really simple SSL plugin too.
Actually I had both plugins since the inception of the website, and did not have any problem so far.
Okay, hm, let’s see: your settings in Settings > General > WordPress Address & Site Address. Do they both start with https://?
Thank you again for your reply.
Actually I flushed the permalinks, reactivated the ACU plugin, and the address was now correct.
Go figure…
All I needed to do then, was to update the domain name in the oceanwp-google-font-poppins.css file, a process I am used to.
SOLVED ! 😉
Awesome. Weird, though!
Btw. are you a Pro user? OMGF Pro allows you to set a Relative URL using the Modify Source URL option. That’ll save you having to do that process all the time!
Thanks for sharing the steps to resolve the issue, btw. I’ve gotten 2 other people experiencing the same issue and your solution fixed it for them as well. It’s in my documentation now 🙂
