In a discussion about the vBulletin Emojis plugin for Discourse, cpradio introduces a plugin to revive classic vBulletin-style emojis — many animated — which coexist with modern Emojione sets without conflict. codinghorror notes that Discourse 1.2 will support custom emoji from Apple, Google, and Twitter, but cpradio argues the vB emojis have a nostalgic, distinct aesthetic that doesn’t fit modern styles. Humor ensues, including playful jabs and emoji-laden replies codinghorror and cpradio. Later, users report the plugin is broken in recent Discourse versions (e.g., 2.5.0.beta2) Hifihedgehog. Steven explains the breakage stems from new emoji group features, suggesting a fix via register_emoji in plugin code, but notes caching issues remain unresolved. cpradio offers to add Steven as a contributor to the repo. Debugging reveals a NameError: uninitialized constant Plugin::Instance::Emojicpradio, which j.jaffeux resolves by wrapping register_emoji in an after_initialize block — a fix cpradio confirms works. sunjam asks whether to import all emojis directly or split into separate plugins; tom1984 questions if native custom emoji now support animation, noting they’ve worked well for 20+ years. Steven confirms some GIFs work, and tom1984 shares success using built-in custom emoji with CSS resizing for proper aspect ratios, citing meta.discourse.org.
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.