FriendsOfFlarum Byōbu, well integrated, advanced private discussions

luceos

JRay thanks removed the link

UaMV

Csineneo Sometimes private discussions are not marked on the discussion list until I view this post.

I have also noticed this to be an issue … particularly if I have entered the forum via a user profile URL or the tags page. When I first click back to All Discussions, then the recipients won't show until I have viewed each specific private discussion.

luceos

UaMV although not quite sure where this behavior comes from, it seems its related to adding the recipients model relationships (or their default includes) on the view page. I have something to start investigating with, thanks .. again!

UaMV

I don't know know that it has yet been mentioned, but it would be good to eventually allow control of notifications (email/on-site) for when a user has been included as the recipient of a private message.

luceos Another fun edge case for you, but may give some more insight into this issue… This appears to also happen when one has been included as a recipient in a message tagged with a tag that is hidden from all discussions. Clicking through to the tag does not show recipients until the discussion itself has been visited. Hope that his clear enough.

luceos

Csineneo thanks, I'll have to look into that.

UaMV your comment is a great pointer, thanks.

Csineneo

I set the 'editUserRecipients' permission to Members, but in fact Member can not see the edit menu.
And permissions are false in returned json.

"canEditRecipients":false,
"canEditUserRecipients":false,
"canEditGroupRecipients":false,

luceos

Hiding discussions when the extension is disabled might be half the solution. Because this event is only triggered when you disable the extension from within Flarum. If you decide to run composer remove, all private discussions will be made public anyway. Aside from that, there seemed to be some complications with identifying which extension is disabled, because that value is not accessible (PR pending for the next release). I will be circumventing this though.

amdad

Hey @luceos. This extension will be official Flarum part? Since, it's on roadmap for a long time.

luceos

amdad I have no way of saying that will be true. If it is this easy to add private discussions/messaging as an extension I would not be surprised to see this functionality to be kept outside of the Flarum organisation (core and core extensions).

For who is following my progress on hiding private discussions, it seems I won't be able to do this easily and I'm almost considering waiting for the next release which holds some of my fixes, before adding the functionality needed..

JRay

luceos bummer this was making good progress. I know it's not your fault, but waiting for the next official release could be forever at their release pace. ?

amdad

Thanks for answer. Personally I think this functionality should be optional (as plugin) but supported as a part of official Flarum release. Since PMS always was strong part of forum software.

luceos

JRay thanks, was hoping I could get it done too. But even my hack to circumvent wasn't successful. Will give it another shot soon.

UaMV

I just noticed that private discussions are not excluded where the tag page shows most recent discussion per tag. The discussion title is still displayed as a most recent discussion, even for a user not included as a recipient … at least when viewing the forum as an admin whose not been included.

UaMV

I've encountered the following issue. I thought maybe I could use a private discussion to draft a new discussion, so I added only myself as a recipient (thinking I could then remove myself as a recipient in order to publish the thread). However, when editing recipients to remove myself (the only recipient), the interface changes so it appears that I've been removed, but when I reload the page, I see that I am still a recipient and the message is still private. I suppose this could be in the design of the plugin – once private, always private – still worth mentioning.

Have I told you lately … thank you for the time you've given to extending Flarum! ??

luceos

UaMV thanks for your praise! ❤

In fact the design was exactly like you proposed, I even considered draft mode. So .. you found a bug. Here at the office that would mean sausage rolls for tomorrow.

I'm looking at the Split extension now, but once I'm done with that I'll focus my attention on byobu again.

luceos

UaMV the problem is that I forced the actor (logged in user) as a recipient if there are no recipient groups and the actor was not an recipient. This was done when saving the recipients. It makes more sense to add the current user to the recipients popup box, allowing the user to remove himself if he deems necessary. That way I won't need to force the actor as recipient anymore and it would allow removing yourself too.

This was fixed in development.

adriculous

This is strange. When I first installed Byobu on my first installation of the forum, everything went well, and I remember that the button next to the tags on the text field said "Recipients" in them.

In this fresh install, I'm seeing something else. Is there a way to fix this? http://i.imgur.com/dzFt9YZ.png

luceos

adriculous disable and enable any extension, this should regenerate the assets/*-<locale>.js files.

luceos

Tagged 0.1.0-beta.9 which solves the above issue of not being able to remove oneself.

luceos

Working on allowing recipients to flag a post and allowing access to this flagged post only for moderators. Quite the deal, but making good progress.

HavocK

luceos I would not want that... Allowing a mod to intervene in Private discussion makes it not private anymore...

« Previous Page Next Page »