Opened 18 years ago
Closed 17 years ago
#4242 closed defect (bug) (fixed)
Export function does not define comments as CDATA
Reported by: | ionfish | Owned by: | westi |
---|---|---|---|
Milestone: | 2.5 | Priority: | normal |
Severity: | normal | Version: | 2.3 |
Component: | Administration | Keywords: | has-patch needs-testing |
Focuses: | Cc: |
Description
Because comments aren't defined as CDATA, if they contain invalid characters (which is likely, given the public nature of comments) then data can be lost when the XML file WordPress generates is imported into a new database.
Attachments (2)
Change History (7)
#3
@
17 years ago
- Keywords needs-testing added; export comments CDATA removed
- Owner changed from anonymous to westi
- Status changed from new to assigned
Current patch doesn't apply
Uploading updated patch.
However a quick test of export from trunk with this change and import into branches/2.3 failed so this may need more work on the import side?
Note: See
TracTickets for help on using
tickets.
Here is a patch, witch adds the post content, the comment content and the dc:creator fields as CDATA sections. Are there any other that should be treated this way?