rofl. this is how I talk in real life, of course.
SOLVED Cant uninstall nodebb-plugin-emoji-extended clearly.
The nodebb-plugin-emoji is not working. Console shows that nodebb-plugin-emoji-extended (Uninstalled) cause this problem.
Please help me. Thanks a lot
Have you run
./nodebb buildand restarted nodebb?
@pitaj Sure, still no working.
Anyone help me plz!
Dravere last edited by
How did you uninstall it? Could you execute the following commands in your NodeBB root folder? You should stop NodeBB before running these.
./nodebb reset -p nodebb-plugin-emoji-extended npm uninstall nodebb-plugin-emoji-extended rm -r ./node_modules/nodebb-plugin-emoji-extended ./nodebb build
This should remove anything related to
nodebb-plugin-emoji-extended. Otherwise additional information might be needed. Like from where is the error actually coming?
Xuchenhao last edited by Xuchenhao
@dravere I have tried these command. But still no working. The error still there. Emoji cant show.
If the emoji works, we can see this window from compose.
But we cant see this window, and get wrong from console.
I have tried to build the assets.
This is the version of my plugin.
Although I have uninstalled the plugin. But I still can find some files from Web console. Such like these:
But I cant find any file on my nodebb folder.
@xuchenhao that node_modules directory you see is a virtual directory. It's in italics because it's from sourcemaps.
Anyways, please try running
./nodebb stop && ./nodebb build && ./nodebb startand see if that is still there. You shouldn't have anything from emoji-extended. Also, try clearing your cache or trying a different browser, that might be an issue as well.
@pitaj The command I have tried. Shift + Ctrl + N for Chrome
Still can see this menu. How to check the sourcemap?
@xuchenhao I just checked your site myself, and
emoji-extendeddoesn't show up for me. So it's definitely an issue with your browser or some other cache layer
@pitaj I delete all the files. And clone a new Nodebb. Install for clean. Then it doesnt show.
@xuchenhao ah ok. Well, I'm sorry you had to do that.