#15203 closed defect (bug) (fixed)
Export function does not properly escape ]]> (CDATA)
Reported by: | ceefour | Owned by: | duck_ |
---|---|---|---|
Milestone: | 3.4 | Priority: | normal |
Severity: | normal | Version: | 3.0.1 |
Component: | Export | Keywords: | has-patch |
Focuses: | Cc: |
Description
- Create a post with <![CDATA[ ... ]]> in it (raw form)
- Export the WordPress data as WXR.
The resulting WXR is not well-formed and is not readable.
Attachments (4)
Change History (15)
@
14 years ago
Patch to fix export (this makes WXR readable to XML-compliant importers, but perhaps not WordPress's own importer)
#5
@
14 years ago
- Keywords has-patch added; wxr export cdata escape backup patch removed
I had thought of this whilst preparing for #15197, but obviously forgot about it. Though I cannot reproduce using your steps above, since the >
is encoded as >
in the output file, there is a possibility of this happening in other circumstances (see #15294).
Before this can go in, I believe the regular expression based importer might have to be updated.
#6
@
14 years ago
- Owner set to duck_
- Status changed from new to assigned
duck_ is this ticket still relevant or can it be closed?
Note: See
TracTickets for help on using
tickets.
Related to #7400 (Import hardcodes CDATA syntax)