Wrong export/import of Gutenberg post_content

[manake]

Exporting Gutenberg content via get_posts and then importing via wp_insert_post doesn't work. I also do json_encode and json_decode.

The problem is that -- is converted to \\u002d\\u002d.

"post_content": "<!-- wp:slug\/some-block {\"someAttributeOfThisBlock\":\"someValue\"} \/-->\n\n<!-- wp:slug\/some-other-block {\"someProp\":1234,\"someOtherProp\":\"xyz\",\"className\":\"x-y-z-a-b\\u002d\\u002dc\"} \/-->",

[manake]

This is not solved in 4.0 RC-1:

#9991
#9929
#7308
#9423

I still have these two problems:

• 4.0 RC-1: className is not loaded back (Edit: It's loaded back when class names are like one two so it's only the problem with dashes it seems. Edit 2: I think it was a caching issue. When JS reloaded after I updated to 4.0 RC-1 then classes are loaded now. So only the other issue remains.)
• 4.0 RC-1: Two dashes in className are saved in such way that export/import doesn't work.

[designsimply]

Are the steps to reproduce and code snippet at #9423 (comment) still relevant for testing for this case? I see that it was recommended in that discussion to use the forums or Slack for detailed technical questions and I also see you had further questions there about trying to double check whether it's really a bug or not.

[manake]

This is already solved for me: #9423 (I updated my above comment before you replied which says that this is no longer the case in Gutenberg 4.0 but it is the case in 3.9. I updated to 4.0 after I wrote this ticket and then I made a correction).

So this is the only problem that remains:

1. I can't do get_posts() and wp_insert_post() when two dashes are used next to one another in className.
2. To me it's not usable and it's a bug.

Solution:
On exporting the post double dashes must remain this: x-y-z-a-b--c and not this: x-y-z-a-b\\u002d\\u002dc (this is with json_encode() applied so the original is probably x-y-z-a-b\u002d\u002dc).

When I manually update x-y-z-a-b\\u002d\\u002dc to x-y-z-a-b--c then I can confirm that importing works via wp_insert_post(). So, it's a problem with export only.

[youknowriad]

I suggest creating a Trac ticket as it seems that the error is in the php functions used here.