Error: File attachment metadata error

At the moment, no idea unfortunately. Since this is the only report of this error, it may be something very specific to your WordPress installation. Let’s wait and see if others also have this issue.

OK, so I digged a little bit deeper into it and have some new insights.

The URL the plugin will obtain is
https://pixabay.com/get/eb36b9062bf51c3e81584206e24b5b97e676e3d71cb619439d_1280.jpg

In my desktop browser it works and shows me a fellow dragon.

But my server, or much rather wp_remote_get() (pixabay-images.php line 198) says the URL 301ses to
https://braxmeier.com/get/eb36b9062bf51c3e81584206e24b5b97e676e3d71cb619439d_1280.jpg

which gives me a Bad Request (400). In both WordPress and my desktop browser.

If you could have a look into that since the 301 is on your end and out of my scope, I would appreciate.

Here’s the pastebin of the complete response including the initially called URL:
https://pastebin.com/QE5zNwW6

Thanks,
Alduin

Same problem here. Since yesterday.

M.

Why is that labeled as “resolved”? Problem persists.

Well, technically, it’s another error right now (timeout because braxmeier.com takes longer than timeout), but it still eventually gives HTTP400 and thus the error above.

Alduin

Hello,

we’ve got the same trouble like Alduin. It would be great if you could fix this issue as fast as possible.

Thanks.

Cheers

TechnikSurfer

I was having this issue as well. The plugin is intentionally avoiding HTTPS for some reason, and the Pixabay server seems to be intermittently throwing Bad Request (HTTP 400) errors on the non-secure https:// URLs.

The following change should stop the Pixabay plugin from forcing non-secure image download URLs.

In pixabay-images.php, replace line 190:

$url = str_replace('https:', 'http:', $_POST['image_url']);

with:

$url = $_POST['image_url'];

THANK YOU @dancriel!

That fixes the problem.

@simonstone
Please apply this patch to the plugin and release an update ??

Alduin

Hmm, no idea why we converted the URLs there. Doesn’t make any sense to me now. We’ll remove this line with the next plugin update.

Thanks a lot, dancriel!

Update is on the way. Tested up to WP 4.9 and this update additionally includes an optional SafeSearch filter.