upgrading from 2.8 to 3.3.9, emojis are missing
-
You probably need to update the URL value in config.json to match the URL at which you access your forum.
-
@sharonyue it's probably just cached or something, try a different browser or clearing your cache
-
I tried using different PCs and phones. It has the same issue. By inspecting Chrome, it says:
It ends up with 'jml6cffvsrs', I dont know what it is. But actually my gif also end up with that.
The above gif does not show properly either in this forum. But you can see the gif if you open it in another tab.
-
The
?v=
doesn't matter. Do other emoji images have the same problem? May just be a problem with that particular image. You say it's a gif, but it has a.png
extension. Maybe that's the issue? -
Do other emoji images have the same problem?
All emojis dont work.
Some are gifs, some are pngs, all has this issue. I think in this forum, it also has this issue. Please try the following code:
![alt text](https://cfd-china.com/assets/plugins/nodebb-plugin-emoji/emoji/customizations/a79385b3-59f6-45c4-9d12-067470db946a-a32fa0401075cb4c65afa559cb0bb7f2.png?v=jml6cffvsrs)
The code above does not show the png. But if you open it in a new tab. We can see the png.
-
@sharonyue the image is not loading here because of a NotSameOrigin error, so a different reason entirely.
In this topic on your forum the main post has a
:baobao:
emoji that appears to be working just fine.Is that one working on your end?
-
@PitaJ Oh, thanks for debugging it deeper. That one works for me. Even I did not notice this. But the others dont work .See this one. Thanks.
I added
:baobao:
in this link text, it does not work either. So some works, some does not work? -
@sharonyue can you share the exact markdown of that post? It doesn't appear to have been parsed as an emoji.
Maybe try changing the priority of the emoji plugin. It should be after markdown.
Edit: at first the image didn't load but now it is, not sure what the problem is. Seems like the browser thinks the image is cross-origin when it isn't.
-
@PitaJ This is my post.
nice!说的太好了!!! :146: :146: :146: :146: :146: :146: > 要求达到建筑物位置的湍流风场特性与风洞试验一致,才能得到精度较高的复现结果 这方面有sci做对比么,竟然有这么大的差异。那要是差异很大,确实需要好好研究下进口了。 ![:baobao:](https://cfd-china.com/assets/plugins/nodebb-plugin-emoji/emoji/customizations/2668306c-43ff-42b9-a42a-d9080357c5b6-c5c446676f124dd61d1247e8656d6bb3.png?v=akh24mtahoq)
-
@sharonyue NodeBB doesn't support accessing from multiple URLs. Instead of serving it on both
example.com
andwww.example.com
, redirect one to the other. -
@sharonyue it will be in your reverse proxy config, such as nginx.
-
@sharonyue yes.
-
@sharonyue said in upgrading from 2.8 to 3.3.9, emojis are missing:
so that means my emoji's address start with "xxx.com", so in "www.xxx.com", my emojis wouldn't show up?
Um..This is not the case for nodebb-v2.
Is there an easy way to do it in nodebb-v3?
-
@sharonyue I can assure you that NodeBB has always only supported a single URL since the beginning. It may be that recently something else changed either in NodeBB or in browsers that made cross-origin images not show up.
But the solution is quite simple: just make
www.example.com
redirect toexample.com
in your reverse proxy config. Having a single canonical URL is better for more reasons beyond just working correctly with NodeBB.