Changes between Version 3 and Version 4 of Ticket #36456, comment 5
- Timestamp:
- 08/19/2016 02:38:48 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #36456, comment 5
v3 v4 3 3 Just imagine a popular site, with an uncached frontpage, displaying full content posts, each containing multiple Instagram oEmbeds with Emojis ;-) 4 4 5 Note that the Instagram oEmbeds can contain other invalid chars than just Emojis, so I ended up using {{{mb_convert_encoding()}}}, like mentioned here: http://stackoverflow.com/a/34640424/2078474 5 Note that the Instagram oEmbeds can contain other invalid chars than just Emojis, so I ended up using {{{mb_convert_encoding()}}}, like mentioned here: http://stackoverflow.com/a/34640424/2078474, instead of using {{{wp_encode_emoji()}}}. 6 6 7 7 8 Then JetPack complicated things further, because it's using it's own Instagram handler, if I remember correctly. I therefore had to unload it through the {{{jetpack_shortcodes_to_include}}} filter, to be able to apply the {{{mb_convert_encoding()}}} to fixthrough the {{{oembed_result}}} filter.8 Then JetPack complicated things further, because it's using it's own Instagram handler, if I remember correctly. I therefore had to unload it through the {{{jetpack_shortcodes_to_include}}} filter, to be able to apply the {{{mb_convert_encoding()}}} convertion through the {{{oembed_result}}} filter. 9 9 10 10 Even if we strip the invalid chars from the fetched Instagram HTML, the javascript part will display it correctly.