Importing omits backslashes

[SeMeKh]

If you try to import a previously-exported post containing backslashes, those backslashes will be omitted during the import process.

[SeMeKh]

Patch to fix the omitted-backslashes bug

[SergeyBiryukov]

Confirmed.

[SeMeKh]

The issue is about wordpress-import, I don't know if the same problem exists for other importers.

[daveagp]

This is basic functionality. The patch is simple and worked for me. It's a pseudo-official plugin that is linked to by core code so this is important. Please accept!

[SeMeKh]

18 months, and this isn't fixed yet. And the patch is already there!

What's wrong with Wordpress developers?

[SergeyBiryukov]

Since $postdata is a simple array, I guess we can just use array_map() here: 21007.patch​.

[boonebgorges]

Hi all - Sorry for the delay on this. It does appear to be a bug, for terms as well as for posts. See the tests in 21007.diff​.

Fixed in ​https://github.com/boonebgorges/wordpress-importer/commit/998f7fc75c6916355859b7e791e60b97a3efccdb. This will be part of the next minor release.

[boonebgorges]

In 38283:

Add wordpress-importer tests demonstrating slashed data behavior.

See #21007.

[mcbsys]

Not sure whether to post here or on Github.

In 0.6.3, backslashes are still being removed from comments. I'm not familiar with WordPress code but adding another wp_slash to wordpress-importer.php seemed to fix it:

<?php

if ( isset( $inserted_comments[$comment['comment_parent']] ) )
    $comment['comment_parent'] = $inserted_comments[$comment['comment_parent']];
$comment = wp_slash( $comment );
$comment = wp_filter_comment( $comment );

[ocean90]

Replying to mcbsys:

Thanks for your PR. The fix will be part of the next minor version.

21007.2.diff​ includes a test to verify the issue and the fix.