Ah, yes, that is potentially a stumbling block... port property is optional, if not specified, NodeBB will listen on port 4567. However the url property is the one that is referenced by NodeBB, and is used as the canonical reference to itself... so when somebody asks your forum what it is to be called, NodeBB will respond back with the value in url, so the port is required if you are accessing your forum with port number in url.
Solved topics.getTopic error
-
I start a reply on a topic (and before finishing and sending it) and when I either refresh the page or go to another topic, I keep getting this error on each page:
-
Thanks for reporting, fixed in https://github.com/NodeBB/NodeBB/issues/10163
closed drafts using removed socket method topics.getTopic #10163
-
@baris it looks like we are having some problems updating our "favicon" as well. It goes back to normal...
Is it normal to have these links, when we have our NodeBB installed as a subfolder?
-
Are you saying it reverts back to the old value after you save and refresh the page?
-
@baris said in topics.getTopic error:
Are you saying it reverts back to the old value after you save and refresh the page?
yes, I even deleted favicon.ico file from ACP... and uploaded our favicon icon again... we still only see the default one (like this forum).
-
(https://yesilkartforum.com/forum/assets/uploads/system/favicon.ico)
This file needs to show the one you upload, it might be getting cached by nginx and nodebb, so try restarting both.
-
@baris said in topics.getTopic error:
(https://yesilkartforum.com/forum/assets/uploads/system/favicon.ico)
This file needs to show the one you upload, it might be getting cached by nginx and nodebb, so try restarting both.
yes, nginx restart solved the issue. Thanks
-
Topic has been marked as solved
crazycells
