Www.mysite.com and mysite.com are different domains, you don't want them both available. Redirect one to the other, if you log in on mysite.com and then get navigates to www.mysite.com, you will no longer be logged in.
or so I understand anyway. 🙂
If you go YOURDOMAIN.TLD/admin/extend/plugins#download
and type emoji in Plugin Search field, can't you see the plugin? (be sure to have selected the "Find Plugins" tab)
@greyteapot do not install emoji-extended. It's features are incorporated into the normal emoji plugin and it is outdated and deprecated.
You need to have
nodebb-plugin-emoji installed and enabled. You also need to have at least one emoji pack installed and enabled, such as
nodebb-plugin-emoji-android. Then you need to rebuild and restart.
It should work from there.
I can say I’m encountering this problem also and had not reported it yet. (v1.16.)
Emoji appear as broken links but a single page refresh often bring them back. Sometimes it stops. Then returns as an issue.
They emoji will appear in the menu drop down or auto-fill suggestion, but when the post is commit again broken.
what version of the plugin are you using?
Try Building Emoji Assets from the emoji admin page, waiting 30sec, then running a rebuild and restart.
Initially these 2:
Did many rebuilds both of emoji and forum (1.16) via ACP.
I have uninstalled the Android and I'm trying gout the Apple - https://github.com/NodeBB/nodebb-plugin-emoji/tree/master/packs/apple (2.0.1)
Note: Sometimes I need to refresh the plugins > emoji page in the ACP, to get the "Buil dEmoji" button to do it's thing.
does the apple option work in your forum?
@majr are you still having issues? Any errors in server logs or in the browser? Does the build emoji button complete successfully, showing a success message? What version of Node are you using?
Hey so I also ran the following in the cli just in case:
npm upgrade nodebb-plugin-emoji
I also update npm to version 7.5.3 > 7.5.4
Things do seem more stable but I am not ready yet to pronounce it issue free. Give it 24/48 hours and a checking on few other devices later and I'll update.
Nope this is still behaving strangely.
I have seen a warning in the log about the emoji plugin not being compatible!
Emojis present on first page load as broken images, a page refresh displays them. Navigate away and navigate back and they are broken again.
The Build Emoji button has always completed successfully in my experience.
Sometimes I try then also a full rebuild via the ACP. None of this seems to make a difference.
Finally, I tried to create a custom emoji, while it saved, I had to buy;/restart to get it to appear int he selector panel.
Tried a custom emoji, same deal, it appears as a broken image, refresh's and it's there. Nav away and back to page, all broken again.
Maybe there is something at the nginx level that needs to be addressed.
I could not get it to work.
I get error messages:
When i install the ...android it says to require a peer of [email protected]^2.0.0 but none is installed
I change it - No difference
When I go for apple it says...requires a peer of [email protected]^3.4.2 but none is installed
I change it - No difference
I also have this message but I do not know what it means ???:
BEGIN emojis -->
emojis could refer to the top-level value
emojis or the
.emojis property of the current element, so compiler must emit code for both cases
| note: Migrate to modern syntax to avoid the ambiguity. This will become an error in the future.
@omega I am using nginx as well. What do you suggest could be the Problem?
@omega can you look for 404 errors in your browser console? It sounds like the emoji images are pointing to the wrong place.
@majr it looks like you aren't on the latest version of the plugins. Try this:
npm install [email protected] [email protected] ./nodebb stop ./nodebb activate emoji ./nodebb activate emoji-android ./nodebb build ./nodebb start
You should not see the
require a peer of [email protected]^2.0.0 warning or the
ambiguous inner begin warning. Regardless, these are warnings that you can usually ignore. They're meant for plugin devs, not for users. Also in the future, please share the whole error, not one randomly cut off.
Then Build Emoji Assets from the plugin page, wait 30sec, and do this:
./nodebb stop ./nodebb build ./nodebb start
Yea a ton of errors
FetchEvent.respondWith received an error: TypeError: Not allowed to request resource
Also web socket
wss: connection failures too all resolving to the plugin folders and/or emojis folders/resrouces.
@omega can you share more information? Like a screenshot of your console showing all of the errors?
Or even give me a link to your site so I can investigate.
You think I would have configured this right... the refresh was the clue... I forgot to set the
https in the config.json file... thanks for pointer to look in the browser console! It was easier to observe the flip from
https when refreshing.
Hello, thank you for all your help but it made no difference. I did it exactly as you explained.
I have one error in the console of the browser. Transplated in English
the android plugin says:
"Failed to load resource: The request timed out". That would be a little bit strange.
I wonder why. Is my server too slow to show emojis? I am using nginx.
@majr please provide the full error. Include what resource it says timed out.
Do you have any errors in the server log?
Is your site public? I'd like to see what's going on.