FriendsOfFlarum Byōbu, well integrated, advanced private discussions

giter

Swift_TransportException: Expected response code 354 but got code "503", with message "503 Error: need RCPT command

Regarding the error, I found that it occurs if a private discussion member uses a non-existent email address. By using the correct email address the error disappeared.

stimw

When will the stable version be released? Thank you.

peopleinside

stimw Byobu is compatible with Flarum 1.0.2

luceos

IanM I don't 🙁

stimw make sure to update using composer require fof/byobu:*@beta

ornanovitch

Hey, IDK if it's already a known issue but it seems that it's still possible to edit recipients for non Byobu discussions.
Keep up the good work 😀

luceos

ornanovitch I hadn't even noticed 🙈

IanM

ornanovitch This is to allow the conversion of a regular discussion into a private discussion

GreXXL

ornanovitch Hey, IDK if it's already a known issue but it seems that it's still possible to edit recipients for non Byobu discussions.
Keep up the good work 😀

Don't know if intended? But I think not - was reported above just for completeness 🙂

ornanovitch

luceos one step after another 😁

Walys

One question about byobu extension.
Have any possibility in the admin panel to limit to use this "private message" for new users?
I think this is good idea for avoid profiles only registered in the forum to spamming via MP

Maybe limit for post.... If the user not have more than 50 post not have any possibilty to use this extension.

GreXXL

Walys yes permissions are available. You just need a group and maybe Auto Moderator extension if you want to automate access to the group

Walys

GreXXL mmmm.. ok thanks. But this extension not have this limit option by default no?
If I understand you, it´s necessary third extension to moderate this limit per user.

GreXXL

Walys yes this extension ships with permissions to restrict access, starting individual or starting group conversations (and a lot more). It does not implement any limits but that’s what permission groups are for. This is not part of any extension.

As you might want to automate permission groups (eg. Trust Levels) there is an awesome extension for that which I will link you: https://discuss.flarum.org/d/27306-flarum-automoderator

ornanovitch

[to reproduce]

I noticed that on the discussion list, for a private discussion, the recipient zone (item-recipients) is clickable as expected (as the entire DiscussionListItem), but doesn't point to the discussion id. It just reloads the discussion list 😶

IanM

1.0.0-beta.7

Fix recipients modal styling issue
Adds frontend typings for better development
Hide admin page translation relating to Tags if tags is not installed
Extract Prettier config to .prettierrc
Bump Webpack CLI
Conversions to Typescript and more modern code
Use core [deleted] text instead of custom translation
Use oninput instead of onkeyup to support copy-pasting
Clean up Less
Merge recipient label borders when next to one another (no more 2px borders!)

Huge thanks to @davwheat for putting this together whilst I concentrate on other things these last couple of weeks 🏆️

Installation

composer require fof/byobu:^1.0.0-beta.7
php flarum cache:clear

Please continue to provide feedback on your experiences with this beta, so that we can move towards 1.0 of this extension as quickly as possible 👍️

IanM

Justman10000 No, it's not. Please read the thread. Simply posting > Justman10000 Outdated
on any extension you think is not updated is not useful.

IanM

rafaucau

The search for recipients is case-sensitive. This makes it very difficult to search.

K4nj

Hello, good day I'm facing an issue where my forum displays a blank editor and I can't click anywhere !(https://prnt.sc/16kv8wl) this happens when I click send a message, a bit of assistance would be greatly appreciated thank you.

IanM

K4nj Can you tell me which version of the extension you are using please?

K4nj

IanM latest beta version of this plugin, I'm also using the latest florum core.

ornanovitch

GreXXL as @IanM stated in a split discussion:

This is to allow the conversion of a regular discussion into a private discussion

So this is as intended. Nevertheless there is an opened MR which discusses it. Quoting myself about this intended behavior:

I fully agree, but IMO in that case such a possibility should depend on an other permission than editUserRecipients and editGroupRecipients as it's a very specific action that one could want to restrict a lot more

Maybe it would be more consistent if edit{User|Group}Recipients were general permissions, when something like togglePrivateDiscussion would be a "restrict by tag" permission?

IanM

K4nj could you please try downgrading to the previous extension version and see if the problem still exists?

composer require fof/byobu:1.0.0-beta.6

If so, this is a regression in the latest, which I'll get looked at ASAP

K4nj

IanM same issue, might be issue on my side? not too sure but any suggestions on how I could possibly go about sorting it out, (https://prnt.sc/16kxig8), but this is my settings for it, not too sure if I'm doing something wrong.

« Previous Page Next Page »