#4028 closed defect (bug) (fixed)
Importing WXR breaks serialized postmeta value
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | low | Milestone: | 2.2 |
| Component: | Administration | Version: | 2.2 |
| Severity: | normal | Keywords: | import has-patch WXR |
| Cc: | JonathanRogers |
Attachments (2)
Change History (9)
takayukister — 6 years ago
comment:1
foolswisdom — 6 years ago
- Milestone changed from 2.3 to 2.2
comment:2
foolswisdom — 6 years ago
- Keywords WXR added
Actually, nothing passed to add_post_meta should be escaped. Unlike most other functions, add_post_meta does it's own escaping. I think we just need to stripslashes() all postmeta values before handing off to add_post_meta.
- Resolution set to fixed
- Status changed from new to closed
comment:5
JonathanRogers — 4 years ago
- Cc JonathanRogers added
- Resolution fixed deleted
- Status changed from closed to reopened
- Version changed from 2.2 to 2.8.3
Unfortunately, this bug seems to have been re-introduced by Ticket #7347. Now, serialized post meta values are doubly serialized after importing. Since Ticket #7347 indicates there might be some reason for maybe_serialize() to doubly serialize (though I can't fathom what it might be) and add_post_meta() calls maybe_serialize(), I'm not sure where this should be fixed.
- Resolution set to fixed
- Status changed from reopened to closed
- Version changed from 2.8.3 to 2.2
I think this would be better off in a new ticket JonathanRogers.
I'm going to reclose this, Could you open a new ticket related to it in the current version?
comment:7
JonathanRogers — 4 years ago
OK, the new one is Ticket #10619

I wrote a patch whitch try to unserialize.