Thank you, @baris

GitHub issue: https://github.com/julianlam/nodebb-plugin-support-forum/issues/7

ELadner created this issue in julianlam/nodebb-plugin-support-forum

closed Moving topic to another category has side-effects. #7

Ok. I think I know what's going on.

We're using a plugin called support forum that looks like it hasn't been updated in quite a while. My guess is that it keeps a hard reference to the tid, even if it's moved to another category.

It's only 168 lines of source, but I don't know Node.js or NodeBB architecture enough to make heads or tails of it. Maybe I should put a bounty on it? Not sure how well those kinds of offers are received, though.

@baris said in Moving topic from one Category to another:

db.objects.find({_key: "cid:<cat_A_id>:tids", value: "<moved_topic_id>"});
db.objects.find({_key: "cid:<cat_A_id>:tids:posts", value: "<moved_topic_id>"});
db.objects.find({_key: "cid:<cat_A_id>:tids:votes", value: "<moved_topic_id>"});
db.objects.find({_key: "cid:<cat_A_id>:tids:lastposttime", value: "<moved_topic_id>"});
db.objects.find({_key: "cid:<cat_A_id>:tids:recent_tids", value: "<moved_topic_id>"});

Very odd, and matches some very odd stuff I've seen on other things.

Replacing with the appropriate topic and category ID's doesn't return any values.

MongoDB shell version: 3.2.16
connecting to: nodebb
> db.objects.find({_key: "cid:35:tids", value: "39220"});
> db.objects.find({_key: "cid:35:tids:posts", value: "39220"});
> db.objects.find({_key: "cid:35:tids:votes", value: "39220"});
> db.objects.find({_key: "cid:35:tids:lastposttime", value: "39220"});
> db.objects.find({_key: "cid:35:tids:recent_tids", value: "39220"});
>

Just so I know it's working, here's the category it was moved to:

> db.objects.find({_key: "cid:54:tids", value: "39220"});
{ "_id" : ObjectId("5a610c4e1a911d0fab1a28aa"), "_key" : "cid:54:tids", "value" : "39220", "score" : 1516309669264 }

Me, as an admin, if I go look at the CatA category, it looks completely blank (all posts moved to private CatB). If I create a regular authenticated user and look at CatA, it's completely blank.

However, the creator of the moved_topic can still see a ghost of the topic in CatA.

Is there some per-user server-side caching going on? I can't see a way this could be client side, especially since there have been multiple reports of seeing the snippet of the most recent post change (right side of the topic in the list when it shows the most recent user to post and the first 100 chars or so of the post itself).

yes. My mongo is a little noobish, but I have command line access.

NodeBB 1.7.0

CatA settings: nothing special. registered users can find cat, access cat, access topic, create topic

CatB settings: also nothing special. privileges are assignd to only one group (full privs across the board for that group)

Long story, but here goes.

1. Two categories: one open to registered users (CatA), one restricted to a group (CatB).

2. Occasionally, moderators will move a topic from the open group to the closed group (CatA -> CatB) to discuss it in more detail in a closed session.

3. The original topic shouldn't be visible in CatA anymore (and to most people, it is not) but the original poster of the topic can still see it on the list. He can't click on it (permission denied in the other forum) but can still see the first line or two of the last post in the preview on the right.

I doubt this is a setup issue. Is this some kind of dangling reference bug?

Re: Change all postings for a one user to another user.

I'd also like to know if it's possible to move one users posts to be owned by another (specifically for merging two accounts created by the same user into one user account).

I have the same issue (both Chrome 62.0 and Firefox Focus 2.5) on Android 8.0 (Pixel XL). Although, my issue is slightly different that originally reported (can't press on sides to get anything to scroll if nothing but pinned topics are visible).

Scrolling on non-pinned threads works fine. Scrolling on pinned threads doesn't work.

@joykiller Nope. Steps to repeat are as simple as:

1. goto Manage->Categories.
2. Select any category (hit Edit)
3. click on Privileges
4. click on any single privilege displayed to toggle it.
5. Every click adds another "Create Poll" column to the table and shifts everything left.

It appears after clicking what's necessary, the "copy to sub-cats" works as expected. So.. I don't think it's affecting functionality, just an annoying visual glitch that makes large scale permissions edits tedious. Everything ends up very squished after a while.

Going out and into aother category, the table remains with the same number of columns as before with all the extras. only way I've found to reset it is to "reload" NodeBB.

Hmm.. No good. Only removing both plugins that added privs corrected the issue (calendar and poll plugins). Adding back just the poll problem reproduced the issue again.

Both plugins were "uninstalled", NodeBB restarted, then tested the privs page, then the poll plugin was installed and activated (followed by a restart). Issue returned.