FriendsOfFlarum Byōbu, well integrated, advanced private discussions

poVoq

luceos

poVoq how come you think is caused by byobu and not the other extensions active? From what I can tell there's just too much going on so it doesn't fit.

luceos

poVoq Oh and a word of warning: disabling this plugin makes all private discussions become public

What flarum version do you run because that isn't supposed to happen.

poVoq

luceos Beta7.1

poVoq

Because when I disable Byobu it works. And if I disable the other plugins and keep Byobu on the issue remains to some extend.

Edit: after playing around with it some more, it seems to be indeed caused by a combination of various issues.

matteocontrini

@luceos I think the preview image in the first post is broken ?

luceos

matteocontrini it is, i'm transferring them. Those files were hosted on a Flarum discuss installation I used for testing.

ANONIMNIQ

This extension is awesome, but why users can't change participants and can't delete their private discussions forever?

luceos

ANONIMNIQ users can't change participants

there's a permission for that..

ANONIMNIQ can't delete their private discussions forever

this is also related to a global permission (delete discussion) and this normally falls onto the role of moderation

ANONIMNIQ

luceos I try permissions, but I want authors of private discussions to change participants and to delete only their own discussions. If I get this permission to them, they have oprion to change participants on other peoples threads and to delete them. That's not what I want.
Private discussions are hiden from admins/moderators, so If author of private discussion delete it, there is no way admin to delete this discussion forever.

luceos

ANONIMNIQ i'll take this along for future releases, don't expect it soon though.

ANONIMNIQ

I'm not sure if this is a good idea, but maybe we don't need to select tags for private discussions and instead of this, all private discussions automatically to go in their own Private tag. This is my idea:

PaulArenson

I seem to be having trouble sending ONLY to a user, I am asked to choose a TAG. (All my tags denote broad thematic discussion areas, and are accessible to everyone. Since I want to use it as a PM, I guess I can create a tag that says CLICK TO SEND ONLY TO USER, NOT A TOPIC. (That assumes I HAVE to choose a tag)

Also, the one time I succeeded as an admin in sending to a user (also me with another login name in another browser), there was no notification to the user that they had a message. Is that the way it works?

Thanks.

luceos

PaulArenson byobu is not a PM extension. It's a DM extension, it allows discussions between users and groups. Initially the idea was to create a PM extension, but I wanted to stay close to existing functionality as much as possible. So eventually what I released was an extension that integrates nicely into Flarum, takes care of keeping discussions private. As a consequence it has the same requirements of any discussion, meaning if you demand a tag, Byobu does too..

I guess it will be a matter of time for someone to come up with a decent PM extension though.

PaulArenson

luceos

Thanks. I did not quite get the difference since I have my forum set up with one tag per topic. A very small group with a very limited number of topics. Now I think I have it sort of working "like" a PM. I have a TAG view and my login view. and I created a Tag as follows:

                        Private Messages (Send & Read)

To send a PRIVATE message, choose THIS tag, choose a user, and do NOT choose a topic tag. To SEE your private messages, click on this tag.

So then the sender clicks on this and only has to add a user. Then look in the same topic (or notifications it seems is the same?) for the message.

So far it seems that a message comes to the recipient. And if I understand, one does not HAVE to type @username for that to happen.

Unrelated to this extension but I guess important for notifications is if each user sets both "Someone replies to one of my posts" and "Someone mentions me in a post" to make sure EMAIL is checked. Otherwise nothing comes to remind them.

Am I doing this right?

luceos

PaulArenson Am I doing this right?

It's your forum not mine. Whatever suits your needs ... suits your needs. This extension or any of those by Flagrow are not meant to force you into a specific way of using Flarum. Don't expect us to know whether what you envision and set up as representation is okay, because we can't say.

PaulArenson

luceos Yes, that's true. Anyway it works for my needs (message get to who they should) EXCEPT that it seems if I send a message to two users, an email does not always come to both users notifying them. It seems more consistent when I am replying to another user in a topic. Not sure if there is some error on my part. Probably not a problem with byōbu I guess.

EDIT

I think the problem is my misunderstanding of Flarum. I am learning both the platform and THIS extension at the same time and getting confused.

1) In a normal topic (sent to a tagged topic), the first message doesn't seem to notify anyone. Or so it is for me...this would seem to be a problem since other members do not know there is a new message or topic).

2) Likewise, in a message using byōbu. (Unless I add @user).
3) But in both cases a REPLY will send a notification mail.

(In a private message, I seem to need to add @user, or REPLY to the first message)

Now I wonder if I still fail to understand something....

PaulArenson

luceos

One more thing I noticed. If I have the extension activated I get the permission to create private discussions in administration. But even if I have that set that to members, as my permission to start a discussion is limited (for now) to administrators, the users can't actually send a private message.

Does that mean if I want them to be able to send a private message, I have to allow them to start discussions?

luceos

PaulArenson yes the extension works on top of the native flarum functionality.

tamasurfi

Hi!

I installed the extension in beta8.1, but I got this error:

Notice: Undefined index: data in /path.../vendor/flarum/core/src/Frontend/Content/CorePayload.php on line 76

Fatal error: Uncaught Zend\HttpHandlerRunner\Exception\EmitterException: Output has been emitted previously; cannot emit response

Is this a bug with beta8.1?

clarkwinkelmann

tamasurfi you might need to configure your PHP to not output notices. Not sure if we actually have recommendations regarding that in Flarum docs.

Maybe it could also be an issue with the extension but I'm not sure.

luceos

tamasurfi could you post some more information? The output of php flarum info would be best. I can't seem to reproduce.

« Previous Page Next Page »