DB structure / connection of threads and posts ... post double displayed in different threads
-
Hi all,
some things about me:
I am an IT guy, but have nearly no experince with mongo. Used to work with php/mysql, "oldscool"stuffSome things about my system:
Ubuntu 18 Server
Mongo v3.6.3
nodeBB v.1.10.0 (latest yesterday)I have a notebb forum running, and some weird things happen.
A post was posted, but is displayed ion two "different" threads.Why
I would like to know how threads and post are connected. Is there any database structure available?
The "problem record" is in objects.
_key = post:2952 pid = 2952 uid = 10 tid = 9 toPid = 2951
So what for is pid, uid, tid and toPid?
This record is displayed in:
- topic/172/zitat-des-tages/37
and in: - topic/9/wanderwochenende/13
Anybody any clue, why this happens?
I have none - sorry ...Can anybody point me in the right direction?
Any help highly appreciated.Kind regards,
tecy - topic/172/zitat-des-tages/37
-
pid = the unique post id, this never changes
uid = the id of the user who posted it, this never changes
tid = the id of the topic this post is currently in, this changes if the post is moved between topics
toPid = posts can be direct replies to other posts, in which case this field stores the post which is being replied toA post shouldn't be in multiple topics.
-
Hi all,
thanks for the reply.
Made the steps & structure clearer to meI imported an Backup and the stuff is running like a charm.
But when I have a look at the logs, I always see stuff like this:88.xx.xxx.xx - - [28/Sep/2018:16:47:32 +0000] "GET /error_docs/internal_server_error.html HTTP/1.1" 404 - "-" "Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0"
If I call directly:
an error appears, saying:
- error_docs/internal_server_error.html does not exists. go to startpage.
But actually the folder structure:
- /error_docs/internal_server_error.html
exists in the nodebb "root" folder where the forum is installed.
Do I have a chance to get to know where this error comes from?
Would be great resolving this issue!
-
The most efficient way is to just put them in a separate directory and configure your reverse proxy to serve them statically.