[nodebb-plugin-emoji-extended] Emoji Extended
-
Yeah, I was making assumptions since it was showing up properly in my 0.5.7 ACP and disappeared from 0.6.0. I also had to remove it to get 0.6.0 to start (was causing an error, due to the plugin changes in 0.6.0, I assume) so I figured it just wasn't available for the new version. But you're right and installing through the command line works flawlessly. Thanks!
-
sorry, must have missed the posts of @Ted and @Andrea-Cardinale 21/18d ago.
@Ted is correct. The
0.4.1-x
versions are supposed to work with (and only with) NodeBB0.6.x
. They're published since Nov, 21 '14 so technically it should be fine at all.I've just manually confirmed the support within the NodeBB Package Manager, so I hope that helps the plugin to appear in ACP. Give it some hours thought.
EDIT: Even the suggestion works like a charm, so it's pretty clear it's just missing on the plugins-list
-
@frissdiegurke maybe this is of use to you: http://hassankhan.github.io/emojify.js/
-
added version
0.4.2-1
for NodeBB0.7.x
- split emoji-modal into tabs rather than displaying all at once
- using
0.7.x
way to add composer-button - fixed help-message
-
Bringing this one back to life. @frissdiegurke, best way of changing existing posts that reference http:// to https:// now that I've got an SSL Certificate. As it's giving warnings as old posts were saved with http:// before I had an SSL Cert.
-
@a_5mith As long you change the
url
within the config, it should work fine. All parsing steps AFAIK happen when a client requests a post.
Maybe it just needs a restart? -
Speaking of which, any particular reason it uses absolute urls in reference to the emojis? I'd assume
nconf.get('relative_path') + '/plugins/nodebb-plugin-emoji-extended/emoji/' + emoji + '.png'
would be sufficient?Also, any luck updating the plugin to vanillajs?
-
I guess I should use
relative_path
xD have taken this the whole way from its originsActually great timing for the second question, I've just started working on the rework again (@a_5mith already triggered this burst in motivation)
PS: It's not about just updating to plain js but rather about a whole rewrite with many improvements such as different sets to choose from, custom sets, modulating markdown related code, etc., etc.
-
@julian said:
Speaking of which, any particular reason it uses absolute urls in reference to the emojis? I'd assume
nconf.get('relative_path') + '/plugins/nodebb-plugin-emoji-extended/emoji/' + emoji + '.png'
would be sufficient?I finally remember, where absolute url is needed: emails Since the emoji are being parsed in emails, it needs to be absolute