Opened 15 years ago
Closed 12 years ago
#18060 closed defect (bug) (wontfix)
image upload handling between atompub and xmlrpc different
| Reported by: | rfc1437 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | AtomPub | Version: | 3.2 |
| Severity: | normal | Keywords: | has-patch needs-testing |
| Cc: | Focuses: |
Description
Uploading images via XMLRPC generates different image sizes in addition to the original image. Uploading the same image through AtomPub will only create a single original file in the uploads/year/month/ directory, the thumbnail and different formats normally generated on upload are missing. It is probably because wp_handle_upload is missing from the wp-app.php create_attachment definiition - it only uploads the bits and creates an attachment, but neither handles metadata updates nor image thumbnail generation.
Attachments (2)
Change History (8)
#2
@
15 years ago
Ok, I tested it on my blog with the only AtomPub client I have at hand - the LR/Blog plugin for Lightroom - and it worked now. Since this was the AtomPub client I noticed the problem with, I'd say this patch should do it :) Thanks!
#3
@
14 years ago
- Cc added
- Version 3.2 → 3.4
This is annoying: it still is not fixed with 3.4 and the patch doesn't work anymore now, because the file structure did change. Does anybody ever actually read and work on these tickets?
#4
@
14 years ago
I updated the patch to work with 3.4 - to repeat, the problem isn't missing metadata or anything, the problem is missing image sizes that are normally generated on upload.
#5
@
14 years ago
- Component Media → AtomPub
- Version 3.4 → 3.2
Version number indicates when the bug was initially introduced/reported.
#6
@
12 years ago
- Milestone Awaiting Review
- Resolution → wontfix
- Status new → closed
As AtomPub was removed from core in 2012, see #21866. There is a plugin for it here: http://wordpress.org/plugins/atom-publishing-protocol/.
I doubt anyone really interfaces with WordPress via AtomPub anymore. Did anyone ever truly use it? I heard that when WordPress.com had it enabled, a few dozen posts came through it a day, all from few clients.
So realistically, AtomPub is essentially considered "end of life" to us. This plugin was merely done for backwards compatibility.
Closing this ticket as wontfix.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
The AtomPub code looks rather unloved, following patch brings it more in line with
media_handle_upload()and adds image exif/iptc data checks and metadata updates and sizes.I haven't got an AtomPub client to test with though.