There recently has been an issue publishing a post to one of your GMB locations: Failed to create/update post: Request contains an invalid argument. [3]Image format is not supported. Field: photos.additional_photo_urls
I’m having to manually post after publishing my blog post. This used to happen automatically. I’ve not changed anything. I’ve been posting WebP without issues for ages until this started happening. Any advice appreciated.
Sorry to hear your posts are no longer being automatically published. This could potentially be related to the 3.3.4 update that was recently released. It introduced some improvements to the way the plugin handled large-scale WebP and Avif images, which previously would result in an “image too large” error.
Could you share the image URL and “original image”-URL of the image of one of the affected posts? You can find these in your Media Library by clicking on the image, and then copy the value from the “File Url” field, and right click on the “Original Image” link > Copy Link, and paste both here. That way I can try to replicate the error.
How are you attaching the image to the GBP post? Are you using the “Auto-post” feature and having the plugin automatically fetch the image from the WP post, or are you manually creating the GBP post through the plugins’ post creation metabox?
The only way I was able to replicate the error is if I manually enter the image URL into the “Insert from URL” field when selecting an image. Which makes sense, because the plugin will treat it as an externally hosted image, and not convert it from WebP to PNG to meet GBP requirements.
I’ve checked the related code in the latest update, and I don’t see any way it could affect the plugin behavior in your specific case. Have you made any changes to your workflow, or any major changes to the website?
I’m just using the auto-post feature, as I’ve always done without issue before. I was using autopublish without issue until a few weeks ago (possibly coinciding with this update). When it fails to publish I use the manual option which then publishes fine.
Thanks for the full error message, it actually brings up an interesting anomaly. The image URL from the error message returns a 404 “not found” error, while the (seemingly) same image URL from your previous message works fine.
I’ve put the URLs side by side but can’t spot a difference between them. But it’s probably an URL encoding issue somewhere in the chain.
So you’re initially publishing the post using Auto-post -which fails to publish- and then you manually edit the failed post within the plugin, by selecting the same image directly from the media library, and then it goes through?
I’ve just put them side by side too and cannot spot any difference!
When autopublish fails I am using the GMB element on the post composition page:
The most recent two posts here are, in reverse order, published without manually adding image and published with the manual addition of the image. I don’t seem to need to add the image manually for this, %post_content% seems to pick it up.
It definitely looks like an encoding issue, I took a closer look and there is a difference if you right click on the links, hit “Copy link” and then put them side by side in a text editor:
In the “Advanced post settings” of the auto-post template (Post to GMB > Settings > Auto-post settings), what do you have configured for fetching the post image? (use featured image/fetch from post content?)
I’m just trying to understand the path the image takes and where in the chain it goes wrong.