Opened 7 months ago
Last modified 7 days ago
#52840 accepted enhancement
Include filesize information in REST API response for all media types
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 5.9 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | REST API | Keywords: | has-patch needs-unit-tests |
| Focuses: | rest-api | Cc: |
Description
Requesting the /media REST API endpoint, only audio attachments include filesize information in the response data (in media_details->filesize).
I suggest to check for each item if filesize is present, or else fill it in using the actual file. This would be pretty much in line with what is done in wp_prepare_attachment_for_js.
Making the information available locally, when creating the response data, is much more performant than having to request the file in one or more follow-up requests.
Attachments (2)
Change History (8)
#1
@
7 months ago
- Keywords needs-unit-tests added
- Milestone changed from Awaiting Review to 5.8
- Owner set to rachelbaker
- Status changed from new to accepted
This ticket was mentioned in Slack in #core-media by spacedmonkey. View the logs.
5 months ago
#3
@
5 months ago
- Milestone changed from 5.8 to 5.9
Today is 5.8 feature freeze. Unfortunately this one ran out of time.
Punting to 5.9 as there has been good recent momentum.
This ticket was mentioned in Slack in #core-restapi by spacedmonkey. View the logs.
7 days ago
#6
@
7 days ago
This ticket was discussed in this week's REST API meeting.
In short, making filesize calls in the rest api, will likely come with some overhead. For example those storing files on NFS or S3, will like need to ping an external resource to get file information, slowing down the response.
Until file sizes are "cached" somehow ( see #49412 ), this ticket should be marked as blocked.
Formatting