FriendsOfFlarum Byōbu, well integrated, advanced private discussions

luceos For those using flagrow byobu please await our update, do not disable or uninstall byobu as that will open up private discussions to everyone.

Our update needs some testing after which we will most likely tag stable for byobu. Follow the extension thread for updates.

https://discuss.flarum.org/d/6341-flarum-v0-1-0-beta-7-released/9

We'll release a compatible update for beta 7 within 48 hours. The update will fix opening up private discussions when byobu is disabled once and for all.

Tagged 0.1.0-beta.17 and 0.1.0-beta.18.

• Implemented is_private properties of core to hide etc.
• Fixed a bug where deleting a recipient added through the profile card control was impossible.
• Added missing translation for "send pm" control on profile card.

If no new issues arise this will be most likely the last beta for this extensions. Because.. Flarum now supports keeping discussions and posts invisible (is_private) even if Byobu is disabled or uninstalled ? @Toby flagrow/byobu11

Now onto the harder part, updating. Read with care:

• Enable maintenance mode and make sure it works!
• Run composer update --prefer-dist --no-dev -o.
• Open your admin area to continue the database upgrade.
• Make sure you have beta 7 by checking in console with php flarum info.
• Do some quick checks whether your discussions are private still, if not create an issue on our tracker.
• Disable maintenance mode by setting offline to false in your config.php.

If at any step you get lost, get in touch!

I have just updated to Beta 7 including updating Flagrow byōbu. Everything went fine, private posts are properly hidden when the extension is disabled.

One reported bug is still present though:

Apoculos Only Admins are allowed to edit user participants once a private discussion is started... regardless of how I setup the permissions.

This brought me into a strange situation at my local testbed installation: As an admin I initiated a private discussion with another user and before sending it (or after the fact, I don't remember exactly) I withdrew myself from the recipient list. After that nobody was able to correct this mishap. As an admin I could not open this discussion (even though I started it), and the other user could not add me to the recipients again.

The bug that I Pollux earlier is now halfway resolved. Private discussions in the All Discussions view get their byōbu-decoration and the recipients listed even without having visited such a discussion before. The same however is not true when I enter any tag view with private discussions and reload the page. As before there will be no more visual indicators for a private discussion. To make them visible again, I need to look into said private discussions (as reported before) or reload the All Discussions view (new).

Pollux if you are able to report them on github it's easier for us to follow up. We'll look into this soon.

@luceos - hi, any progress with more "realtime" chatting in this great extension? I saw some commits in your GitHub, any ETA for beta testing? Thank you!

I found a serious bug exposing supposedly private discussions to the public, when initiated via the user profile link.

I also reported it on Github: flagrow/byobu37

Sorry, I forgot to mention @luceos

Pollux no worries I follow all Flagrow extension threads.

I'll take a look asap and do some catching up on reported items tomorrow.

@luceos

Wonderful, I updated already. Unfortunately the second change (permission can now be configured per tag) doesn't work as intended.

I also reported it on Github: flagrow/byobu39

Thank you for the update luceos

We run into a small problem after updating, public discussions cannot be started anymore. A discussion can only be started when recipients are selected..

I reported the bug on Github flagrow/byobu40

luceos Can't understand why you're the only one ?

In my case, our forum is not public yet and our talks right now were in fact only in existing discussions.

Thanks once more for your prompt reaction.

luceos Thank you for you swift response ?? and the great extensions you wrote ?

I am getting

POST http://flarum.loc/api/discussions

{
  "errors": [
    {
      "status": "404",
      "code": "resource_not_found"
    }
  ]
}

when I specify a recipient.

And discussion is created normally if I don't specify a recipient.

sledov I'm getting the same. Posted the issue on Github.

Veriael right, previously you were added per default. That might have been lost, I will look into this.