Invalid argument error

Hi @arbpen,

Although the image has the .jpg extension, it does seem to be encoded in webp: https://i.imgur.com/3vDvtKJ.png

The plugin should automatically convert webp images based on the content-type, and not the extension, so theoretically that shouldn’t be a problem.

Are you using the W3Speedster plugin by any chance? I recently had another user with same issue, and he used that plugin to generate those images.

~ Koen

Very interesting! The mystery just got a lot larger. When I do pictures, my process is to take the image from my phone (jpg), resize and enhance it with my ancient image editor which is so old it was created before Google was even a thought (but it’s still a good editor,), convert the image and add a watermark to webp, then upload both the jpg and the webp to the server, add them to the Media Library via Add from Server, add alt via Media Assitant, then choose which jpg for the post. I already know that webp won’t work for posting to Pinterest and other apps, so my Featured Image is always jpg. As you can see from my convoluted method, that jpg I get from my phone never was or becomes a webp. That must mean that my web host is doing this – shame on them! –> … runs off to web host.

You would THINK, since it’s Google’s My Business and since Google INVENTED webp that they would accept it. Thanks for all your help. I’ll be back when I find out what’s going on. The solution to this might be helpful to someone else.

Yeah, looks like they’re converted on the fly at some point after the plugin checks if they’re a WebP image. It does this by checking the file content-type locally on the filesystem, not the image URL.

I’ll add a webp-check to the actual image URL in the next update, that should fix the issue!

It turned out to be the CDN that was doing it. I have CDN through a hosting provider and they have now turned off the conversion from JPG to WEBP. Then, this morning, I realized that Jetpack’s CDN was also doing it, so I turned off the image CDN through Jetpack, cleared the cache at the host, and the post went through flawlessly.

Happy to hear that you’ve found a solution already! Just in case I have added an extra image content-type check in the 3.1.5 update. That should allow you to use the WebP conversion service provided by your CDN, and still have the GMB posts go through properly.

Thank you!