Opened 15 years ago
Last modified 7 years ago
#19764 new defect (bug)
Invalid JSON in custom fields meta value after export
| Reported by: | abdessamad idrissi | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Import | Version: | 3.3 |
| Severity: | normal | Keywords: | needs-patch |
| Cc: | Focuses: |
Description
Hey there,
I exported a working copy of my online WordPress site to a local copy and noticed that the code gets changed; The backslash is removed which causes the json format to be invalide.
Original code in the custom fields meta
{"videos":{"0":"<iframe width=\"480\" height=\"360\" src=\"http://www.youtube.com/embed/YAozOaxXYx4\" frameborder=\"0\" allowfullscreen></iframe>"}}
Becomes in the local site after import
{"videos":{"0":"<iframe width="480" height="360" src="http://www.youtube.com/embed/YAozOaxXYx4" frameborder="0" allowfullscreen></iframe>"}}
Change History (6)
#2
follow-up:
↓ 3
@
15 years ago
I think it has to do with the WordPress import utility because when I check the exported XML file I find the backslashes there.
#3
in reply to: ↑ 2
@
15 years ago
- Component Export → Import
- Version 3.3.1
Replying to abdessamad idrissi:
I think it has to do with the WordPress import utility because when I check the exported XML file I find the backslashes there.
Yep. The importer uses add_post_meta() which calls add_metadata() which strips slashes from the value.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
This is probably caused by
stripslashes_deep($meta_value)in add_metadata().