When I want to import the XML files with the aid of the WordPress Importer plugin, the blogs imported will lose all the slashes, i.e., "\", which are really contained in the XML files imported.
Since I have to use the LaTeX plug-in (Latex for WordPress plug-in), it becomes terrible.
In fact, maybe weeks ago, it worked well. There was no such problem at all. But from one day, I find that all changed. TT
Is there any one who know what's happening? Thank you very much!
The importer calls wp_insert_post() which runs stripslashes_deep() on the data. But the exporter doesn't run addslashes. Looks like a bug to me.
What you may try is to prepare the data during export.
Create a plugin with the following content and activate it before you run the export:
<?php
/**
* Plugin Name: Slash my export
* Description: Adds extra back slashes to exported data.
*/
add_filter( 'the_content_export', 'addslashes' );
add_filter( 'the_excerpt_export', 'addslashes' );
I have not tested this, it may be wrong, it may have side effects. stripslashes_deep() may eat the extra slashes too …
You should open a bug on Trac if this plugin fixes your problem.
addslashes before the slashes are stripped … which happens very early. Because once they are removed there is no way to say where they should have been preserved. Changing the export is much easier.
addslashes() to begin with.
Commented
Feb 2, 2017 at 5:13
The missing backslash issue was reported to WordPress here:
https://core.trac.wordpress.org/ticket/21007
and mostly fixed in 0.6.3:
https://wordpress.org/plugins/wordpress-importer/#changelog
Unfortunately, the fact that backslashes are missing in comments as well was not reported and has not been fixed. I've submitted a pull request that I hope will fix it:
https://github.com/boonebgorges/wordpress-importer/pull/6
Note that the plugin also has a new bug that assigns an Uncategorized category to every post even if it does have a category. That's not related to this question, but it's something to note if you are considering using this plugin. Discussion here:
https://core.trac.wordpress.org/ticket/39301
Update
The fix for backslashes in comments should be in the next minor release, 0.6.4:
I recently ran into this problem as well, and came up with an a solution that worked for me. In your wordpress install folder, browse to the subfolder wp_includes and open post.php. My version contained the line:
$data = wp_unslash( $data );
(The wordpress function reference manual says that wp_unslash is the replacement to the deprecated stripslashes_deep(), so in an older version of wordpress it may be using stripslashes_deep instead of the command above.)
I commented this line out, re-imported, and all my LaTeX backslashes were there. Hope this helps.
I found it ended up being easiest to just do a global search and replace for single backslashes to double backslashes in a text editor. I was worried it might escape some important stuff in the XML, so the following bit of PowerShell will tell you the XML tag that surrounded your backslashes.
$r = Select-String '<([^>]*)>.*?\\.*?\1' .\wordpress.2015-09-13.xml -AllMatches
$matches = $r | % { [PSCustomObject] @{ Tag = $_.Matches.Groups[1].Value; LineNumber = $_.LineNumber; Line = $_.Line } }
$matches
In my case, all (except one) were HTML tags from the post content itself.
PS> $matches | Foreach-Object Tag | Sort -Unique
/font
/SPAN
BR
content:encoded
div
font color="#000000"
FONT face="Courier New"
FONT face=Times color=#000000
LI
P
span style="color: "
span style="color: #000000"
SPAN style="COLOR: #006400"
span style="color: #cccc66; background-color: #012456"
SPAN style="COLOR: blue"
SPAN style="COLOR: green"
SPAN style="COLOR: maroon"
wp:comment_author
I took a look at the wp:comment_author post (somebody had backslashes in their name), and their name imported fine into that post.
