Opened 8 years ago
Last modified 7 months ago
#2504 new defect (bug)
Forums: Replies from archived topics are still displayed in user profiles
Reported by: | SergeyBiryukov | Owned by: | |
---|---|---|---|
Milestone: | Q1 | Priority: | high |
Component: | Support Forums | Keywords: | |
Cc: |
Description
- Archive a topic (but not individual replies).
- Replies from that topic are still displayed in participants' profiles.
Change History (20)
#2
@
8 years ago
It's not just archived; replies from pending and spam topics are also displayed in profiles, unless replies themselves have a non-public status too.
#3
@
7 years ago
repiles from archived topics are displayed in RSS-feeds as well, unless they are archived too
This ticket was mentioned in Slack in #forums by clorith. View the logs.
7 years ago
#5
@
7 years ago
@coffee2code might have some information on the connection between profiles and the archived states here.
#8
@
5 years ago
Thinking on this, getting the parent topic of posts and checking the parent state sounds relatively expensive, I wonder if the right approach here would be to hook into the status change and change any reply with a default state to be archived as well, we would have some floaters pre-implementation, but I think that's an acceptable tradeoff, and they can be dealt with manually if desired?
Not sure how we would solve the data that's been sent to the profiles section though, since that's technically a different system.
This ticket was mentioned in Slack in #bbpress by netweb. View the logs.
5 years ago
This ticket was mentioned in Slack in #bbpress by netweb. View the logs.
5 years ago
#11
@
5 years ago
See: bbp_trash_topic_replies()
and bbp_untrash_topic_replies()
When a Topic has some action taken on it, some other action needs to run on the children Replies.
Unfortunately, you cannot simply blindly take action on all of them, because some of them may already be trashed, and you don't want untrashing something to accidentally bring things back from the dead.
See the _bbp_pre_trashed_replies
Topic meta key, as an example of this juggle. It makes sure that when a Topic is untrashed, that previously trashed Replies do not suddenly also become untrashed.
(The same happens when marking a Topic as Spam.)
My recommendation is to mirror this behavior for Topic Archives, and mark the replies as archived
as well. This may require a bit of finesse, since Topics generally expect their replies to either be "public" or "non-public" by default, and Archived kinda walks the line.
#12
follow-up:
↓ 17
@
5 years ago
Is this a bbPress core thing, or a weirdness due to an optimization on the WordPress.org side of things?
This ticket was mentioned in Slack in #meta by sergey. View the logs.
4 years ago
#17
in reply to:
↑ 12
@
4 years ago
Replying to dd32:
Is this a bbPress core thing, or a weirdness due to an optimization on the WordPress.org side of things?
This is a dotorg thing, archived
is a topic/reply status that was implemented here specifically, so I think comment:11 has the keys we need, our custom status needs to do the same kind of juggling with reply-statuses.
Related: #2408 (for WP.org profiles).