FriendsOfFlarum Byōbu, well integrated, advanced private discussions

clarkwinkelmann

YaarBaturalpArtar you need to clear the cache to reload the translations I guess. Also check Cloudflare cache if you use it.

bikepost

YaarBaturalpArtar I get this when I install extensions. Eventually, your (shared?) server will refresh and everything will look normal. It seems to take 1-2 days for me.

Cleaning up the browser cache doesn't help in my case. This is something on the server even after I clear cache there too with

php flarum migrate 
php flarum cache:clear

YaarBaturalpArtar

bikepost Yes its shared, ok then thanks.

bikepost

I have an issue when trying to designate one recipient: I get this, see the image below please.

is it because of this missing code @luceos ?

 "prefer-stable": true,
    "minimum-stability": "beta"

Here is what the bottom code of my composer.json looks like, so I don't think that's the issue.

[redacted]

luceos

bikepost no it's because you have to add yourself as recipient in order to view the private discussion. You used to be included by default, I must have erroneously removed that with the latest refactoring.

Will be back in the next release though ?

bikepost

luceos ?

Of course, why didn't I think of that? Just tested and it works!
Thank you!

luceos

Tagged 0.1.0-beta.21 which fixes the issue that the current user is not added to the recipients by default.

Thanks for your reports!

bikepost

luceos It's the least I can do. So thankful and happy for all the work you guys do and the support you have provided me with.

Thank you very much.

wignu

This may be a dumb couple of questions but I've never let that stop me before. Do these discussions appear in the main discussion list, there's no separate 'area' to access them and will this create a private discussion 'tag' on the side to access them?

luceos

wignu

Do these discussions appear in the main discussion list,

Only for the recipients.

there's no separate 'area' to access them and

Search with is:private to find all private discussions you have access to.

will this create a private discussion 'tag' on the side to access them?

Nope, but you can create a link to a page that filters by is:private ?

wignu

Wow, thanks @luceos for your prompt answers ?. Main reason I asked the questions is that as an administrator I would get a lot of messages, which would of course be private discussions with your extension, so I'm guessing they could potentially overwhelm the first page or so of the discussions which is something that really should be avoided. Have you considered a separate area, say alongside or integrated with the notifications where you can view the private discussions away from the main discussion list?

luceos

wignu I did. The diversity of how this extension can be used is immense. So simply hiding all private discussions per default is not a solution. If any implementation of such a feature should be added, it should play nice with the other extensions.

Having said so, being able to lock down who can create and update recipients per tag should allow for pretty flexible set ups. You could create a tag hidden to the public which has the required permissions for members to create a private discussion with just you.

One thing I do consider is allowing for a support desk-type of usage. This would mean something like the ability to specify a tag and forced recipients in the admin, this would be very powerful if combined with the tag permissions.

bikepost

Dear luceos

I would like to add to this conversation by stating that as an owner/ admin on my forum, I would want the ability to see ALL private conversations, even if I am not part of them.
There are liability, housekeeping, information ramifications to justify this.

JRay

luceos You could create a tag hidden to the public which has the required permissions for members to create a private discussion with just you.

This is interesting.

Could I create a tag for "Private Discussions" that would allow them to be viewed all on one page and also allow me to control permissions for them via that tag? For example, allow users to delete these but not other topics.

Or can we add a column to the permissions tree that handles the Private tag?

wignu

@luceos I wasn't thinking of it as a whole solution as such but as an option as no doubt there will be those who would wish to use it in the discussion and others separate it out. Having it compatible with other extensions is of course a given, am I right in thinking that if you did have an option of separating it out it will create another set of programming problems??

Unfortunately your second paragraph doesn't really solve the main issue I was talking about with the discussion page getting filled up, sure it won't be to those not involved in the discussions but to the mods/admins it could well be so.

Honestly not too sure on what you are driving at with your last paragraph.

luceos

wignu Honestly not too sure on what you are driving at with your last paragraph.

Let's say you have a tag "priority" and you configure that one to allow create and view by members. You allow private discussions in that tag. Within the admin area you can specify that specific user groups and users are assigned to each new discussion in this tag, this in addition to the using starting the discussion.

As a result each new discussion in that tag will be private by default and visible only to a specific preconfigured group of users.

Visually the users will be immediately added when the tag is selected and the recipients selector will be disabled.

Hope that makes more sense ?

wignu am I right in thinking that if you did have an option of separating it out it will create another set of programming problems??

Separating it out is not an issue. The effects that private discussions disappearing from the index without proper visual indicators is though. If you're able to brainstorm a bit in an issue on the GitHub repository, then I'd be more than willing to consider an implementation.

wignu

@luceos To be honest not being a programmer, or any inkling of one, I don't think there would be much use me muddying the waters in there.

luceos

wignu most development tasks I receive professionally are written down as user stories, they hardly ever specify how to get there technically. As a user and requester of a feature you most likely have an opinion how you'd like to see this feature in your Flarum forum. So feel free to create an issue on GitHub if you can ?

Veriael

It seems that Polish language file is missing line 10:

send_pd: "Wyślij wiadomość do {username}"

And causes 500 internal server error, when Polish enabled. I already translated this line for you, so if you wish, just add it and it will hopefully work properly (as it works for me).

luceos

Veriael not likely that is causing a 500. I think the problem was the 0 at the end of the file. I've removed it and added your translation. Will tag a new version soon ™

meto

Thanks for this great expansion.

I hope Flagrow byōbu can improve this:
Automatically generate a Conversation node (Hidden in all discourse), the user can only add a participant to a private messages after selecting this node (If the user does not select the node, it will not be able to add the participant, just like the general discourse).

Veriael

bikepost
I wouldn't agree - private, means private.

clarkwinkelmann

bikepost I would like to add to this conversation by stating that as an owner/ admin on my forum, I would want the ability to see ALL private conversations, even if I am not part of them.

Just a reminder: if you really need to access the private messages you just need to access the database. Or do you need to access the private messages of your users 24 hours a day ? ?

Also, if a member of the conversation flags a message you will be able to see it in Flarum.

« Previous Page Next Page »