I’ve seen this happen before, but could not figure out specifically why. It depends on your specific installation though. There must be something unique about your site that is causing that.
If you figure out, it would be great if you posted it here and I could create a global solution.
Thread Starter
Foococo
(@simplefootball)
Hi,
I did find out the reason and this was because of my caching plugin (in my case WP Rocket).
I had the “Disable WP Embeds” turned on and by switching it off errors disappeared.
I don’t know if it’s possible for your plugin to work without WP Embeds, but at least you now know where to point out future similar request and/or where to start to work on to have this error solved.
Best regards
Nice! Thank you for posting your findings.
Are you familiar with what the purpose of disabling WP Embeds is for?
Thread Starter
Foococo
(@simplefootball)
It’s purely for optimization: it avoids one http request + one file to be downloaded. Given the size of the file I really believe this is minor.