Opened 10 years ago
Last modified 10 years ago
#2630 new defect (bug)
Closing a private topic changes status back to public
Reported by: | alexander.rohmann | Owned by: | |
---|---|---|---|
Milestone: | 2.8 | Priority: | high |
Severity: | normal | Version: | 2.5.4 |
Component: | General - Administration | Keywords: | needs-patch |
Cc: |
Description
So I'm seeing a few scenarios where closing/opening a topic for replies resets the topic visibility, and vice versa.
Scenario 1:
- Edit a topic, and change visibility to private.
- On the front end, click "Close" for the topic.
- View the topic in the dashboard, and you can see it's been reset to public.
Scenario 2:
- Click "Close" on the front end for a topic OR change status to closed in the dashboard.
- Edit the topic in the dashboard, and set "Visibility" to "Private"
- After clicking update, the Visibility will be private, but the status will reset to open
Scenario 3:
- Editing a topic in the dashboard, change visibility to "Private"
- Change status to "Closed" from the post editor screen.
- After clicking update, the post status remains open
We often use private topics for our team to continue a conversation with users outside of public view. There are times when we would also like to close the discussion. This bug prevents both from happening on the same topic.
Change History (2)
Note: See
TracTickets for help on using
tickets.
Confirmed, but unlikely to have a fix until 2.7. This has to do with having multiple
post_status
form fields between the bbPress metabox and the WordPress core one. We've gone back-and-forth with tweaking this behavior in the past, and it likely needs a bit more massaging.