Closed pflstr closed 6 years ago
@pflstr just did a test locally and cannot reproduce. Did you first create a public discussion and make it private afterwards?
@luceos I started the private discussions via the user profile link. Maybe, the issue only arises there. That's also the way I reproduced it at Devflarum.
I think, this issue is related: https://github.com/flagrow/byobu/issues/37
The first post now gets the posts.is-private
field set to 1 fixing the above issue, but the discussions.is-private
field still doesn't, and maybe that's why replies don't get the posts.is-private
set to 1 either.
Just tested this again:
Am I missing something @pflstr. If this is an issue I'd like to get all necessary information:
php flarum:info
Thanks!
php flarum:info
is not at hand (DevFlarum).
Tagged 0.1.2 which addresses some private property things. Went over this full procedure to see whether I could reproduce again but to no avail. Would love to hear whether this is fixed for everyone.
As far as I've understood, the purpose of the introduction of the
is-private
field into theposts
anddiscussions
tables was to avoid that private discussions become visible while Byōbu is deactivated e.g. during an upgrade process.Right now however, Byōbu sets neither the
discussions.is-private
field nor theposts.is-private
field beyond the original post to 1. The consequence is, that only private discussions without replies stay invisible after deactivating Byōbu, every private discussion with at least one reply becomes visible (bar the original post) to everyone (if not restricted otherwise).This behaviour can be reproduced at the Devflarum sandbox server.