-
Notifications
You must be signed in to change notification settings - Fork 239
Labels
🚦 status: awaiting triageHas not been triaged & therefore, not ready for workHas not been triaged & therefore, not ready for work🛠 goal: fixBug fixBug fix
Description
Description
When I retrieved the images via the REST API, I noticed that some of them were inaccessible due to a 410 error. WordPress block editor gets the image list to be inserted into the content via the endpoint, but some images aren't inserted due to the HTTP error above.
Reproduction
- Access https://playground.wordpress.net/ to start the WordPress instant environment
- Go to the Dashboard > Create a new post > Open the main inserter > Click the Media tab > Click the Openverse menu
- Search images by "mountain"
- You should see that some images have no preview.
- Click them. Browser console outputs the 410 (Gone) error and the image isn't inserted.
Request example:
Screenshots

Additional context
We may be able to filter out the broken images on the client side, but I'd appreciate it if I could know why the broken images are included in the first place and if there is an option to filter them out.
Metadata
Metadata
Assignees
Labels
🚦 status: awaiting triageHas not been triaged & therefore, not ready for workHas not been triaged & therefore, not ready for work🛠 goal: fixBug fixBug fix
Type
Projects
Status
🏗 In Progress