Możesz zgłosić problem na GitHub (Issues) lub tu na forum ale po angielsku w dziale Bug Reports. Istnieje duża szansa, że ktoś z developerów się nad tym pochyli. Koniecznie z dopiskiem, że chodzi o hosting współdzielony (shared).
Tu na forum po wywołaniu /api/admin/advanced/database widać to co niżej:
I would guess, that your plugins still have the wrong permissions set. Try to run "sudo chown -R nodebb:nodebb <nodebb folder>". Of course replace "nodebb:nodebb" with the user/group you have created in your installation.
How are you using MongoDB? Installed directly on the system or running for example in a docker container? I still would highly recommend to check if the MongoDB wasn't killed by the Linux OOM killer. MongoDB has a tendency to eat up all the available memory in your system. During testing for my own forum I ran into several issues with this.
In my theme, I have categories (treated as sections) and sub categories (categories set as child of those sections).
The class unread-class on the categories are always empty, even when there are unread topics.
Is that a known bug? Expected behavior on sub categories?
I managed to fix it by disabling the plugin, which let me then edit the post and I've also replaced the plugin with one that's actually maintained.
Thanks again for the help in locating this error.
My setup: 1.9.3 synced to master.
I set up a plugin to listen and log action:notification.pushed events.
It looks like notification events are fired only to recipients who are currently logged off.
Two questions if I may:
Is there a way to get a notification events for logged-in recipients as well?
Are there any settings controlling these events. For example, allowing the plugin to set a timeout, so if the recipient does not see/respond, an event is fired?
The folder is probably named /home/nodebb/nodebb not /path/to/nodebb so try. cd /home/nodebb/nodebb to go to the installation directory. If that gives the same error you can list the contents of the /home/nodebb directory by the ls command and find out the real name of the nodebb installation directory.
@pummelchen Thanks for the response.
Ok for the solution, but If that's true, it's still strange behavior. My forum is in a test period so indeed it doesn't have much traffic, but I come by at least once a day to see just how frequent the error is. It means that if we go on vacation and nobody visits our forum for a few days, when we get back all the owners of a forum under nodeBB have chances to see this error? That's annoying.