#16280 closed enhancement (invalid)
UI improvements to Themes API
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | minor | Version: | 3.1 |
| Component: | Themes | Keywords: | |
| Focuses: | Cc: |
Description
Following on from #16132, some improvements to the Themes API UI. Here's a patch for one particular issue, but there may be more overhaul for WP 3.2
Attachments (1)
Change History (6)
#1
follow-up:
↓ 2
@
14 years ago
I don't like this patch. As it is, the error message we're sending does very little to explain what went wrong. Providing the raw HTTP error might only make it worse.
These errors, strings, and UX need a real overhaul in 3.2.
#2
in reply to:
↑ 1
@
14 years ago
Replying to nacin:
I don't like this patch. As it is, the error message we're sending does very little to explain what went wrong. Providing the raw HTTP error might only make it worse.
IMO "An unexpected HTTP error occurred" is far less helpful than the original HTTP error. But I agree that the whole thing needs improvement, so maybe minor tweaks isn't the way to go.
Pass on original wp_error when http request fails