Backups created by this plugin have this at the top of the .sql file<\/p>\n
That kills all emojis during imports (e.g. Replacing the offending line with <\/p>\n fixes the problem. I do want to add that emoji’s are getting more prevalent – even in business copy. So this was an issue for us till we dug deeper.<\/p>\n","protected":false},"template":"","class_list":["post-10816734","topic","type-topic","status-publish","hentry","topic-tag-emoji"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10816734","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":1,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10816734\/revisions"}],"predecessor-version":[{"id":10816739,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/10816734\/revisions\/10816739"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=10816734"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\/*!40101 SET NAMES utf8 *\/;<\/code><\/p>\nsource <backup.sql>;<\/code>). Note that the generated backup SQL file has<\/strong> emojis and even tables within are fine (they are CHARSET=utf8mb4 COLLATE=utf8mb4_unicode_ci<\/code>). It’s just that that offending line clobbers emojis during the INSERT operation inside the backup script.<\/p>\n\/*!40101 SET NAMES utf8mb4 *\/;<\/code><\/p>\n