This may be an issue with Discourse, as opposed to the plugin.
If you’re using the default Wordpress emoji handling, I’m assuming you’re copy/pasting unicode emojis into the wordpress editor. If you do this the raw post content sent to discourse will just include the unicode emojis. Discourse should normally convert those into the emojiset of the forum. I can indeed reproduce the issue in certain circumstances.
On the technical front (as I know you’re technical ), you can see the issue directly if you attempt to use the relevant Discourse ruby class to parse a html string with unicode emojis.
Technical detail of issue
rails c
PrettyText.cook("<p>This is the sentence before the emojis</p><div>🦊🦊🦊🦊</div>")
=> "<p>This is the sentence before the emojis</p><div>🦊🦊🦊🦊</div>"
Generally speaking, some issues in Wordpress full post html > Discourse post conversion are not unexpected. The record of the Wordpress post on Discourse is just that, a record of the post.
That said, @simon and I are actively looking at improving that process in both wp-discourse and Discourse itself, with an appropriate prioritization. We’re going to focus on a few other things in this respect (e.g. the broken images issue mentioned above), before we get to this one. So you’ll need to sit tight for an official fix on this one for a bit.
Hey, just a note that addressing this is on my agenda for June of this year. If anyone has an issue closely related to this, please let me know and I will look at it at the same time.