For anyone who wants to relive the old days of vBulletin and bring back those emojis, have a look at the following plugin (and yes, several of them are animated)
Oh, and they do not interfere with the existing emojione emoticons, as these are all prefixed with ‘vb-’ https://github.com/cpradio/vb_emoji
A big thanks goes out to @eviltrout for his emoji extender!
Yes, that looks really neat (btw). The vB ones really don’t fit in with the Google/Apple/Twitter… ones, so I see this still being the easiest way to quickly bring in the vB emoticons, but I do like the progress that was made here within Discourse.
Well aware of that. As you are aware that the opinions of others are the existing ones don’t really fit in anywhere… So the opinions are mutual across both sides. I personally don’t care enough one way over another, I simply created the plugin as 1) a test to get used to the plugin framework, and 2) because I know our forum specifically wants it.
PSA: This plugin in the last few weeks has become broken with the latest release of Discourse, 2.5.0.beta2. Bye, bye, vbulletin emoticons. It was nice knowing ya. :’(
The plugin can be updated, the plugin is broken because of a great new feature that allows the creation of new emoji groups but we still can register new emojis via plugin
Thanks, @Steven. I see @cpradio is still active visiting the forums here, as of 3 days ago. If he doesn’t reply in a week, is it kosher if I fork his plugin (duly credited) using the fix you mention above?
@Steven, if you want, I can add you as a contributor to the existing repo. More than happy to share the responsibility. Sadly, it will take me awhile to get a dev environment built for discourse again, sadly, I haven’t had time to spend in it so I’ve discarded my setups for awhile now.
Sent you an invite. If there are any others you want to be invited to, let me know. I did get my rig put back together late last night, but that is as far as I got, clean install of Discourse. I plan to look at it again tonight (time willing), worst case, tomorrow night.
This is weird and might not be an issue with the plugin itself. When I do a rebuild on a clean install of Discourse adding my plugin, I get the following error