Hi,
This error usually indicates that WP-Optimize wasn’t able to download the compressed image.
WP-Optimize uses the php function file_get_contents to download the compressed image. If the PHP setting allow_url_fopen is disabled on your server, it will make file_get_contents fail.
Are you able to check the value of allow_url_fopen on your server?
Best regards,
Marc.
Thread Starter
Mariette
(@mariette-jackson)
Hi
I have checked and can confirm that the allow_url_fopen option is enabled.
The websites are hosted on SiteGround, if that helps…
thanks
M
Hi,
Thanks. We’re working on a fix for this issue, and we hope it will be ready soon.
Best regards,
Marc
Thread Starter
Mariette
(@mariette-jackson)
Great, thanks. Will you confirm when it’s OK to try again please?
By the way, I received an email yesterday from WPMU DEV saying “Thank you again for using Smush to make your WordPress images fly.” I guess that is as a result of me using your plugin? I’m not using Smush anywhere (although I did many years ago).
thanks
Mariette
Yes we’ll let you know when we release the fix.
And no, the email from WPMU DEV isn’t from us. You’ll receive emails from us only if you sign up to our newsletter or buy the premium version on our website.
Marc.
Hi Mariette,
I had the same issue and figured it out. In case you need it, below is the reason.
‘allow_url_fopen’ is the issue. It must be enabled for wp-admin directory. On some servers( e.g. some cPanel why you can change PHP settings by putting a php.ini in the home directory ), it will only work for home directory. You need to put the same php.ini in the /wp-admin directory.
Writing a phpinfo(); in a test file and put it in /wp-admin directory to make sure ‘allow_url_fopen’ is enabled.
Kevin
Thread Starter
Mariette
(@mariette-jackson)
Hello Kevin
Thanks for that tip. I think this is already enabled server-wide on my Cloud hosting, not in a root php.ini, but this might help someone else having a similar issue.
For me, I have decided to return to Imagify for image optimisation.
best wishes
Mariette
Hello,
The new release should now fix the “invalid_response”.
Regards,
Marc.