No problem dude !
I hope you have a good vacation. Enjoy your loved ones!
here a gif for the problem of perf.
On a clean install of nodeBB on a clean install server VM
The problem is just when I refresh the page entierly or ACP access
No problem on 1.18.x or 1.19.2
very odd
@DownPW Looks like that’s waiting for a response from something. Have you run this site through the F12 developer tools -> Network tab to see where the delay is ?
@DownPW 8ms is nothing - less than one second… ?
you not see at the good place
EDIT:
coincidence? Emoji CSS failed !
I don’t believe
I think we put the finger on something
@DownPW Yes, you’re right. For some strange reason, that CSS file is not being served - but should be on your server if you check the path.
yes it still here
EDIT:
I have remove the directory when I have the problem of install with 1.18.x
But when I upgrade to 1.19.3, he have reinstalled by default
@DownPW I see this
@phenomlab on your website ?
@DownPW No - on yours.
ha lol ok
because you are guest maybe because not me
test admin:nodebb
@DownPW Same error when logged in
yes I think there is a problem with that plugin.
Maybe open a topic with this on nodeBB communauty
@DownPW agreed. What happens actually if you change the loading order of that plugin ? You can do that from the ACP -> Plugins
I put emoji plugin on first load and this :
@DownPW makes no difference then.
yes
The path doesn’t exist (Assets/plugins/…)
EDIT:
Sorry Existing path:
http://192.168.1.53:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u
I find the problem Mark
The error message indicated this path :
http://localhost:4567/assets/plugins/nodebb-plugin-emoji/emoji/styles.css?v=6983dobg16u
I change the path url on config.json
And all it’s good
Weird, I didn’t have to change that path before 1.19.3
But this does not prevent the problem from a clean install with Emoji Plugin
EDIT: After test, that resolv the problem installation for 1.18.x but not for 1.19.x (I have other error message when I run ./nodebb Setup
For resume: NodeJS 16_x with 1.18.x is ok