iacas Posted March 7, 2019 Share Posted March 7, 2019 :D :) Aren't being auto-replaced anymore despite the setting being turned on, plus where did all of my emoji (like :man_facepalming:) go? This is true even here at IPS, so it does not appear to be an issue with my site. Where are the rest of the emoji???? Link to comment Share on other sites More sharing options...
iacas Posted March 7, 2019 Author Share Posted March 7, 2019 I sure as heck hope this bullet point isn't responsible: Quote Removed EmojiOne-style emojis due to licensing issues. from: https://invisioncommunity.com/release-notes/440-r81/. Link to comment Share on other sites More sharing options...
Clover13 Posted March 7, 2019 Share Posted March 7, 2019 Dang, you run The Sand Trap? Nice! The bullet point you linked is exactly what came to mind. What is set in your Customization >> Editor >> Emoji >> Standard Tab after the upgrade? I haven't upgraded yet but I'd imagine the Twitter style is still available, does that will work as an immediate substitute? Also check if the "Replace text with emoji?" option is ON Link to comment Share on other sites More sharing options...
iacas Posted March 7, 2019 Author Share Posted March 7, 2019 I've toggled them off and back on with no change in the behavior. Those are emoji, too, showing there - it's not an image. Native emoji should work. It's from the user's device - it shouldn't be EmojiOne or anything. Link to comment Share on other sites More sharing options...
Clover13 Posted March 7, 2019 Share Posted March 7, 2019 Hmm definitely looking like a bug on auto-replace (since it exists here too). You don't have an Emoticons section at the bottom of your Emoji popup when you scroll to the bottom? Assuming that's where your custom :man_facepalming: would be. Link to comment Share on other sites More sharing options...
iacas Posted March 7, 2019 Author Share Posted March 7, 2019 14 minutes ago, Clover13 said: Hmm definitely looking like a bug on auto-replace (since it exists here too). I think it's simply not replacing :) and :D and =) and things like that… because they don't exist anymore. The emoji set is vastly, vastly shrunk/compromised. 14 minutes ago, Clover13 said: You don't have an Emoticons section at the bottom of your Emoji popup when you scroll to the bottom? Assuming that's where your custom :man_facepalming: would be. I do, which we retain for backward compatibility when forums had to supply their own emoji, but :man_facepalming: was not a custom emoji. It's a standard emoji. https://emojipedia.org/man-facepalming/ Link to comment Share on other sites More sharing options...
Clover13 Posted March 7, 2019 Share Posted March 7, 2019 Auto-replace does work here for some like 😄 :D and 😉 ;) Link to comment Share on other sites More sharing options...
iacas Posted March 8, 2019 Author Share Posted March 8, 2019 :) :D ;) :P Link to comment Share on other sites More sharing options...
iacas Posted March 8, 2019 Author Share Posted March 8, 2019 Something changed, both here and at my site, because now the popup menu has all of the normal emoji, and now after reloading the page I too can get these to replace - 😄 😛 🙂😉 etc. Link to comment Share on other sites More sharing options...
Clover13 Posted March 8, 2019 Share Posted March 8, 2019 I was on Windows before, I'm on MacOS now. The Native emojis changed here...I'll have to look on Windows later to verify the native is/was showing. At one point the replacement wasn't happening though, just as you experienced. Link to comment Share on other sites More sharing options...
bfarber Posted March 8, 2019 Share Posted March 8, 2019 The emojis that are supported will vary depending upon your operating system/user agent FWIW. We did not remove emoji support (or support for any specific emojis) - we only removed support for using EmojiOne images to represent the emoji that were posted, due to licensing concerns. Link to comment Share on other sites More sharing options...
iacas Posted March 8, 2019 Author Share Posted March 8, 2019 In trying some other browsers and computers, the problem seems to be localized to one specific instance. It just so happened that this browser, which worked fine on 4.3.6, behaved funny after upgrading to 4.4.1. I'll reboot and troubleshoot from there, but other browsers even on this computer are fine, and this same browser and OS on other computers is fine, so I think it'll work itself out. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.